From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28016] New: [REGR] RV635 GPU lockup after enabling unmappable VRAM V2 (KMS, Radeon)
Date: Fri, 7 May 2010 04:41:20 -0700 (PDT) [thread overview]
Message-ID: <bug-28016-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28016
Summary: [REGR] RV635 GPU lockup after enabling unmappable VRAM
V2 (KMS, Radeon)
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: astronomo@op.pl
Created an attachment (id=35492)
--> (https://bugs.freedesktop.org/attachment.cgi?id=35492)
kernel log with the backtrace
I have tested recent branches drm-radeon-testing (last commit
7a1ffce50373c177d3f6eecce52badc40c90e1dd) and drm-next (last commit
9e51159c14c29ebd485a45ba56f148e180d62c29) from
http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git. These branches
contain patches for enabling unmappable VRAM. However, soon after booting I am
getting a GPU lockup and corrupted console and X.
My hardware is laptop ASUS M50SA with 4GB system memory, and graphics 1GB
Mobility Radeon HD 3650.
I am attaching the kernel output with the backtrace and lspci -v output.
--
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:[~2010-05-07 11:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 11:41 bugzilla-daemon [this message]
2010-05-07 11:42 ` [Bug 28016] [REGR] RV635 GPU lockup after enabling unmappable VRAM V2 (KMS, Radeon) bugzilla-daemon
2010-05-07 11:42 ` bugzilla-daemon
2010-05-07 11:48 ` bugzilla-daemon
2010-05-07 13:18 ` bugzilla-daemon
2010-05-07 15:35 ` bugzilla-daemon
2010-05-07 15:36 ` bugzilla-daemon
2010-05-10 10:14 ` [Bug 28016] KMS:RV635:HD3650 GPU lockup bugzilla-daemon
2010-05-10 13:29 ` bugzilla-daemon
2010-05-10 13:51 ` bugzilla-daemon
2010-05-10 13:51 ` bugzilla-daemon
2010-05-10 19:22 ` bugzilla-daemon
2010-05-10 19:30 ` bugzilla-daemon
2010-06-03 19:10 ` bugzilla-daemon
2010-06-03 21:39 ` bugzilla-daemon
2010-06-09 15:21 ` bugzilla-daemon
2010-07-06 4:05 ` 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-28016-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.