[Bug 93555] Errors on lid close/open, black screen.

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jun 8 12:31:40 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=93555

--- Comment #7 from bruno.pagani at ens-lyon.org ---
Sorry for the huge delay, I finally didn’t have anytime to look into kernel
compiling, but 4.6 just landed in ArchLinux.

The good news is that “i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has
bogus alignment” are gone.

The bad news is that the screen is still black on lid open. Of course, any key
or mouse move bring it back to life, but that’s still not ideal.

Also, now that I have psr by default, there is a difference if I don’t disable
it: instead of my desktop, after escaping the black screen, I face the screen
state at session opening — that is, my login manager (SDDM) with my password in
(bullet-style of course) and validated, with the clock time of the actual
session opening. Here again, any key press returns to the normal situation —
but that’s definitively not what should be the normal behaviour.

The log excerpt haven’t changed outside of the i915 lines being gone, but here
they are just in case (psr doesn’t play any role here):

[  336.913452] pci_bus 0000:04: Allocating resources
[  336.913465] pci_bus 0000:06: Allocating resources
[  336.913478] pcieport 0000:00:1c.2: bridge window [io  0x1000-0x0fff] to [bus
06] add_size 1000
[  336.913480] pcieport 0000:00:1c.2: bridge window [mem 0x00100000-0x000fffff
64bit pref] to [bus 06] add_size 200000 add_align 100000
[  336.913485] pci_bus 0000:07: Allocating resources
[  336.913494] pcieport 0000:00:1c.3: bridge window [io  0x1000-0x0fff] to [bus
07] add_size 1000
[  336.913496] pcieport 0000:00:1c.3: bridge window [mem 0x00100000-0x000fffff
64bit pref] to [bus 07] add_size 200000 add_align 100000
[  336.913500] pcieport 0000:00:1c.2: res[15]=[mem 0x00100000-0x000fffff 64bit
pref] res_to_dev_res add_size 200000 min_align 100000
[  336.913502] pcieport 0000:00:1c.2: res[15]=[mem 0x00100000-0x002fffff 64bit
pref] res_to_dev_res add_size 200000 min_align 100000
[  336.913503] pcieport 0000:00:1c.3: res[15]=[mem 0x00100000-0x000fffff 64bit
pref] res_to_dev_res add_size 200000 min_align 100000
[  336.913504] pcieport 0000:00:1c.3: res[15]=[mem 0x00100000-0x002fffff 64bit
pref] res_to_dev_res add_size 200000 min_align 100000
[  336.913505] pcieport 0000:00:1c.2: res[13]=[io  0x1000-0x0fff]
res_to_dev_res add_size 1000 min_align 1000
[  336.913507] pcieport 0000:00:1c.2: res[13]=[io  0x1000-0x1fff]
res_to_dev_res add_size 1000 min_align 1000
[  336.913508] pcieport 0000:00:1c.3: res[13]=[io  0x1000-0x0fff]
res_to_dev_res add_size 1000 min_align 1000
[  336.913509] pcieport 0000:00:1c.3: res[13]=[io  0x1000-0x1fff]
res_to_dev_res add_size 1000 min_align 1000
[  336.913516] pcieport 0000:00:1c.2: BAR 15: assigned [mem
0xcf600000-0xcf7fffff 64bit pref]
[  336.913531] pcieport 0000:00:1c.3: BAR 15: assigned [mem
0xcf800000-0xcf9fffff 64bit pref]
[  336.913534] pcieport 0000:00:1c.2: BAR 13: assigned [io  0x3000-0x3fff]
[  336.913535] pcieport 0000:00:1c.3: BAR 13: assigned [io  0x4000-0x4fff]
[  336.982273] pci_bus 0000:02: Allocating resources
[  338.487575] pci_bus 0000:04: Allocating resources
[  338.487589] pci_bus 0000:06: Allocating resources
[  338.487613] pci_bus 0000:07: Allocating resources
[  338.555659] pci_bus 0000:02: Allocating resources

[  381.539354] pci_bus 0000:04: Allocating resources
[  381.539370] pci_bus 0000:06: Allocating resources
[  381.539389] pci_bus 0000:07: Allocating resources
[  381.610463] pci_bus 0000:02: Allocating resources
[  382.993490] pci_bus 0000:04: Allocating resources
[  382.993513] pci_bus 0000:06: Allocating resources
[  382.993528] pci_bus 0000:07: Allocating resources
[  383.063902] pci_bus 0000:02: Allocating resources

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160608/fbae8b80/attachment.html>


More information about the intel-gfx-bugs mailing list