From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71864] [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0)
Date: Fri, 22 Nov 2013 14:49:59 +0000 [thread overview]
Message-ID: <bug-71864-502-TDL0s8LMPY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71864-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1514 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71864
--- Comment #11 from reimth@gmail.com ---
(In reply to comment #10)
> Is this still an issue with a newer kernel? Did you also update your
> userspace stack (mesa, xf86-video-ati)?
We used Ubuntu update manager to upgrade to kernel 3.2. It's part of Ubuntu's
long term support release 12.04.
>From the attached logs I can see following installed versions:
1. xserver-xorg-video-ati (Ubuntu's xf86-video-ati)
[ 107.230] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 107.230] (II) Module ati: vendor="X.Org Foundation"
[ 107.230] compiled for 1.11.3, module version = 6.14.99
[ 107.230] Module class: X.Org Video Driver
[ 107.230] ABI class: X.Org Video Driver, version 11.0
[ 107.230] (II) LoadModule: "radeon"
[ 107.230] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 107.231] (II) Module radeon: vendor="X.Org Foundation"
[ 107.231] compiled for 1.11.3, module version = 6.14.99
[ 107.231] Module class: X.Org Video Driver
[ 107.231] ABI class: X.Org Video Driver, version 11.0
2. OpenGL version string: 2.1 Mesa 8.0.4
Are these the expected versions?
I can try to install also a newer kernel. But as we talk about a 24/7 server, I
need some guidance. Newer kernel also requires newer userspace stack? Which
kernel version would you recommend?
Do you have any ideas on possible root causes of this kernel oops?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2404 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-11-22 14:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 8:42 [Bug 71864] New: [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0) bugzilla-daemon
2013-11-21 8:44 ` [Bug 71864] " bugzilla-daemon
2013-11-21 8:44 ` bugzilla-daemon
2013-11-21 8:45 ` bugzilla-daemon
2013-11-21 8:45 ` bugzilla-daemon
2013-11-21 8:50 ` bugzilla-daemon
2013-11-21 8:51 ` bugzilla-daemon
2013-11-21 8:55 ` bugzilla-daemon
2013-11-21 8:56 ` bugzilla-daemon
2013-11-21 9:00 ` bugzilla-daemon
2013-11-21 16:10 ` bugzilla-daemon
2013-11-22 14:49 ` bugzilla-daemon [this message]
2013-11-22 15:08 ` bugzilla-daemon
2013-11-23 11:39 ` bugzilla-daemon
2013-11-23 21:41 ` bugzilla-daemon
2013-11-24 15:37 ` bugzilla-daemon
2013-11-24 16:17 ` bugzilla-daemon
2013-11-24 17:15 ` bugzilla-daemon
2013-12-02 10:00 ` bugzilla-daemon
2013-12-02 17:55 ` bugzilla-daemon
2013-12-05 10:23 ` bugzilla-daemon
2013-12-05 15:10 ` bugzilla-daemon
2019-11-19 8:40 ` 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-71864-502-TDL0s8LMPY@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox