From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 38232] New: kernel bug at drivers/gpu/drm/ttm/ttm_bo.c:272
Date: Sat, 25 Jun 2011 09:27:37 GMT [thread overview]
Message-ID: <bug-38232-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=38232
URL: http://i53.tinypic.com/1zwdxqh.jpg
Summary: kernel bug at drivers/gpu/drm/ttm/ttm_bo.c:272
Product: Drivers
Version: 2.5
Kernel Version: 2.6.39.*
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: lukenshiro@ngi.it
Regression: Yes
I have a kernel panic using a Radeon HD4350 (RV710) with kernel 2.6.39.2, in
Slackware "current" (CPU AMD Phenom, x86_64 non multilib, gcc 4.5.3, glibc
2.13, make 3.82, binutils 2.21.51.0.6, libdrm 2.4.25, ati xorg driver 6.14.1),
after some (about 2 hours) of use.
I have had similar panics also in 2.6.39 and 2.6.39.1 before (but I couldn't do
a transcription of correlative messages).
In url I put the most clear screen snapshot I've taken with a digital camera (i
did other ones but unfortunately they are not of so good quality).
Messages/syslog log files are not really useful. If you need other infos please
let me know.
Another photo is on:
http://i53.tinypic.com/2jfhax.jpg
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2011-06-25 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 9:27 bugzilla-daemon [this message]
2011-06-25 11:01 ` [Bug 38232] kernel bug at drivers/gpu/drm/ttm/ttm_bo.c:272 bugzilla-daemon
2011-06-26 12:58 ` bugzilla-daemon
2011-06-27 22:12 ` bugzilla-daemon
2011-06-27 22:12 ` 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-38232-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox