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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 24 Apr 2004 09:14:22 +0100
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, Xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 24 Apr 2004 09:16:26 +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
The "weird failure" message comes out only occasionally?

I guess if that is the case then it is harmless, but I added some
extra tracing to the e100 driver so we can take a closer look if we

I guess the driver gets into an occasional exceptional state such that
this message appears and then it executes a rare function in the
receive path that causes a blow-up. I've now checked in a fix for the
bad receive function so that should get rid of the crash, but not the
tx warning.

 -- Keir

> 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!
> I got a couple oops messages pasted below, and the xen startup messages.
> My build of xen.gz and xenolinux.gz are here:
>     http://www.cs.duke.edu/~becker/xen/
> The hardware is an IBM x330 PIII with 256MB phys mem.  DOM0 has 40MB and DOM1
> has almost 190MB.  Both domains have 1GB of swap space.  DOM0 runs off
> of real partitions and DOM1 off of virtual disks.
>    # xc_dom_control.py list
>    Dom  Name             Mem(kb)  CPU  State  Time(s)
>    0    Domain-0           40000   0    r-       87
>    1    athos07           189440   0    --      111

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>