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


[Xen-bugs] [Bug 873] KERNEL PANIC on on Xen v. 3.0.3

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 873] KERNEL PANIC on on Xen v. 3.0.3
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 11 Feb 2007 12:24:42 -0800
Delivery-date: Sun, 11 Feb 2007 12:25:35 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-873-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

henning_sprang@xxxxxx changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

------- Comment #2 from henning_sprang@xxxxxx  2007-02-11 12:24 -------
This Kernel version is not produced by Xen upstream. 

Please report it as a bug in the Debian bug tracking system - they are the
providers of the Xen-Linux-Kernel you use. If they realize the problem comes
from upstream code, they will file a bug in Xen BTS.

The Debian Bug Tracking System is located at http://bugs.debian.org, or use

Apart from that, for a proper reproduction of a bug, you should add information
on the situation in which it occured.

I tag this bug as invalid in the Xen BTS, as it's not confirmed a Xen upstream
bug. You can give the Debian developers this bug number, it can then be
reopened if they  believe it's an upstream bug.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

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