On Fri, 2012-05-25 at 09:46 +0200, Olaf Rühenbeck wrote: > On Thu, 24 May 2012 16:21:49 +0100 > Ben Hutchings <ben@decadent.org.uk> wrote: > > > On Thu, May 24, 2012 at 04:30:02PM +0200, Olaf Ruehenbeck wrote: > > > Package: general > > > Severity: important > > > Tags: squeeze > > [...] > > > > The correct package name to use when reporting a bug in the kernel > > is 'linux-image-' followed by the version string reported by > > 'uname -r', so in this case it would be 'linux-image-2.6.32-5-amd64'. > > Which version of this package do you have installed? > > > > Can you check that the package is properly installed, by running > > 'debsums -c linux-image-2.6.32-5-amd64'? (You might need to install > > debsums first.) > > > > Ben. > > > > I'm sorry, this is my first debian bug report. I will try to behave in > the future :) > > The installed version of the kernel package is 2.6.32-41squeeze2. > > root@Blackmagic:/home/xxxxxx# debsums -c linux-image-2.6.32-5-amd64 > root@Blackmagic:/home/xxxxxx# echo $? > 0 So it seems to be installed OK, and as you've seen the same problem on multiple machines it's probably not due to defective hardware. Are you using any out-of-tree modules? (I.e. kernel modules that aren't part of the kernel package.) Can you check whether this is fixed in the current stable version (2.6.32-45)? Then if it isn't, test Linux 3.2 from testing, unstable or sqeueeze-backports? Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else.
Attachment:
signature.asc
Description: This is a digitally signed message part