Hi Moritz, I am surprised that the Debian bug submitting program did not automatically attach such a vital bit of information!
I do believe to have upgraded the kernel in the meantime, simply by installing security upgrades, so I am probably no longer running that exact version. Right now, I am running: 2.6.26-2-openvz-amd64 #1 SMP Sun Jul 26 21:18:21 UTC 2009 x86_64 GNU/Linux So - it probably was the version that was available on the Debian repositories before this one. Is there a reliable way of making sure? The contents of my /boot directory are: ll /boot/ total 19M lrwxrwxrwx 1 root root 1 2009-06-03 11:20 boot -> . -rw-r--r-- 1 root root 302K 2009-02-18 16:13 coffee.bmp -rw-r--r-- 1 root root 84K 2009-07-27 00:46 config-2.6.26-2-openvz-amd64 lrwxrwxrwx 1 root root 15 2009-06-03 11:20 debian.bmp -> /boot/sarge.bmp -rw-r--r-- 1 root root 151K 2009-02-18 16:13 debianlilo.bmp drwxr-xr-x 3 root root 4.0K 2009-08-06 01:09 grub -rw-r--r-- 1 root root 7.5M 2009-08-06 01:09 initrd.img-2.6.26-2-openvz-amd64 -rw-r--r-- 1 root root 7.5M 2009-06-28 08:50 initrd.img-2.6.26-2-openvz-amd64.bak drwx------ 2 root root 16K 2009-06-03 11:17 lost+found -rw-r--r-- 1 root root 24K 2009-02-18 16:13 sarge.bmp -rw-r--r-- 1 root root 24K 2009-02-18 16:13 sid.bmp -rw-r--r-- 1 root root 1.2M 2009-07-27 00:46 System.map-2.6.26-2-openvz-amd64 -rw-r--r-- 1 root root 1.7M 2009-07-27 00:45 vmlinuz-2.6.26-2-openvz-amd64 Does this mean the previous version was also 2.6.26-2? Hope this helps! Rainer ----- "Moritz Muehlenhoff" <[email protected]> wrote: > On Mon, Jul 06, 2009 at 06:56:00AM +0200, Jeremy Lainé wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > reassign 533620 linux-2.6 > > thanks > > > > The problem described in bug 533620 is a kernel bug, so I am > re-assigning it to the > > linux-2.6 package. What version of the kernel were you running when > you experienced the crash? > > Rainer, which kernel was used? > > Cheers, > Moritz -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
