Bug 117581
| Summary: | Celsius H265: suspend does not bring up console unless no_console_suspend is given | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Elmar Stellnberger (estellnb) |
| Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
| Status: | ASSIGNED --- | ||
| Severity: | normal | CC: | marci_r, rui.zhang |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.6.0-rc6-ARCH-00006-g7d92f59 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
dmesg
nvapeek 0x610000 0x20000 - 4.7.0-ARCH-13902-gd491e80 without no_console_suspend and without nouveau module loaded, after bootup nvapeek 0x610000 0x20000 - 4.7.0-ARCH-13902-gd491e80 without no_console_suspend and without nouveau module loaded, after s2ram |
||
Perhaps you may also want to have a look at the corresponding bug for nouveau at https://bugs.freedesktop.org/show_bug.cgi?id=93887 (f.i. I have uploaded the video bios rom there). Please also try to notify me about changes regarding this bug so that I can double re-test for the kernel alone and then for nouveau in order to exclude any interferencces. It seems that suspend works properly on your platform, except that the graphics driver fails to bring the screen back. It could be caused by the nouveau related kernel parameters you're using, but anyway, I think we need graphics experts here. Bug reassigned. With 4.7.0-ARCH-13902-gd491e80 and no_console_suspend the LVDS just did not come up again under init=/bin/bash (i.e. it stayed black while it was still possible to enter commands blindly) - basically a regression when testing the bare kernel (tested with a Celsius H270); interestingly when I tested with nouveau the LVDS came up normally.
Could it be that these problems are related to the following:
> dmesg | grep -i -e warn -e error
[ 8.350192] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20160422/utad
[ 8.356598] ACPI Warning: SystemIO range 0x00000000000011B0-0x00000000000011BF conflicts with OpRegion 0x0000000000001180-0x00000000000011BB (\GPIO) (20160422/utad
[ 8.363088] ACPI Warning: SystemIO range 0x0000000000001180-0x00000000000011AF conflicts with OpRegion 0x0000000000001180-0x00000000000011BB (\GPIO) (20160422/utad
Created attachment 229421 [details]
nvapeek 0x610000 0x20000 - 4.7.0-ARCH-13902-gd491e80 without no_console_suspend and without nouveau module loaded, after bootup
Created attachment 229431 [details]
nvapeek 0x610000 0x20000 - 4.7.0-ARCH-13902-gd491e80 without no_console_suspend and without nouveau module loaded, after s2ram
at least tested to work fine when nouveau is loaded since commit 65ea11ec6a82b1d44aba62b59e9eb20247e57c6e (Ville Syrjälä - x86/hweight: Don't clobber %rdi); gonna test that accurately tomorrow or so; see also: bug 153371, bug 153361, freedesktop bug 93887 (https://bugs.freedesktop.org/show_bug.cgi?id=93887). I guess it would already be resolved but Bug 155511 inhibits me from testing that out correctly. |
Created attachment 215141 [details] dmesg There is a suspend issue with my Celsius H265/H270 notebook. The screen stays black after suspend though the machine comes up well and can still execute commands entered via keyboard. The no_console_suspend parameter can resolve this issue the screen still turning black on suspend. cmdline: BOOT_IMAGE=/boot/vmlinuz-custom root=/dev/disk/by-label/arch ro resume=/dev/disk/by-label/swap nouveau.hdmimhz=225 debug ignore_loglevel log_buf_len=1M modeset=0 nouveau.blacklist=1 init=/bin/bash log: see for the attachement