Proxecto: | Trisquel |
Versión: | 6.0 |
Componente: | Programs |
Categoría: | informe de erro |
Prioridade: | critical |
Asignado: | Sen asignar |
Estado: | active |
On wakeup from standby mode, the login screen appears (query the user's password). So far so good … everything looks good.
But mouse has frozen and keyboard input is not possible (off).
Within about 10-20 seconds the screen has frozen and the whole system crashed/be down.
Since my upgrade to Trisquel 6.0 via CD, his was not an issue with Trisquel 5.5 (amd64).
You need to specify hardware for this bug to have any meaning. Include the output of lspci -nn
Here's the output (lspci -nn):
Any peripheral devices, like wireless perhaps or something else?
Does this happen everytime or happened once?
Can you switch to VT1?
Can you use https://en.wikipedia.org/wiki/Magic_sysrq (REISUB)
Anything in the logs?
See lsusb output:
For me the same problem occurred as previously reported in https://trisquel.info/en/issues/7980 ,
I meant no harm by it (thought I had done something wrong), so I tried / installed 'GNOME Desktop Environment'.
You can’t log in into _any_ environment ('gnome-classic', 'gnome', 'ubuntu').
Further tested:
Login screen -> Standby mode -> Login screen => Same difference.
(Q) > Does this happen everytime or happened once?
Everytime.
(Q) > Can you switch to VT1?
I don’t know VT1.
(Q) > Can you use https://en.wikipedia.org/wiki/Magic_sysrq (REISUB)
Yes, REISUB works within short window of time (about 20-25 seconds) but --no matter which-- no key input is displayed and machine seems frozen.
After short time window, the system crashed completly: no REISUB.
(Q) > Anything in the logs?
Not really, sorry. There are no errors. What should I look for?
Can you remove any peripherals? Disconnect all you can and then try.
You could also try a newer kernel from http://jxself.org/linux-libre/ (seems to be down at the moment)
If that doesn't help, one more thing you could try is removing as many kernel modules as possible before suspend. Note that if module A is used by B, then A cannot be removed before B is removed. You can list modules with lsmod and remove them with sudo rmmod MODULENAME.
First of all, a big "Thank you" for supporting, Lembas!
> Can you remove any peripherals? Disconnect all you can and then try.
No, I can’t.
The previously described seems to base on (jxself’s) linux-libre64-3.8.x-gnu (all versions, currently 3.8.6).
There’s _no_ problem with (jxself’s) linux-libre64-3.7.x-gnu (all versions, currently 3.7.10), and also not with Trisquel’s current linux-libre 3.2.0.38.46+6.0trisquel1. (R-E-S-U-B, nice hint). ;)
(I think many current bug reports based on the same linux-libre 3.8 kernel.)