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)

Christoph Anton Mitterer <calestyo@scientia.net> writes:
> 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.

Thanks for reporting this bug. Can you please save the save the state
of the hung domU by executing

xm dump-core $DOMAIN $DOMAIN.dump

on dom0 (you probably need your ISP to run it for you) and then

apt-get install linux-image-2.6.32-5-amd64-dbg crash

on some squeeze machine (even your domU booted with another kernel is
ok) so that you can say

crash -e emacs /usr/lib/debug/boot/vmlinux-2.6.32-5-amd64 $DOMAIN.dump

and then invoke at least the following commands in the "crash>"
prompt:

sys
ps
foreach bt -f
foreach bt -F




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 84fwv4cd94.fsf@sauna.l.org">http://lists.debian.org/84fwv4cd94.fsf@sauna.l.org

Christoph Anton Mitterer <calestyo@scientia.net> writes:
> Package: linux-image-2.6.32-5-amd64
> Version: 2.6.32-27
> Severity: important

Can you also attach the output of "xm info" from the dom0 to the bug
report? 2.6.32-27 boots here as a domU just fine when I also use
2.6.32-27 as a dom0 :-)



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 847hggc7zh.fsf@sauna.l.org">http://lists.debian.org/847hggc7zh.fsf@sauna.l.org

Hi.

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.

Also, the commands you've mentioned seemed to not have been available
there.


So I guess you might close the bug, at least from my side there's not much
more I can to for debugging/tracing :-(


Cheers,
Chris.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4096ed83270ee4ea2e58cfdb799135c3@imap.dd24.net">ht tp://lists.debian.org/4096ed83270ee4ea2e58cfdb799135c3@imap.dd24.net

Christoph Anton Mitterer <calestyo@scientia.net> writes:
> 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.

That's unfortunate. Do they advertise support for hosting debian in a
xen publicly?




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 8462vofmjo.fsf@sauna.l.org">http://lists.debian.org/8462vofmjo.fsf@sauna.l.org