From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94331] New: Random panic with radeon
Date: Thu, 05 Mar 2015 11:45:55 +0000 [thread overview]
Message-ID: <bug-94331-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=94331
Bug ID: 94331
Summary: Random panic with radeon
Product: Drivers
Version: 2.5
Kernel Version: 4.0.0-rc1-00151-ga38ecbb
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: sulamiification@gmail.com
Regression: No
Created attachment 169221
--> https://bugzilla.kernel.org/attachment.cgi?id=169221&action=edit
Kernel log
Yesterday my 4.0.0-rc1 randomly panicked. Because of the panic messsage I am
assuming it is at least related to radeon.
Hardware:
- Intel Xeon E3-1245v3
- AMD Radeon HD7970
- ASRock B85M Pro4
Software:
- Mainline Kernel built on Monday (4.0.0-rc1-00151-ga38ecbb)
- radeon driver
The panic happened after about one day of uptime, I was running cwm + compton,
an OpenBSD VM in qemu/kvm without graphics in the background and a HTML5
YouTube video in Firefox.
I added the log up until then as an attachment, but I cannot find anything
suspicious. The "wm" segfault is my fault, I am working on a Wayland
compositor. The bridge mess as well.
I made a photo of the panic for later examination, which can be found here:
https://i.imgur.com/I7xBwWD.jpg
So far I have not been able to reproduce this issue.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-03-05 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 11:45 bugzilla-daemon [this message]
2015-03-06 1:28 ` [Bug 94331] Random panic with radeon bugzilla-daemon
2015-03-07 16:28 ` 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-94331-2300@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 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.