[oi-dev] Fwd: [Graphics/DRM - Bug #7716] drm hang with ring dumps in messages
Aurélien Larcher
aurelien.larcher at gmail.com
Fri Feb 10 21:27:05 UTC 2017
On Fri, Feb 10, 2017 at 10:22 PM, ken mays via oi-dev <
oi-dev at openindiana.org> wrote:
> Hello,
>
> My desktop doesn't hang when doing this test.
>
What is the chipset?
>
> Two things are reporting to fix issue:
> 1. Update xorg-video-intel 2.99.917 driver to recent git (fixes this for
> Linux users for same bug).
>
Nope. I already run latest git with Xorg 1.18.4.
> 2. Patch gfx-drm.
>
> ~K
>
>
>
> On Friday, February 10, 2017 12:14 PM, Aurélien Larcher <
> aurelien.larcher at gmail.com> wrote:
>
>
>
>
> On Fri, Feb 10, 2017 at 9:06 PM, Marcel Telka <marcel at telka.sk> wrote:
>
> I just did on my T520:
>
> mdb -kwe 'i915_try_reset/W 1'
>
> I'll report back in few days if it won't hang (or sooner, if it will).
>
>
> You can trigger it by running glx_gears in non-synced mode: vblank_mode=0
> glxgears
>
> See if the GPU hangs 2-3 seconds then continues.
>
>
>
>
>
> Thanks.
>
>
> On Fri, Feb 10, 2017 at 02:39:07PM -0500, Gordon Ross wrote:
> > I've heard this happens on the Lenovo W520 (and maybe others)
> > Can anyone try this for me? Thanks.
> >
> >
> > ---------- Forwarded message ----------
> > From: illumos project <devnull at illumos.org>
> > Date: Fri, Feb 10, 2017 at 2:37 PM
> > Subject: [Graphics/DRM - Bug #7716] drm hang with ring dumps in messages
> > To:
> >
> >
> > Issue #7716 has been updated by Gordon Ross.
> >
> >
> > Can anyone with one of the systems affected by this hang try setting
> > i915_try_reset = true
> > (you can use mdb -kw to set it)
> > and report back with the result? Thanks!
> >
> > ------------------------------ ----------
> > Bug #7716: drm hang with ring dumps in messages
> > https://www.illumos.org/ issues/7716#change-18715
> <https://www.illumos.org/issues/7716#change-18715>
> >
> > * Author: Marcel Telka
> > * Status: New
> > * Priority: Normal
> > * Assignee:
> > * Category:
> > * Target version:
> > * Difficulty: Medium
> > * Tags: needs-triage
> > ------------------------------ ----------
> > I face the drm hang with the flood of ring dumps in the
> > /var/adm/messages (attached). After the hang the screen shows the
> > distorted image and Xorg core dumps. The only way I found how to get
> > out of this is reboot.
> >
> > Here is the beginning of the messages log:
> >
> > <pre>
> > Jan 2 11:41:32 telcontar drm: [ID 300979 kern.warning] WARNING:
> > [drm:ring_dump:881] Dump render ring ring
> > Jan 2 11:41:32 telcontar drm: [ID 834546 kern.warning] WARNING:
> > [drm:ring_dump:882] HEAD 0x14d04 TAIL 0x14e28
> > Jan 2 11:41:32 telcontar drm: [ID 628728 kern.warning] WARNING:
> > [drm:ring_dump:883] seq 3742159
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a34]: 0x12044
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a38]: 0x3919c9
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a3c]: 0x0
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a40]: 0x11000001
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a44]: 0x22040
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a48]: 0x3919c9
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a4c]: 0x0
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a50]: 0x10800001
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a54]: 0x80
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a58]: 0x3919c9
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a5c]: 0x1000000
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a60]: 0xb160001
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a64]: 0x3919c9
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a68]: 0x0
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a6c]: 0x0
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a70]: 0x7a000003
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a74]: 0x100002
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a78]: 0x261084
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a7c]: 0x0
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a80]: 0x0
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a84]: 0x0
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a88]: 0x7a000003
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a8c]: 0x4000
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a90]: 0x261084
> > Jan 2 11:41:32 telcontar drm: [ID 994420 kern.warning] WARNING:
> > [drm:ring_dump:890] render ring[0x14a94]: 0x0
> >
> > ...
> > </pre>
> >
> > This hang happens usually in less than 24 hours after the boot, but
> > sometimes the machine survives for several days. The machine is
> > Lenovo T520 with this graphics controller (scanpci):
> >
> > <pre>
> > pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x0126
> > Intel Corporation 2nd Generation Core Processor Family Integrated
> > Graphics Controller
> > </pre>
> >
> > IIRC, this started to happen once I updated from older drm binaries
> > (made by Martin Bochnig) to the gfx-drm work available in recent OI
> > Hipster.
> >
> > ---Files---------------------- ----------
> > messages (695 KB)
> >
> >
> > --
> > You have received this notification because you have either subscribed
> > to it, or are involved in it.
> > To change your notification preferences, please click here:
> > http://www.illumos.org/my/ account <http://www.illumos.org/my/account>
> >
> > ______________________________ _________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > https://openindiana.org/ mailman/listinfo/oi-dev
> <https://openindiana.org/mailman/listinfo/oi-dev>
>
> --
> +----------------------------- --------------+
> | Marcel Telka e-mail: marcel at telka.sk |
> | homepage: http://telka.sk/ |
> | jabber: marcel at jabber.sk |
> +----------------------------- --------------+
>
> ______________________________ _________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/ mailman/listinfo/oi-dev
> <https://openindiana.org/mailman/listinfo/oi-dev>
>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
>
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
--
---
Praise the Caffeine embeddings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20170210/622a0e18/attachment-0005.html>
More information about the oi-dev
mailing list