From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 39550] Brightness stuck to low value after suspend/resume
Date: Mon, 20 Feb 2012 14:16:42 +0000 [thread overview]
Message-ID: <bug-39550-8800-gOllgDVLLV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-39550-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=39550
--- Comment #26 from Walther <walther.MD-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2012-02-20 06:16:42 PST ---
I repeated testing using kernel 3.3.0 RC4, and results are similar:
nvapeek (before):
0000e100: 001c1100
0000e28c: 00000100
0000e104: 72267640 0441474b
0000e280: 44444747 00000000
After:
0000e100: 001c1100
0000e28c: 00000100
0000e104: 72267240 0441474b
0000e280: 44444747 00000000
Compared to the previous version, the only change is that 0x1000 was added to 0xe104 (and 0x400 is still unset on resume). And, of course, brightness controls
ceased to response after resuming.
PS: What still worries me is that after resuming nvagetbios still fails, that is a definite vbios bug/corruption somewhere, isn't it...
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-02-20 14:16 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 11:35 [Bug 39550] New: Brightness stuck to low value after suspend/resume bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-39550-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-07-26 12:19 ` [Bug 39550] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-26 18:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-26 18:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-26 19:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-26 20:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-10 6:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-10 6:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-10 11:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-10 22:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-22 21:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-25 10:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-25 11:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-25 12:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-25 12:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-26 19:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-27 14:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-27 18:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-28 15:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-09-28 15:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-12 9:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-01-30 21:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-01-31 1:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-14 14:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-14 15:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-14 15:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-20 14:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2012-04-04 9:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-04 17:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-06 1:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-11 11:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-14 6:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 13:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-24 15:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-06 18:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-06 20:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-13 17:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-15 7:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-18 19:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-29 12:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-12 8:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-13 8:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 4:28 ` [Bug 39550] [NV96] Brightness stuck to low value after suspend/resume on HP Elitebook 8530w bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 12:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 15:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 16:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 16:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-01 12:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-01 14:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-01 15:28 ` 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-39550-8800-gOllgDVLLV@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.