From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 25658] New: Move to loadable firmware breaks suspend on nVidia 9800M
Date: Tue, 15 Dec 2009 11:25:55 -0800 (PST) [thread overview]
Message-ID: <bug-25658-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=25658
Summary: Move to loadable firmware breaks suspend on nVidia 9800M
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: tavianator-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Since the move to loadable firmware ctx voodoo, suspend is broken on my nVidia
9800M (NV92). Upon running pm-suspend, or hitting the keyboard shortcut, I get
a flashing cursor on a black screen, but it sits there forever instead of
suspending. There's no response to magic SysRq or ssh -- I have to hard-reset
it. To be sure, I bisected it down to the commits starting with
6303a1a6ab13da61b0352101e7a974ca446d6a36 (use fw loader interface for
ctxprog/ctxvals). Anything before that seems to work; anything after
c2f85058e99c542a82cfc893fbe5ebd2b86c666e (add back the ctxprog/ctxvals we have
as loadable firmware) is broken.
--
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-12-15 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 19:25 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-25658-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-12-15 19:27 ` [Bug 25658] Move to loadable firmware breaks suspend on nVidia 9800M bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-15 23:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-16 0:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-16 0:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-16 6:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-16 7:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-16 7:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-16 11:40 ` 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-25658-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.