Bug 1356115 - X is broken, suspend is broken
Summary: X is broken, suspend is broken
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-13 12:44 UTC by Hubert Figuiere
Modified: 2017-08-08 15:33 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 15:33:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hubert Figuiere 2016-07-13 12:44:24 UTC
Description of problem:
X is broken, suspend is broken.

After rebooting into kernel 4.6.3-300 as installed by update, suspend cause the X session to crash.
Also the start of the X session is rocky. When gnome-shell is started, the mouse pointer of gdm is still here, not moving. The actual mouse pointer of the session is invisible (albeit moving) and will appear once I open my first window (like the terminal).

This NEVER happened with the previous kernels.

Version-Release number of selected component (if applicable):
4.6.3-300.fc24

How reproducible:
Always with that kernel version.

Steps to Reproduce:
1. Install kernel 4.6.3 from fedora updates
2. Reboot and start a standard GNOME session
3.

Actual results:
see above.

Expected results:
Suspend works, no "ghost" cursor, etc.
This works with kernel 4.5.7-300.fc24.x86_64

Additional info:
video driver is nouveau (NV5)

* OS Release (cat /etc/*-release | uniq):
     Fedora release 24 (Twenty Four)
     NAME=Fedora
     VERSION="24 (Workstation Edition)"
* CPU Model
    4  Intel(R) Core(TM) i5 CPU       M 520  @ 2.40GHz
     

     01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 330M] (rev a2)

* DRM Information (journalctl -k -b | grep -o 'kernel:.*drm.*$' | cut -d ' ' -f 2-
         ):
     [drm] Initialized drm 1.1.0 20060810
     [drm] Memory usable by graphics device = 2048M
     [drm] Replacing VGA console driver
     [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
     [drm] Driver supports precise vblank timestamp query.
     [drm] failed to find VBIOS tables
     [drm] RC6 disabled, disabling runtime PM support
     [drm] Initialized i915 1.6.0 20151218 for 0000:00:02.0 on minor 0
     [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
     [drm] Cannot find any crtc or sizes - going 1024x768
     i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
     [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
     [drm] Driver supports precise vblank timestamp query.
     [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1

* GL Support (glxinfo | grep -E "OpenGL version|OpenGL renderer"):
     OpenGL renderer string: Gallium 0.4 on NVA5
     OpenGL version string: 3.0 Mesa 12.0.0

machine: Apple Inc. MacBookPro6,2/Mac-F22586C8

Comment 1 Hubert Figuiere 2016-07-13 13:08:38 UTC
According to DRM there is the Intel GPU too on the machine, but is not what is used by stock Fedora. It is definitely nouveau. The DRM information above is from the currently running kernel, that do work as advertised.

Comment 2 Hubert Figuiere 2016-07-14 02:06:35 UTC
Also I wanted to add that this cause the OSD for the screen brightness to not work (pressing F1-F2). The one for the keyboard backlight do, though.

No problem with the older kernel.

Comment 3 Hubert Figuiere 2016-09-07 01:58:03 UTC
Still happen with kernel 4.7.2-201.fc24 and xorg-x11-drv-nouveau 1.0.12-4.fc24

Comment 4 Hubert Figuiere 2016-10-08 16:47:15 UTC
On kernel 4.7.5 the GNOME session (with X) it still fails badly... actually never starts (black scree). On the other hand the Wayland do work, which is progress...

Comment 5 Hubert Figuiere 2016-10-12 04:35:31 UTC
With 4.7.6-200.fc24.x86_64, the problem is like in comment 0. But Wayland works which is progress.

Comment 6 Hubert Figuiere 2016-10-20 00:48:07 UTC
Using kernel 4.8.1-1.fc25.x86_64 from Fedora 25. Wayland works, but X even less. I had to actually hard reboot the machine. Nothing displayed.

Comment 7 Hubert Figuiere 2016-10-29 01:32:35 UTC
On 4.8.4-301.fc25.x86_64:

X11 work, and since now X11 is forced back because the machine had two GPU (Intel + Nvidia) I can't work around with Wayland.
But then suspend still cause the whole thing to crash and forces me to reboot.

And now I have TWO screens shown in control-center, even though this is a laptop connected to nothing.

Comment 8 Bastien Nocera 2016-11-02 12:15:32 UTC
Reassigning to the Intel driver. I see this on a similar MacBook Pro with Intel+AMD GPUs.

Comment 9 Hubert Figuiere 2017-01-19 16:51:11 UTC
Comment 7 still apply with 4.9.3-200.fc25.x86_64

At that point the Intel driver failed (i915 kernel module is still loaded though). From the boot logs:

[   13.996684] intel ips 0000:00:1f.6: CPU TDP doesn't match expected value (found 25, expected 29)
[   13.999323] intel ips 0000:00:1f.6: enabling device (0000 -> 0002)
[   14.003601] bcma: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x22, class 0x0)
[   14.006167] bcma: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x17, class 0x0)
[   14.009188] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled until i915 loads
[   14.009997] bcma: bus0: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x0F, class 0x0)
[   14.047526] genirq: Flags mismatch irq 0. 00000080 (ips) vs. 00015a00 (timer)
[   14.049872] CPU: 0 PID: 855 Comm: systemd-udevd Not tainted 4.9.3-200.fc25.x86_64 #1
[   14.052251] Hardware name: Apple Inc. MacBookPro6,2/Mac-F22586C8, BIOS    MBP61.88Z.0057.B11.1509232013 09/23/15
[   14.054445]  ffffa2f601a0b9e8 ffffffffa63f3ddd ffff89fa42e8b100 00000000fffffff0
[   14.056345]  ffffa2f601a0ba40 ffffffffa6101f37 0000000000000246 ffff89fa4701b49c
[   14.058837]  ffff89fa420c5c98 000000002c3f82c9 ffff89fa42e8b100 0000000000000000
[   14.060133] bcma: bus0: Bus registered
[   14.064021] Call Trace:
[   14.066661]  [<ffffffffa63f3ddd>] dump_stack+0x63/0x86
[   14.069291]  [<ffffffffa6101f37>] __setup_irq+0x5e7/0x640
[   14.071921]  [<ffffffffa610216b>] request_threaded_irq+0x10b/0x1a0
[   14.074560]  [<ffffffffc0315f27>] ips_probe+0x3a7/0x6a0 [intel_ips]
[   14.077195]  [<ffffffffa6448b85>] local_pci_probe+0x45/0xa0
[   14.079819]  [<ffffffffa6449fd3>] pci_device_probe+0x103/0x150
[   14.082397]  [<ffffffffa654a753>] driver_probe_device+0x223/0x430
[   14.085007]  [<ffffffffa654aa3f>] __driver_attach+0xdf/0xf0
[   14.087595]  [<ffffffffa654a960>] ? driver_probe_device+0x430/0x430
[   14.090203]  [<ffffffffa654813c>] bus_for_each_dev+0x6c/0xc0
[   14.092802]  [<ffffffffa6549e9e>] driver_attach+0x1e/0x20
[   14.095380]  [<ffffffffa65498d0>] bus_add_driver+0x170/0x270
[   14.097618]  [<ffffffffc0346000>] ? 0xffffffffc0346000
[   14.099945]  [<ffffffffa654b360>] driver_register+0x60/0xe0
[   14.102451]  [<ffffffffc0346000>] ? 0xffffffffc0346000
[   14.104758]  [<ffffffffa64484ac>] __pci_register_driver+0x4c/0x50
[   14.104763]  [<ffffffffc034601e>] ips_pci_driver_init+0x1e/0x1000 [intel_ips]
[   14.104766]  [<ffffffffa6002190>] do_one_initcall+0x50/0x180
[   14.104769]  [<ffffffffa620efa1>] ? __vunmap+0x81/0xd0
[   14.104773]  [<ffffffffa622f2b9>] ? kmem_cache_alloc_trace+0x159/0x1b0
[   14.104777]  [<ffffffffa61c017a>] ? do_init_module+0x27/0x1ef
[   14.104779]  [<ffffffffa61c01b2>] do_init_module+0x5f/0x1ef
[   14.104782]  [<ffffffffa612fe01>] load_module+0x25b1/0x2980
[   14.104784]  [<ffffffffa612c6e0>] ? __symbol_put+0x60/0x60
[   14.104786]  [<ffffffffa6130343>] SYSC_init_module+0x173/0x190
[   14.104788]  [<ffffffffa613047e>] SyS_init_module+0xe/0x10
[   14.104790]  [<ffffffffa6003c17>] do_syscall_64+0x67/0x180
[   14.104794]  [<ffffffffa681bcab>] entry_SYSCALL64_slow_path+0x25/0x25
[   14.104878] intel ips 0000:00:1f.6: request irq failed, aborting
[   14.115351] wmi: Mapper loaded
[   14.167995] intel ips: probe of 0000:00:1f.6 failed with error -16
[   14.176528] ACPI: Smart Battery System [SBS0]: Battery Slot [BAT0] (battery present)
[   14.193310] pci 0000:00:00.0: Intel HD Graphics Chipset
[   14.201197] pci 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[   14.205149] pci 0000:00:00.0: detected 32768K stolen memory
[   14.207710] [drm] Memory usable by graphics device = 2048M
[   14.214396] checking generic (c0030000 834000) vs hw (b0000000 10000000)
[   14.214399] [drm] Replacing VGA console driver
[   14.221161] input: bcm5974 as /devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1.2/1-1.2:1.2/input/input8
[   14.228267] media: Linux media interface: v0.10
[   14.237991] usbcore: registered new interface driver bcm5974
[   14.266101] Linux video capture interface: v2.00
[   14.273019] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   14.275138] [drm] Driver supports precise vblank timestamp query.
[   14.277265] i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x20000000] (bogus alignment)
[   14.279395] [drm] failed to find VBIOS tables
[   14.318726] ACPI Warning: \_SB.PCI0.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[   14.321346] ACPI: \_SB_.PCI0.IGPU: failed to evaluate _DSM
[   14.323559] ACPI Warning: \_SB.PCI0.P0P2.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[   14.326021] [drm] RC6 disabled, disabling runtime PM support
[   14.328407] ACPI: \_SB_.PCI0.P0P2.GFX0: failed to evaluate _DSM
[   14.330641] nouveau 0000:01:00.0: enabling device (0002 -> 0003)
[   14.343980] checking generic (c0030000 834000) vs hw (c0000000 10000000)
[   14.343982] fb: switching to nouveaufb from EFI VGA


Let me know if you need more information.

Comment 10 Fedora End Of Life 2017-07-25 21:46:44 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2017-08-08 15:33:54 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.