|
Bugzilla – Full Text Bug Listing |
| Summary: | Laptop with Intel+Nvidia hybrid graphics won't suspend after hibernation | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Iakov Karpov <srid> |
| Component: | Kernel | Assignee: | Takashi Iwai <tiwai> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | bjoernv, srid, tiwai |
| Version: | Leap 15.0 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Log of kernel-vanilla + drm.debug=0x0e
Log of kernel-vanilla + nouveau.debug=debug Log of kernel-desktop from home:tiwai:bsc1094751 repo Log of kernel-default form Kernel:stable repo Error message of kernel 4.12.14-lp150.12.13-default kernel error message |
||
|
Description
Iakov Karpov
2018-05-27 17:49:58 UTC
Could you check the kernel in OBS home:tiwai:bsc1094751 repo? Does it still cause the issue? Created attachment 772162 [details] Log of kernel-vanilla + nouveau.debug=debug (In reply to Takashi Iwai from comment #1) > Could you check the kernel in OBS home:tiwai:bsc1094751 repo? > Does it still cause the issue? I did check with home:tiwai:bsc1094751 repo, it had that issue, and vanilla has this problem too, so I think it's a different problem than bug 1094751 There is no blank screens or anything, laptop would just fail to suspend after you wake it up from hibernation. I'm not sure how to reproduce it reliably though. I only know it happens after hibernation. Could you give the kernel messages with the kernel from home:tiwai:bsc1094751, too? Also, are you using docking station? The symptom appears similar as the upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=90682 It mentioned about DP-MST. Created attachment 772165 [details] Log of kernel-desktop from home:tiwai:bsc1094751 repo (In reply to Takashi Iwai from comment #3) > Could you give the kernel messages with the kernel from > home:tiwai:bsc1094751, too? Sure thing. I have figured it refuses to suspend on the second time after hibernation. And just in case, I tried starting kernel with no video=VGA-2:d pcie_aspm=force parameters, no effect. (In reply to Takashi Iwai from comment #4) > Also, are you using docking station? > > The symptom appears similar as the upstream bug > https://bugs.freedesktop.org/show_bug.cgi?id=90682 > > It mentioned about DP-MST. There are no docking station for that model. But for some reason it has phantom VGA port attached to nvidia card, that's why I have to use video=VGA-2:d Thanks, it shows the very same code path, so it's the same crash consistently. FWIW, the situation is like below. An error was seen before the Oops happened at suspending at the second time: nouveau 0000:01:00.0: DRM: suspending display... nouveau 0000:01:00.0: DRM: evicting buffers... nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle... nouveau 0000:01:00.0: fifo: PBDMA0: 00008000 [] ch 0 [003fe12000 DRM] subc 0 mthd 0000 data 00000000 nouveau 0000:01:00.0: DRM: failed to idle channel 0 [DRM] The driver returned back and tried to resume again: nouveau 0000:01:00.0: DRM: resuming display... nouveau 0000:01:00.0: invalid power transition (from state 4 to 3) ... and the power state change was inconsistent. Now, suspending again, and failed with "channel 0" (but no fifo error message at this time). Resuming again, though, caused an Oops. nouveau 0000:01:00.0: DRM: suspending console... nouveau 0000:01:00.0: DRM: suspending display... nouveau 0000:01:00.0: DRM: evicting buffers... nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle... nouveau 0000:01:00.0: DRM: failed to idle channel 0 [DRM] nouveau 0000:01:00.0: DRM: resuming display... BUG: unable to handle kernel paging request at ffff8805393d8ffc IP: evo_wait+0x56/0x120 [nouveau] .... And I forget whether you've already test the recent upstream kernel, e.g. the kernel in OBS Kernel:stable repo. Did you try that already? If the issue happens with 4.16.x, it should be reported to upstream. e.g. bugzilla.freedesktop.org category DRI/Nouveau. Feel free to put me (tiwai@suse.de) there. Created attachment 772211 [details] Log of kernel-default form Kernel:stable repo (In reply to Takashi Iwai from comment #7) > And I forget whether you've already test the recent upstream kernel, e.g. > the kernel in OBS Kernel:stable repo. Did you try that already? > > If the issue happens with 4.16.x, it should be reported to upstream. > e.g. bugzilla.freedesktop.org category DRI/Nouveau. > Feel free to put me (tiwai@suse.de) there. I tried the kernel:stable repo, laptop still won't suspend, but kernel log is a little bit different this time. However, I'm not sure if I can make a legit report for upstream, because kernel-vanilla 4.16 fails to resume from hibernation for some reason. It's fine to report to upstream as long as the kernel-default in Kernel:stable also shows the issue. TW kernel (i.e. the one in Kernel:stable) has very few backport patches, and very close to the upstream as is. 4.16.x kernel seems showing the very same symptom; it gets a fifo PBDMA0 error (although it shows repeatedly), then Oops at resume in evo_wait(). So, it'd be really better to report to upstream. You can give the kernel messages booted with drm.debug=0x0e as well, which shows more debug messages. Created attachment 779681 [details] Error message of kernel 4.12.14-lp150.12.13-default Still happening with latest openSUSE Leap 15.0 kernel. Also, I noticed that after that nvidia chip won't shut down until you unplug all power sources (battery and AC adapter). Upstream bug (https://bugs.freedesktop.org/show_bug.cgi?id=106795) never got a reply. Could you check whether Leap 15.1 works in this regard? It should have been addressed there. (In reply to Takashi Iwai from comment #11) > Could you check whether Leap 15.1 works in this regard? It should have been > addressed there. It does not work. In fact, it got worse: dmesg is flooded with nouveau error messages like this: [ 154.861853] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 [ 154.861868] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 [ 154.861883] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 [ 154.861898] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 [ 154.861913] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 [ 154.861928] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 [ 154.861943] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 [ 154.861958] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 [ 154.861973] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 [ 154.861989] nouveau 0000:01:00.0: fifo: PBDMA0: 80000000 [] ch 2 [003fd71000 X[5243]] subc 0 mthd 0000 data 00000000 In a couple of minutes I got a gigabyte of those. Then it's very likely an upstream problem, as Leap 15.1 already got most of updates for nouveau. To be sure, try the 5.1.x kernel from Kernel:stable repo. If this still doesn't work, continue on the upstream bug tracker, bugs.freedesktop.org. If 5.1 kernel works, we may still have some chance for a fix backport to Leap 15.1. Created attachment 809571 [details] kernel error message (In reply to Takashi Iwai from comment #13) > Then it's very likely an upstream problem, as Leap 15.1 already got most of > updates for nouveau. > To be sure, try the 5.1.x kernel from Kernel:stable repo. If this still > doesn't work, continue on the upstream bug tracker, bugs.freedesktop.org. > If 5.1 kernel works, we may still have some chance for a fix backport to > Leap 15.1. 5.1.16 is also affected, however it's a little bit more informative (see attachment). I've reported this upstream a year ago, but they seem to ignore it. Just try to ping again the upstream bug tracker. Developers are overloaded, but active reports give more chance for the attention. Could you check whether the problem persists with Leap 15.2? It goes to 5.3 kernel (with a bunch of backports), so we have a better chance now. (In reply to Takashi Iwai from comment #16) > Could you check whether the problem persists with Leap 15.2? It goes to 5.3 > kernel (with a bunch of backports), so we have a better chance now. I've installed 15.2 kernel on top of my 15.1, problem still persists. It's a pity that nouveau isn't maintained well enough in many aspects. Could you try the 5.6.y kernel? Just to make sure. (In reply to Takashi Iwai from comment #18) > It's a pity that nouveau isn't maintained well enough in many aspects. > > Could you try the 5.6.y kernel? Just to make sure. 5.6.13 doesn't work either Since this is an old distro issue, I close now as WONTFIX. If you have the same problem with the latest openSUSE versions, please reopen. Thanks. |