From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 20130] New: GT200: nv50 chipset 0xa0 lockup
Date: Sun, 15 Feb 2009 19:50:09 -0800 (PST) [thread overview]
Message-ID: <bug-20130-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=20130
Summary: GT200: nv50 chipset 0xa0 lockup
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: kamilkss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=22971)
--> (http://bugs.freedesktop.org/attachment.cgi?id=22971)
Logs
Hi guys,
I recently mailed in a mmiotrace of my GT200 on which I tried to enable EXA
with no success. I have noticed a new commit
http://cgit.freedesktop.org/mesa/drm/commit/?id=a4ac60a10239bb6d19f6d89f2c044e9b7b29837c
and went ahead with latest git. After issuing startx I get a blank screen and a
complete lockup. Please see the attached logs. I'm unable to provide a
meaningful dmesg since it gets overwritten on the next boot after a lockup (I'm
using Arch Linux). I will be more than happy to help. Thanks!
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2009-02-16 3:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 3:50 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-20130-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-02-16 4:23 ` [Bug 20130] GT200: nv50 chipset 0xa0 lockup bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17 17:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17 17:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17 17:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17 22:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17 22:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17 23:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17 23:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-24 7:27 ` [Bug 20130] GT200: nv50 chipset 0xa0 2D corruption bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-24 7:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-24 7:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-24 7:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-24 10:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-24 21:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-05-28 19:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-02 4:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-18 3:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-20130-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.