[Intel-gfx] 5.13-rc6 on thinkpad X220: graphics hangs with recent mainline

[Intel-gfx] 5.13-rc6 on thinkpad X220: graphics hangs with recent mainline

[Pavel Machek]

[-- Attachment #1.1: Type: text/plain, Size: 4690 bytes --]

Hi!

I'm getting graphics problems with 5.13-rc:

Debian 10.9, X, chromium and flightgear is in use. Things were more
stable than this with previous kernels.

Any ideas?

Best regards,
								Pavel

[185233.329693] wlp3s0: deauthenticated from 5c:f4:ab:10:d2:bb (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
[185234.040352] wlp3s0: authenticate with 5c:f4:ab:10:d2:bb
[185234.043836] wlp3s0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
[185234.046652] wlp3s0: authenticated
[185234.049087] wlp3s0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
[185234.052667] wlp3s0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=1)
[185234.055398] wlp3s0: associated
[185300.784992] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[185300.888694] i915 0000:00:02.0: [drm] fgfs[27370] context reset due to GPU hang
[185472.274563] usb 2-1.1: USB disconnect, device number 3
[185472.274578] usb 2-1.1.2: USB disconnect, device number 5
[185472.281518] hid-generic 0003:04F2:0111.0003: usb_submit_urb(ctrl) failed: -19
[185472.299837] hid-generic 0003:04F2:0111.0003: usb_submit_urb(ctrl) failed: -19
[185472.305986] hid-generic 0003:04F2:0111.0003: usb_submit_urb(ctrl) failed: -19
[185472.328012] hid-generic 0003:04F2:0111.0003: usb_submit_urb(ctrl) failed: -19
[185472.333738] usb 2-1.1.3: USB disconnect, device number 6
[185673.454821] usb 2-1.1: new high-speed USB device number 7 using ehci-pci
[185673.563486] usb 2-1.1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[185673.563502] usb 2-1.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[185673.563509] usb 2-1.1: Product: USB 2.0 Hub
[185673.564488] hub 2-1.1:1.0: USB hub found
[185673.564595] hub 2-1.1:1.0: 4 ports detected
...
[207277.385543] wlp3s0: deauthenticated from 5c:f4:ab:10:d2:bb (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
[207278.062061] wlp3s0: authenticate with 5c:f4:ab:10:d2:bb
[207278.068175] wlp3s0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
[207278.070985] wlp3s0: authenticated
[207278.075545] wlp3s0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
[207278.080793] wlp3s0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=1)
[207278.084081] wlp3s0: associated
[207564.046469] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[207564.150293] i915 0000:00:02.0: [drm] fgfs[25729] context reset due to GPU hang
[209075.178776] wlp3s0: deauthenticated from 5c:f4:ab:10:d2:bb (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
[209075.841872] wlp3s0: authenticate with 5c:f4:ab:10:d2:bb
[209075.845305] wlp3s0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
[209075.851186] wlp3s0: authenticated
[209075.852537] wlp3s0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
[209075.855972] wlp3s0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=1)
[209075.858522] wlp3s0: associated
[210159.723726] PM: suspend entry (deep)
[210159.741497] Filesystems sync: 0.017 seconds
[210159.743585] Freezing user space processes ... (elapsed 0.009 seconds) done.
[210159.753345] OOM killer disabled.
[210159.753349] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
[210159.757357] printk: Suspending console(s) (use no_console_suspend to debug)
[210159.945365] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[210159.945443] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[210159.945651] sd 0:0:0:0: [sda] Stopping disk
[210159.947225] sd 2:0:0:0: [sdb] Stopping disk
[210160.019791] wlp3s0: deauthenticating from 5c:f4:ab:10:d2:bb by local choice (Reason: 3=DEAUTH_LEAVING)
[210160.021158] e1000e: EEE TX LPI TIMER: 00000011
[210161.245106] PM: suspend devices took 1.488 seconds
[210161.266601] ACPI: EC: interrupt blocked
[210161.305431] ACPI: Preparing to enter system sleep state S3
[210161.313532] ACPI: EC: event blocked
[210161.313535] ACPI: EC: EC stopped
[210161.313537] PM: Saving platform NVS memory
[210161.313548] Disabling non-boot CPUs ...
...
[224698.957159] wlp3s0: associated
[229707.724067] wlp3s0: deauthenticated from 5c:f4:ab:10:d2:bb (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
[229708.370607] wlp3s0: authenticate with 5c:f4:ab:10:d2:bb
[229708.373732] wlp3s0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
[229708.376501] wlp3s0: authenticated
[229708.379997] wlp3s0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
[229708.383773] wlp3s0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=1)
[229708.386423] wlp3s0: associated
[229756.518759] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[229756.622596] i915 0000:00:02.0: [drm] fgfs[2648] context reset due to GPU hang

-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] 5.13-rc6 on thinkpad X220: graphics hangs with recent mainline

[Joonas Lahtinen]

Quoting Pavel Machek (2021-06-24 12:53:59)
> Hi!
> 
> I'm getting graphics problems with 5.13-rc:
> 
> Debian 10.9, X, chromium and flightgear is in use. Things were more
> stable than this with previous kernels.
> 
> Any ideas?

The error you are seeing:

> [185300.784992] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
> [185300.888694] i915 0000:00:02.0: [drm] fgfs[27370] context reset due to GPU hang

That just indicates that the rendering took too long. It could be caused
by a change in how the application renders, userspace driver or i915. So
a previously on-the-edge-of-timeout operation may have got pushed beyond
the timeout, or the rendering genuinely got completely stuck.

If you only updated the kernel, not the application or userspace, could
you bisect the commit that introduced the behavior and report:

https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs

We have changes around this area, so would be helpful if you can bisect
the commit that started the behavior.

Regards, Joonas

> 
> Best regards,
>                                                                 Pavel
> 
> [185233.329693] wlp3s0: deauthenticated from 5c:f4:ab:10:d2:bb (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
> [185234.040352] wlp3s0: authenticate with 5c:f4:ab:10:d2:bb
> [185234.043836] wlp3s0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> [185234.046652] wlp3s0: authenticated
> [185234.049087] wlp3s0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> [185234.052667] wlp3s0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=1)
> [185234.055398] wlp3s0: associated
> [185300.784992] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
> [185300.888694] i915 0000:00:02.0: [drm] fgfs[27370] context reset due to GPU hang
> [185472.274563] usb 2-1.1: USB disconnect, device number 3
> [185472.274578] usb 2-1.1.2: USB disconnect, device number 5
> [185472.281518] hid-generic 0003:04F2:0111.0003: usb_submit_urb(ctrl) failed: -19
> [185472.299837] hid-generic 0003:04F2:0111.0003: usb_submit_urb(ctrl) failed: -19
> [185472.305986] hid-generic 0003:04F2:0111.0003: usb_submit_urb(ctrl) failed: -19
> [185472.328012] hid-generic 0003:04F2:0111.0003: usb_submit_urb(ctrl) failed: -19
> [185472.333738] usb 2-1.1.3: USB disconnect, device number 6
> [185673.454821] usb 2-1.1: new high-speed USB device number 7 using ehci-pci
> [185673.563486] usb 2-1.1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
> [185673.563502] usb 2-1.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
> [185673.563509] usb 2-1.1: Product: USB 2.0 Hub
> [185673.564488] hub 2-1.1:1.0: USB hub found
> [185673.564595] hub 2-1.1:1.0: 4 ports detected
> ...
> [207277.385543] wlp3s0: deauthenticated from 5c:f4:ab:10:d2:bb (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
> [207278.062061] wlp3s0: authenticate with 5c:f4:ab:10:d2:bb
> [207278.068175] wlp3s0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> [207278.070985] wlp3s0: authenticated
> [207278.075545] wlp3s0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> [207278.080793] wlp3s0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=1)
> [207278.084081] wlp3s0: associated
> [207564.046469] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
> [207564.150293] i915 0000:00:02.0: [drm] fgfs[25729] context reset due to GPU hang
> [209075.178776] wlp3s0: deauthenticated from 5c:f4:ab:10:d2:bb (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
> [209075.841872] wlp3s0: authenticate with 5c:f4:ab:10:d2:bb
> [209075.845305] wlp3s0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> [209075.851186] wlp3s0: authenticated
> [209075.852537] wlp3s0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> [209075.855972] wlp3s0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=1)
> [209075.858522] wlp3s0: associated
> [210159.723726] PM: suspend entry (deep)
> [210159.741497] Filesystems sync: 0.017 seconds
> [210159.743585] Freezing user space processes ... (elapsed 0.009 seconds) done.
> [210159.753345] OOM killer disabled.
> [210159.753349] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
> [210159.757357] printk: Suspending console(s) (use no_console_suspend to debug)
> [210159.945365] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
> [210159.945443] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [210159.945651] sd 0:0:0:0: [sda] Stopping disk
> [210159.947225] sd 2:0:0:0: [sdb] Stopping disk
> [210160.019791] wlp3s0: deauthenticating from 5c:f4:ab:10:d2:bb by local choice (Reason: 3=DEAUTH_LEAVING)
> [210160.021158] e1000e: EEE TX LPI TIMER: 00000011
> [210161.245106] PM: suspend devices took 1.488 seconds
> [210161.266601] ACPI: EC: interrupt blocked
> [210161.305431] ACPI: Preparing to enter system sleep state S3
> [210161.313532] ACPI: EC: event blocked
> [210161.313535] ACPI: EC: EC stopped
> [210161.313537] PM: Saving platform NVS memory
> [210161.313548] Disabling non-boot CPUs ...
> ...
> [224698.957159] wlp3s0: associated
> [229707.724067] wlp3s0: deauthenticated from 5c:f4:ab:10:d2:bb (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)
> [229708.370607] wlp3s0: authenticate with 5c:f4:ab:10:d2:bb
> [229708.373732] wlp3s0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> [229708.376501] wlp3s0: authenticated
> [229708.379997] wlp3s0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> [229708.383773] wlp3s0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=1)
> [229708.386423] wlp3s0: associated
> [229756.518759] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
> [229756.622596] i915 0000:00:02.0: [drm] fgfs[2648] context reset due to GPU hang
> 
> -- 
> http://www.livejournal.com/~pavelmachek
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] 5.13-rc6 on thinkpad X220: graphics hangs with recent mainline

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

Hi!
> > I'm getting graphics problems with 5.13-rc:
> > 
> > Debian 10.9, X, chromium and flightgear is in use. Things were more
> > stable than this with previous kernels.
> > 
> > Any ideas?
> 
> The error you are seeing:
> 
> > [185300.784992] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
> > [185300.888694] i915 0000:00:02.0: [drm] fgfs[27370] context reset due to GPU hang
> 
> That just indicates that the rendering took too long. It could be caused
> by a change in how the application renders, userspace driver or i915. So
> a previously on-the-edge-of-timeout operation may have got pushed beyond
> the timeout, or the rendering genuinely got completely stuck.
> 
> If you only updated the kernel, not the application or userspace, could
> you bisect the commit that introduced the behavior and report:
> 
> https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
> 
> We have changes around this area, so would be helpful if you can bisect
> the commit that started the behavior.

So with more recent kernels, problem went away. Is it possible it was
one of those "aborted fence aborts both application and X" problems?

Best regards,
								Pavel
-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]