I had the same problem with the kernel from unstable (2.6.29-1-686 2.6.29-3), but it went away after a couple of dist-upgrades, non of which touched the kernel package, which means that it's some userspace tool that caused this problem.
Now that I can't replicate this bug I can't pinpoint it to an individual package. If anyone still has this bug on their system, a way to trace it down would be to upgrade to most recent unstable, installing new packages one by one. I'm not sure if you would also need to reboot after each package. -- Dmitry Borodaenko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
