[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#529174: marked as done (linux-image-2.6-xen-amd64: Kernel hangs on Dom0 Boot)

Your message dated Mon, 15 Feb 2010 20:39:56 +0100
with message-id <20100215193956.GB19179@baikonur.stro.at>
and subject line Re: linux-image-2.6-xen-amd64: Kernel hangs on  Dom0 Boot
has caused the Debian Bug report #529174,
regarding linux-image-2.6-xen-amd64: Kernel hangs on  Dom0 Boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
529174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529174
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6-xen-amd64
Version: 2.6.26+17+lenny1
Severity: critical
Justification: breaks the whole system


When booting with xen 3.0.3-1amd64 /Debian GNU/Linux, kernel 2.6.26-2-xen-amd64 kernel, it hangs after displaying the following message on the tty..

(XEN) Xen trace buffers: disabled

I had to roll back to the old kernel 2.6.18-6 to report the bug.


-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-6-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6-xen-amd64 depends on:
ii  linux-image-2.6.26-2-xe 2.6.26-15lenny2  Linux 2.6.26 image on AMD64, oldst
ii  linux-modules-2.6-xen-a 2.6.26+17+lenny1 Linux 2.6 modules on AMD64

linux-image-2.6-xen-amd64 recommends no packages.

linux-image-2.6-xen-amd64 suggests no packages.

-- no debconf information

!DSPAM:4a10751515581985114631!

--- End Message ---
--- Begin Message --- 
closing as no followup since initial report.

also most propably a well known limitiation of the 2.6.26 patchset
to not use too many virtual cpu's or such.


thanks for your report.

--- End Message ---
Reply to: