From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99881] Lockup/Freezes on Laptop with switchable graphics
Date: Tue, 21 Feb 2017 04:09:19 +0000 [thread overview]
Message-ID: <bug-99881-502-b0rmCGVeDO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99881-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 5098 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99881
--- Comment #9 from Matthew Fox <matthew@tech3.me> ---
(In reply to Michel Dänzer from comment #8)
> Please attach the corresponding Xorg log file.
Hi,
The only Xorg logs I have are for my new session. They weren't in /var/log/ but
/home/matthew/.local/share/xorg/Xorg.1.log
/var/lib/gdm3/.local/share/xorg/Xorg.0.log
for some reason. They are attached.
Also attached is a dmesg log for my current session.
When I said:
With previous ubuntu/kernel versions, the main issue was the freezing which
would happen every seven seconds with the corresponding dmesg block. This would
continue ad infinitum, although on rare occasions it would stop after many
freezes. However with my current kernel this pattern doesn't seem to occur - it
freezes a few times before the freezing stops and the freezes do not occur at
regular intervals.
- this seems to be true of my current kernel. From the current dmesg.log, the
'Disabling via vga_switcheroo' happened at 14, 33, 41 and finally 48 (seven
seconds apart, except 14-33):
[ 14.146303] snd_hda_intel 0000:02:00.1: Disabling via vga_switcheroo
[ 15.586313] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[ 15.588655] [drm] PCIE GART of 512M enabled (table at 0x000000000014C000).
[ 15.588728] radeon 0000:02:00.0: WB enabled
[ 15.588731] radeon 0000:02:00.0: fence driver on ring 0 use gpu addr
0x0000000020000c00 and cpu addr 0xffff90180fa71c00
[ 15.588733] radeon 0000:02:00.0: fence driver on ring 3 use gpu addr
0x0000000020000c0c and cpu addr 0xffff90180fa71c0c
[ 15.589099] radeon 0000:02:00.0: fence driver on ring 5 use gpu addr
0x000000000005c418 and cpu addr 0xffffbdbf41a1c418
[ 15.605265] [drm] ring test on 0 succeeded in 1 usecs
[ 15.605270] [drm] ring test on 3 succeeded in 2 usecs
[ 15.791907] [drm] ring test on 5 succeeded in 1 usecs
[ 15.791914] [drm] UVD initialized successfully.
[ 15.791956] [drm] ib test on ring 0 succeeded in 0 usecs
[ 15.791986] [drm] ib test on ring 3 succeeded in 0 usecs
[ 16.482332] [drm] ib test on ring 5 succeeded
[ 16.515177] snd_hda_intel 0000:02:00.1: Enabling via vga_switcheroo
[ 16.619344] snd_hda_intel 0000:02:00.1: CORB reset timeout#2, CORBRP = 65535
[ 33.089549] snd_hda_intel 0000:02:00.1: Disabling via vga_switcheroo
[ 33.389563] snd_hda_intel 0000:02:00.1: Cannot lock devices!
[ 34.733597] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[ 34.735932] [drm] PCIE GART of 512M enabled (table at 0x000000000014C000).
[ 34.736006] radeon 0000:02:00.0: WB enabled
[ 34.736009] radeon 0000:02:00.0: fence driver on ring 0 use gpu addr
0x0000000020000c00 and cpu addr 0xffff90180fa71c00
[ 34.736011] radeon 0000:02:00.0: fence driver on ring 3 use gpu addr
0x0000000020000c0c and cpu addr 0xffff90180fa71c0c
[ 34.736378] radeon 0000:02:00.0: fence driver on ring 5 use gpu addr
0x000000000005c418 and cpu addr 0xffffbdbf41a1c418
[ 34.753251] [drm] ring test on 0 succeeded in 1 usecs
[ 34.753256] [drm] ring test on 3 succeeded in 2 usecs
[ 34.939919] [drm] ring test on 5 succeeded in 1 usecs
[ 34.939926] [drm] UVD initialized successfully.
[ 34.939969] [drm] ib test on ring 0 succeeded in 0 usecs
[ 34.940006] [drm] ib test on ring 3 succeeded in 0 usecs
[ 35.617560] [drm] ib test on ring 5 succeeded
[ 35.650390] snd_hda_intel 0000:02:00.1: Enabling via vga_switcheroo
[ 35.753848] snd_hda_intel 0000:02:00.1: CORB reset timeout#2, CORBRP = 65535
[ 41.025246] snd_hda_intel 0000:02:00.1: Disabling via vga_switcheroo
[ 41.325632] snd_hda_intel 0000:02:00.1: Cannot lock devices!
[ 42.665278] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[ 42.667593] [drm] PCIE GART of 512M enabled (table at 0x000000000014C000).
[ 42.667666] radeon 0000:02:00.0: WB enabled
[ 42.667670] radeon 0000:02:00.0: fence driver on ring 0 use gpu addr
0x0000000020000c00 and cpu addr 0xffff90180fa71c00
[ 42.667671] radeon 0000:02:00.0: fence driver on ring 3 use gpu addr
0x0000000020000c0c and cpu addr 0xffff90180fa71c0c
[ 42.668038] radeon 0000:02:00.0: fence driver on ring 5 use gpu addr
0x000000000005c418 and cpu addr 0xffffbdbf41a1c418
[ 42.684185] [drm] ring test on 0 succeeded in 1 usecs
[ 42.684189] [drm] ring test on 3 succeeded in 2 usecs
[ 42.870780] [drm] ring test on 5 succeeded in 1 usecs
[ 42.870784] [drm] UVD initialized successfully.
[ 42.870821] [drm] ib test on ring 0 succeeded in 0 usecs
[ 42.870850] [drm] ib test on ring 3 succeeded in 0 usecs
[ 43.553259] [drm] ib test on ring 5 succeeded
[ 43.582109] snd_hda_intel 0000:02:00.1: Enabling via vga_switcheroo
[ 43.685717] snd_hda_intel 0000:02:00.1: CORB reset timeout#2, CORBRP = 65535
[ 48.960919] snd_hda_intel 0000:02:00.1: Disabling via vga_switcheroo
[ 49.261324] snd_hda_intel 0000:02:00.1: Cannot lock devices!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5945 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-21 4:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 0:06 [Bug 99881] Lockup/Freezes on Laptop with switchable graphics bugzilla-daemon
2017-02-21 0:10 ` bugzilla-daemon
2017-02-21 1:18 ` bugzilla-daemon
2017-02-21 1:21 ` bugzilla-daemon
2017-02-21 1:52 ` bugzilla-daemon
2017-02-21 2:07 ` bugzilla-daemon
2017-02-21 2:31 ` bugzilla-daemon
2017-02-21 2:55 ` bugzilla-daemon
2017-02-21 3:08 ` bugzilla-daemon
2017-02-21 3:11 ` bugzilla-daemon
2017-02-21 4:09 ` bugzilla-daemon [this message]
2017-02-21 4:11 ` bugzilla-daemon
2017-02-21 4:15 ` bugzilla-daemon
2017-02-21 4:16 ` bugzilla-daemon
2017-02-21 4:46 ` bugzilla-daemon
2017-02-21 6:20 ` bugzilla-daemon
2017-02-21 20:28 ` bugzilla-daemon
2017-02-21 20:29 ` bugzilla-daemon
2017-02-21 20:30 ` bugzilla-daemon
2017-02-21 20:32 ` bugzilla-daemon
2017-02-21 20:33 ` bugzilla-daemon
2017-02-21 20:34 ` bugzilla-daemon
2017-02-21 20:36 ` bugzilla-daemon
2017-02-21 20:36 ` bugzilla-daemon
2017-02-22 9:25 ` bugzilla-daemon
2017-02-22 16:29 ` bugzilla-daemon
2017-02-23 0:58 ` bugzilla-daemon
2017-02-23 3:29 ` bugzilla-daemon
2017-02-23 3:30 ` bugzilla-daemon
2017-02-23 3:34 ` bugzilla-daemon
2017-02-23 3:36 ` bugzilla-daemon
2017-02-23 3:38 ` bugzilla-daemon
2017-02-23 4:03 ` bugzilla-daemon
2017-02-23 8:24 ` bugzilla-daemon
2017-02-23 13:53 ` bugzilla-daemon
2017-02-23 20:51 ` bugzilla-daemon
2019-11-19 9:25 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99881-502-b0rmCGVeDO@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.