WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 713] XEN Crashed the Kernel on high network traffic

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 713] XEN Crashed the Kernel on high network traffic
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 18 Oct 2006 16:11:59 -0700
Delivery-date: Wed, 18 Oct 2006 16:12:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-713-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=713


haircut@xxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |haircut@xxxxxxxxx




------- Comment #2 from haircut@xxxxxxxxx  2006-10-18 16:11 -------
I experienced a crash under related circumstances. I successfully created a
dom0 on a dual proc dual core Dell Xeon box following a guide by Mark Foster (
http://mark.foster.cc/wiki/index.php/Xen_on_CentOS-4 ). The dom0 boots, but
eth1 doesn't come up on boot. No clues in any logs as to why, in fact, the
syslog indicates that the interface *does* come up. No matter (for now), eth1
can be brought up manually. Other ignored errors seen during boot: "FATAL:
Module microcode not found", "FATAL: Module acpi not found", "smartd startup
failed". Whatever, I can still log in, and after restarting the network the box
appears completely normal by any measure.

As soon as I try and scp a large file to the box, BAM! Kernel panic. I don't
have kdump set up, but I did take a photograph of the panic and will attach it
to this bug. 


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

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