>Does the screen go blank, or is there still text/images on the screen
>at that point?
As it happens, the picture on the screen gets frozen like a screenshot. Also, the last ~500ms of sound are looped, I think it is the sound chip buffer. Looping is going on for some minutes, then it is quiet.
>Has this always been this way, or did it start after an upgrade (i.e.,
>is it a regression)? If it is a regression, what were the last
>working and first broken versions?
It is the completely fresh installation, made with unofficial Debian 6.0.3 AMD64 netinstall with firmware, downloaded from cdimage.debian.org and updated. The hardware was working well for 1 year long with Ubuntu. But I can remember, that ~2 years ago on 2 ubuntu versions (xx.04 AND xx.10) I had the same symptoms. Sorry, but I do not know any more what kernel version wehe there.
>Results from testing with v3.x from sid or experimental would also be
>very useful, so we can get help from upstream if it is still broken
>there or find a fix to backport if it is fixed. (The only packages
>from outside squeeze aside from linux-image itself that should be
>needed to test are initramfs-tools and linux-base, both available from
>squeeze-backports.)
Do I understand right: I should write the squeeze-backports source to the apt-list and install 3 packages, linux-image, linux-base and initframs-tools in version 3.x? Do I need something extra to do, aside from uninstalling of the 2.6.x-kernel packages?
>It would be possible to test for that by blacklisting the driver and
>seeing if it still happens. (Likewise for other drivers if you have
>suspicions.)
The big problem what we here have, there is no trigger for reproducing. I am suspicious about sound, WiFi, video, adobe-flash too. Because I am often using this things and logicaly it crashes when I'm watching something on youtube, for example. Yesterday as I was trying to catch the kernel log, it was frozen 2 times. The first time I had no log, because the LAN link was unstable for no reason and it happened only 2-3 minutes after booting. The second time as I got the log, it took several hours. This means, I will of course make a test with 3.x kernel, but cann not guarantee after 2 days of testing that the bug is gone. My question is, if there is a way to force the kernel to give more debugging info.
Thank you for helping.
Regards,
Eugen
___________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192