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

Bug#603432: marked as done (linux-image-2.6.32-5-amd64 hangs when booted as VM under Xen)

Your message dated Thu, 9 Feb 2012 02:41:53 -0600
with message-id <20120209084153.GA2488@burratino>
and subject line Re: linux-image-2.6.32-5-amd64 hangs when booted as VM under Xen
has caused the Debian Bug report #603432,
regarding linux-image-2.6.32-5-amd64 hangs when booted as VM under Xen
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.)


-- 
603432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603432
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-27
Severity: important


Hi.

I have a virtualised server rented at some ISP, which uses Xen for virtualisation.

The setup is rather simple:
- running sid
- using lvm
- root-fs is on a LV using ext4
- CPU is 64 bit

When ever I booted an -amd64 kernel, the system hanged (see attached screenshort for the
place where it hanged), regardless of whether the userspace was i386 or amd64.
The 32 bit kernels (e.g. -486) worked however without any problems.

After many hours of trying, I (with the help of my ISP) found out that the problem seems
to be solved in at least the 2.6.36-amd64 kernels from experimental.

The ISP runs the following configuration:
-Xen-Kernel: 2.6.27.42-0.1.1.xs5.6.0.44.111158xen
-CPUs: 2x Intel Xeon E5520

The've also confirmed me that they successfully booted a Debian 5.0.6 with 2.6.26-2-amd64.
So the problem must have been introduced in the meantime.


Given the fact, that 2.6.32 is for squeeze, and that Xen is rather common, this might even
qualify for being rc.

If you need any further help or so, please ask. My great ISP (Star-Hosting) is very
cooperative and they'll probably give me a test system for some time, if we need it.


Cheers,
Chris.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.36-heisenberg (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6.32-5-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.36     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.98.5     tools for generating an initramfs
pn  linux-base                    <none>     (no description available)
ii  module-init-tools             3.12-1     tools for managing Linux kernel mo

Versions of packages linux-image-2.6.32-5-amd64 recommends:
ii  firmware-linux-f 2.6.36-1~experimental.1 Binary firmware for various driver

Versions of packages linux-image-2.6.32-5-amd64 suggests:
pn  grub | lilo                   <none>     (no description available)
pn  linux-doc-2.6.32              <none>     (no description available)

Attachment: screen.png
Description: PNG image


--- End Message ---
--- Begin Message --- 
Christoph Anton Mitterer wrote:

> Unfortunately it turned out, that my ISP had to but that respective
> cluster into production now, and was therefore not longer able to play
> around very much.
[...]
> So I guess you might close the bug, at least from my side there's not much
> more I can to for debugging/tracing :-(

Ok, closing.  But we'd be happy to revisit this if you learn more
about it.

Thanks for the update,
Jonathan

--- End Message ---
Reply to: