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] Xen bug or sky2 device driver bug?

To: Jae-Wan Jang <jwjang@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen bug or sky2 device driver bug?
From: Marco Gerards <mgerards@xxxxxxxxx>
Date: Fri, 18 Aug 2006 10:22:31 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 18 Aug 2006 01:20:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44E5713A.2050106@xxxxxxxxxxxxxxxxxx> (Jae-Wan Jang's message of "Fri, 18 Aug 2006 16:50:18 +0900")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-copies-to: mgerards@xxxxxxxxx
References: <44E5713A.2050106@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
Jae-Wan Jang <jwjang@xxxxxxxxxxxxxxxxxx> writes:


> I'm using ASUS P5WD2-E Premium mother board.
> It has two Marvell Yukon II gigabit Ethernet and sky2 device driver is
> used for them.
> When domU receives lots of lots of packets (about 10Kb each),
> dom0 crashes.
> Unfortunately, my machine doesn't have serial port, I can't capture all
> the oops messages.
> Following is backtrace of the oops messages.

May I assume this is only when you are using it in gigabit mode?

This same bug is mentioned here:

I have a MacBook with the Marvell Yukon II and I am using it as
100MBit only.  It works perfectly for me, although I tried hard to
reproduce this specific bug.


Xen-devel mailing list