Hi guys,
When I log on after hibernating my Debian 11, the option About in Settings panel (gnome-control-center) does not work. If I click on the About section, my laptop stops working.
Anyone knows how can I fix this bug?
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Gnome freeze after hibernation with hybrid graphic
-
- Posts: 44
- Joined: 2019-08-07 17:49
- Has thanked: 1 time
Gnome freeze after hibernation with hybrid graphic
Last edited by pedronovaes on 2021-09-09 12:06, edited 1 time in total.
-
- Global Moderator
- Posts: 2966
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: Bug after hibernation
Hello,pedronovaes wrote: ↑2021-09-08 01:26 When I log on after hibernating my Debian 11, the option About in Settings panel (gnome-control-center) does not work. If I click on the About section, my laptop stops working. Anyone knows how can I fix this bug?
What do you exactly mean with "stops working" ?
Does it freeze ?
Can you access to a textual console (pressing simultaneously CTRL ALT F1), anyway ?
Can you do a controlled shutdown with the REISUB [1] sequence ?
More information is needed to classify this as a "bug".
[1] https://en.wikipedia.org/wiki/Magic_SysRq_key
-
- Posts: 44
- Joined: 2019-08-07 17:49
- Has thanked: 1 time
Re: Bug after hibernation
Hello,
Seeing dmesg log, I received a lot of message like that:
By the end, I received this message in dmesg log:
Any idea?
Yes, first it appears the window with the option to Force quit or Wait, and second it freezes the screen.Does it freeze ?
Yes.Can you access to a textual console (pressing simultaneously CTRL ALT F1), anyway ?
Seeing dmesg log, I received a lot of message like that:
Code: Select all
nouveau 0000:02:00.0: fifo: PBDMA0: 00026000 [GPFIFO GPPTR PBPTR] ch 3 [007fad5000 systemd-logind[589]] subc 0 mthd 0000 data 00000000
Code: Select all
[ 259.823193] nouveau 0000:02:00.0: fifo: channel 5 [gst-plugin-scan[4593]] kick timeout
[ 259.823718] BUG: unable to handle page fault for address: fffffffffffffc00
[ 259.823719] #PF: supervisor read access in kernel mode
[ 259.823719] #PF: error_code(0x0000) - not-present page
[ 260.819181] Fixing recursive fault but reboot is needed!
-
- Global Moderator
- Posts: 2966
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: Bug after hibernation
Hello,
It looks like something related to the nouveau kernel module. It would be useful to analyze/ submit for analysis the complete journal log of a previous boot session finished with a system freeze after hibernation. You could be able to collect the log with the following steps:
- boot
- start graphical session
- hibernate
- resume from hibernation
- replicate malfunction
- shutdown from console with halt command
- reboot
- type the following command in a console as root user
The log will be in log.txt file
A detailed description of hardware info would be useful, too. You can use the inxi command for this.
It looks like something related to the nouveau kernel module. It would be useful to analyze/ submit for analysis the complete journal log of a previous boot session finished with a system freeze after hibernation. You could be able to collect the log with the following steps:
- boot
- start graphical session
- hibernate
- resume from hibernation
- replicate malfunction
- shutdown from console with halt command
- reboot
- type the following command in a console as root user
Code: Select all
journalctl -b -1 --no-pager > log.txt
A detailed description of hardware info would be useful, too. You can use the inxi command for this.
-
- Posts: 44
- Joined: 2019-08-07 17:49
- Has thanked: 1 time
Re: Bug after hibernation
Hello,
As my message contains more characters than this reply is possible, I paste the complete log message in this link: https://pastebin.pl/view/7d2c7039
As my message contains more characters than this reply is possible, I paste the complete log message in this link: https://pastebin.pl/view/7d2c7039
-
- Global Moderator
- Posts: 2966
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times
Re: Bug after hibernation
The log in the link does not contain info from the boot of the session and does not contain traces of a kernel driver malfunction or of suspend/resume activities.pedronovaes wrote: ↑2021-09-08 17:25 As my message contains more characters than this reply is possible, I paste the complete log message in this link: https://pastebin.pl/view/7d2c7039
If you wish, you can compress a new log and attach to a next message as a compressed file. For example, you can use a command like this to collect all journal log generated today between 08 AM and 9 PM:
Code: Select all
journalctl --since="2021-09-08 08:00:00" --until="2021-09-08 21:00:00" --no-pager | gzip -9 > log.gz
Last edited by Aki on 2021-09-08 19:05, edited 2 times in total.
-
- Posts: 44
- Joined: 2019-08-07 17:49
- Has thanked: 1 time
Re: Bug after hibernation
Hello,
As you mentioned before the problem seems to be related to the nouveau kernel module, I tried to install the packages Bumblebee and Primus (following this tutorial https://wiki.debian.org/Bumblebee).
After reboot, the problem was fixed.
Thank you so much!
As you mentioned before the problem seems to be related to the nouveau kernel module, I tried to install the packages Bumblebee and Primus (following this tutorial https://wiki.debian.org/Bumblebee).
After reboot, the problem was fixed.
Thank you so much!
-
- Global Moderator
- Posts: 2966
- Joined: 2014-07-20 18:12
- Location: Europe
- Has thanked: 73 times
- Been thanked: 405 times