found 531090 2.6.30-1-486
notfound 531090 2.6.22-2-486
thanks
This also happens with 2.6.30-1-486. However after resume, there's a
series of kernel oopses on the console, which unfortunately didn't go
to any logfile (0 pointer dereference in the kernel), directly after
reinitialization of opl3sa2.
Also it appears that other subsystems of the kernel stopped working
properly as well, since I wasn't able to 'less /var/log/syslog' and
reboot (I had to alt-sysrq-sync/umount and then hold the off-switch
for 4 seconds).
So this is a lot worse with 2.6.30 than with 2.6.29.
Since I had no other way of capturing those logs, I took a series of
actual photographs of the kernel messages on the console. Please tell
me if you want to look at them. And of course I'll happily provide any
other information that might be helpful.
Looks like I'll be downgrading to 2.6.22 or the highest kernel that
does not exhibit this bug.
Kind regards
Friedel
--
Friedrich Delgado Friedrichs <frie...@nomaden.org>
TauPan on Ircnet and Freenode ;)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
