This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] memory fault

To: David Becker <becker@xxxxxxxxxxx>
Subject: Re: [Xen-devel] memory fault
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 23 Apr 2004 21:33:43 +0100
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, Xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Fri, 23 Apr 2004 21:38:53 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Fri, 23 Apr 2004 16:11:02 EDT." <20040423201102.GN3473@xxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> " It's a message from Xen. It only gets printed if the network device
> " driver's transmit function returned an error. This should never happen
> " (if the driver isn't ready to accept packets there is a way to signal
> " that).
> "   
> " Maybe it's a driver or hardware bug. Maybe Xen is running low on
> " memory (unlikely).
> I am seeing xen crash again with the 'Weird' log message.
> This time it is xen-1.3-devel using an eepro100 NIC:
>     (XEN) Weird failure in hard_start_xmit!

Couple of questions that I think might be a big help to us in
tracking this down:

 Can you repeat with hardware other than eepro100? (Our test
machines have tg3 and e1000 cards).

 Can you reproduce reliably using the ttcp test program? 

 What about in UDP mode "ttcp -s -u -fm", or does it require data
to be flowing in both directions to trigger it? (I presume it's
the transmitter that blows up?)

 Does reducing the packet size (and hence taking the packet rate
up) cause the bug to trigger more frequently?

 Can you cause the bug to trigger with just one domain running on
each machine?

 Can you cause the bug to trigger with the machine booted "nosmp"?

Of course, the new IO stuff should be ready soon and the bug
might just disappear ;-)


This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>