From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196273] Loss of video output and system freezes *ERROR* Couldn't read SADs: 0
Date: Thu, 06 Jul 2017 18:39:19 +0000 [thread overview]
Message-ID: <bug-196273-2300-Q27guEGszM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196273-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196273
--- Comment #8 from Olaf H B (olaf@seldiame.net) ---
(In reply to Michel Dänzer from comment #6)
> Is this a regression from older kernel versions? If yes, can you bisect?
I don't think this is a regression because I had similar issues with kernel
4.11
I got other freeze some minutes ago.
This appears in the kernel.log: (complete file in attachment)
Jul 6 13:18:35 hiperion kernel: [47523.933893] general protection fault: 0000
[#1] SMP
Jul 6 13:18:35 hiperion kernel: [47523.934043] Modules linked in: kvm_amd kvm
irqbypass aesni_intel aes_x86_64 amdgpu crypto_simd cryptd glue_helper
input_leds fam15h_power k10temp mfd_core backlight ttm acpi_cpufreq
Jul 6 13:18:35 hiperion kernel: [47523.934565] CPU: 2 PID: 12681 Comm: Timer
Not tainted 4.12.0 #3
Jul 6 13:18:35 hiperion kernel: [47523.934746] Hardware name: To be filled by
O.E.M. To be filled by O.E.M./M5A97 R2.0, BIOS 2603 06/26/2015
Jul 6 13:18:35 hiperion kernel: [47523.935031] task: ffff88031ba00d00
task.stack: ffffc900015b8000
Jul 6 13:18:35 hiperion kernel: [47523.935146] RIP: 0010:0xffffffff8106674e
Jul 6 13:18:35 hiperion kernel: [47523.935178] RSP: 0018:ffffc900015bbcd8
EFLAGS: 00010002
Jul 6 13:18:35 hiperion kernel: [47523.935221] RAX: ffffffff81808320 RBX:
ffff8804294aa700 RCX: 0000000000000001
Jul 6 13:18:35 hiperion kernel: [47523.935276] RDX: 0000000000000010 RSI:
0000000000000000 RDI: ffff8804294aa700
Jul 6 13:18:35 hiperion kernel: [47523.935332] RBP: ffffc900015bbd20 R08:
0000000000000041 R09: 0000000000000001
Jul 6 13:18:35 hiperion kernel: [47523.935387] R10: ffffea000c6fed00 R11:
0000000000000000 R12: 0000000000000001
Jul 6 13:18:35 hiperion kernel: [47523.935443] R13: ffff8804294aadbc R14:
0000000000000046 R15: 0000000000018740
Jul 6 13:18:35 hiperion kernel: [47523.935499] FS: 00007f2b6bb57700(0000)
GS:ffff88043ec80000(0000) knlGS:0000000000000000
Jul 6 13:18:35 hiperion kernel: [47523.935561] CS: 0010 DS: 0000 ES: 0000
CR0: 0000000080050033
Jul 6 13:18:35 hiperion kernel: [47523.935607] CR2: 00007f53897ea000 CR3:
00000003c397f000 CR4: 00000000000406e0
Jul 6 13:18:35 hiperion kernel: [47523.935662] Call Trace:
Jul 6 13:18:35 hiperion kernel: [47523.935685] 0xffffffff81066aad
Jul 6 13:18:35 hiperion kernel: [47523.935712] 0xffffffff8114a7c1
Jul 6 13:18:35 hiperion kernel: [47523.935738] ? 0xffffffff81066aa0
Jul 6 13:18:35 hiperion kernel: [47523.935766] 0xffffffff8107a1cd
Jul 6 13:18:35 hiperion kernel: [47523.935792] 0xffffffff8107a70f
Jul 6 13:18:35 hiperion kernel: [47523.935818] 0xffffffff8113e761
Jul 6 13:18:35 hiperion kernel: [47523.935845] 0xffffffff81134dff
Jul 6 13:18:35 hiperion kernel: [47523.935872] 0xffffffff8113569e
Jul 6 13:18:35 hiperion kernel: [47523.935898] ? 0xffffffff810adcf8
Jul 6 13:18:35 hiperion kernel: [47523.935925] 0xffffffff81136b8a
Jul 6 13:18:35 hiperion kernel: [47523.935952] 0xffffffff816b96a0
Jul 6 13:18:35 hiperion kernel: [47523.935978] RIP: 0033:0x00007f2b8be0fe5d
Jul 6 13:18:35 hiperion kernel: [47523.936010] RSP: 002b:00007f2b6bb56790
EFLAGS: 00000293 ORIG_RAX: 0000000000000001
Jul 6 13:18:35 hiperion kernel: [47523.936070] RAX: ffffffffffffffda RBX:
00007f2b8bd3edb0 RCX: 00007f2b8be0fe5d
Jul 6 13:18:35 hiperion kernel: [47523.936125] RDX: 0000000000000001 RSI:
00007f2b6bb567a7 RDI: 000000000000001b
Jul 6 13:18:35 hiperion kernel: [47523.936180] RBP: 00000000000000fa R08:
00007f2b76687908 R09: 0000000000000000
Jul 6 13:18:35 hiperion kernel: [47523.936234] R10: 000000000000002b R11:
0000000000000293 R12: 0000000000000005
Jul 6 13:18:35 hiperion kernel: [47523.936289] R13: 0000000000000000 R14:
00007f2b6bb56a28 R15: 00002b38d797ff91
Jul 6 13:18:35 hiperion kernel: [47523.936368] Code: 88 83 04 04 00 00 0f 85
66 01 00 00 83 bb 1c 03 00 00 01 0f 8e b8 01 00 00 48 8b 43 68 ba 10 00 00 00
8b 73 50 44 89 e1 48 89 df <ff> 50 40 48 8d 93 20 03 00 00 41 89 c0 44 89 c0 48
0f
a3 02 0f
Jul 6 13:18:35 hiperion kernel: [47523.936551] RIP: 0xffffffff8106674e RSP:
ffffc900015bbcd8
Jul 6 13:18:35 hiperion kernel: [47523.956831] ---[ end trace de9deca7f7bcb1e8
]---
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-07-06 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 17:49 [Bug 196273] New: Loss of video output and system freezes *ERROR* Couldn't read SADs: 0 bugzilla-daemon
2017-07-04 17:50 ` [Bug 196273] " bugzilla-daemon
2017-07-04 17:50 ` bugzilla-daemon
2017-07-04 17:51 ` bugzilla-daemon
2017-07-04 17:51 ` bugzilla-daemon
2017-07-04 17:52 ` bugzilla-daemon
2017-07-05 1:33 ` bugzilla-daemon
2017-07-05 14:53 ` bugzilla-daemon
2017-07-06 18:39 ` bugzilla-daemon [this message]
2017-07-06 18:40 ` bugzilla-daemon
2017-07-06 18:59 ` bugzilla-daemon
2017-07-10 22:48 ` bugzilla-daemon
2017-07-11 0:27 ` bugzilla-daemon
2017-07-13 18:48 ` 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-196273-2300-Q27guEGszM@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox