From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 35374] New: nouveau: nv50, regression "GPU lockup - switching to software fbcon" introduced in 2.6.38-rc8
Date: Wed, 16 Mar 2011 16:42:33 -0700 (PDT) [thread overview]
Message-ID: <bug-35374-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=35374
Summary: nouveau: nv50, regression "GPU lockup - switching to
software fbcon" introduced in 2.6.38-rc8
Product: xorg
Version: 7.4
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: tallica-h7QdYz1kt/Q@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=44527)
--> (https://bugs.freedesktop.org/attachment.cgi?id=44527)
dmesg log, 2.6.38 with commit 73412c3854c877e5f37ad944ee8977addde4d35a reverted
There's a regression introduced in kernel >=2.6.38-rc8. It's in nouveau/master
(commit 7972f91c24bb66643d76cf635faea78eb184e6b6) as well. Dmesg shows: "GPU
lockup - switching to software fbcon". I've done a git bisect. The problematic
commit is: 73412c3854c877e5f37ad944ee8977addde4d35a "drm/nouveau: allocate
kernel's notifier object at end of block". I reverted that commit on top of the
2.6.38 to confirm the issue.
Reproducible: always
--
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-03-16 23:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 23:42 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-35374-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-03-16 23:44 ` [Bug 35374] nouveau: nv50, regression "GPU lockup - switching to software fbcon" introduced in 2.6.38-rc8 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-16 23:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-18 17:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-18 20:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-18 20:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-18 20:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-18 20:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-04-22 1:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-04-22 2:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-04-22 14:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-04-22 14:37 ` 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-35374-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.