From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33969] New: "unable to handle kernel paging request" crash after playing tuxracer for a few seconds
Date: Sun, 6 Feb 2011 09:32:00 -0800 (PST) [thread overview]
Message-ID: <bug-33969-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=33969
Summary: "unable to handle kernel paging request" crash after
playing tuxracer for a few seconds
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: adam.rak@streamnovation.com
Created an attachment (id=42998)
--> (https://bugs.freedesktop.org/attachment.cgi?id=42998)
Full dmesg after the crash
Hardware is Fusion Zacate APU (HD6310)
Mesa is commit ec96b0ecdbe723f4664188010c7f86d5d7f41d82 checkout
ddx is commit a4899db96029acde6cd400fc0541693a487898e7 checkout
linux kernel is 2.6.38-rc3 commit 44f2c5c841da1b1e0864d768197ab1497b5c2cc1
X.Org X Server 1.7.7 (debian squeeze)
Running nexuiz crashes the X when entering play mode. (no apparent error log)
Running(and playing) extremetuxracer produces a kernel oops after a few
seconds, the dmesg is in the attachment.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-06 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 17:32 bugzilla-daemon [this message]
2011-02-06 17:37 ` [Bug 33969] "unable to handle kernel paging request" crash after playing tuxracer for a few seconds bugzilla-daemon
2011-02-06 19:29 ` bugzilla-daemon
2011-05-05 16:26 ` bugzilla-daemon
2011-05-05 18:20 ` bugzilla-daemon
2019-11-19 8:17 ` 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-33969-502@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.