From: Valdis.Kletnieks@vt.edu
To: Greg KH <gregkh@suse.de>
Cc: akpm@linux-foundation.org, Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: mmotm 2011-03-02 - ACPI/sysfs WARNING with NVidia graphics card
Date: Thu, 03 Mar 2011 23:28:50 -0500 [thread overview]
Message-ID: <8842.1299212930@localhost> (raw)
In-Reply-To: Your message of "Thu, 03 Mar 2011 16:05:50 PST." <20110304000550.GA2073@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
On Thu, 03 Mar 2011 16:05:50 PST, Greg KH said:
> > [ 0.818236] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
>
> Have you tried this option?
>
> There's nothing sysfs can do here, sorry, it really looks like you have
> a BIOS/firmware problem.
Well, (a) it's been saying "try it if the current driver doesn't work" - and
things have worked just fine all along (or more properly, if it's broken in
behavior, I haven't actually seen the effects...)
and (b) Something changed very recently to add the WARNING, which wasn't there
in rc5-next-2011022.
And (c) I doubt that's going to fix the WARNING, because looking at drivers/
acpi/video.c, the variable allow_duplicates is checked in exactly *ONE* place,
which is *after* the printk:
if (status == AE_ALREADY_EXISTS) {
printk(KERN_WARNING FW_BUG
"Duplicate ACPI video bus devices for the"
" same VGA controller, please try module "
"parameter \"video.allow_duplicates=1\""
"if the current driver doesn't work.\n");
if (!allow_duplicates)
return -ENODEV;
}
So since the warning triggers before we see the printk(), setting the variable
won't make a difference because we warn before we ever get into that if
statement.
Now, maybe we need to be checking allow_duplicates earlier and/or in other
places - but I'll let somebody who actually understands the code to decide taht. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-03-04 4:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 0:52 mmotm 2011-03-02-16-52 uploaded akpm
2011-03-03 2:05 ` Stephen Rothwell
2011-03-03 2:17 ` Andrew Morton
2011-03-03 2:30 ` Stephen Rothwell
2011-03-03 8:26 ` Sedat Dilek
2011-03-03 20:50 ` mmotm 2011-03-02-16-52 uploaded (linux-next: drivers/staging/epca - missing header files) Randy Dunlap
2011-03-03 21:06 ` Greg KH
2011-03-03 23:50 ` mmotm 2011-03-02 - ACPI/sysfs WARNING with NVidia graphics card Valdis.Kletnieks
2011-03-04 0:05 ` Greg KH
2011-03-04 4:28 ` Valdis.Kletnieks [this message]
2011-03-04 5:25 ` Zhang Rui
2011-03-04 8:56 ` tun: Failed to create tun sysfs files [was: mmotm 2011-03-02-16-52 uploaded] Jiri Slaby
2011-03-04 9:06 ` tun: Failed to create tun sysfs files David Miller
2011-03-04 9:37 ` Jiri Slaby
2011-03-05 8:04 ` tun routing is broken [was: tun: Failed to create tun sysfs files] Jiri Slaby
2011-03-05 8:10 ` tun routing is broken David Miller
2011-03-05 8:17 ` Jiri Slaby
2011-03-05 8:26 ` Jiri Slaby
2011-03-07 12:54 ` Jiri Kosina
2011-03-05 11:48 ` Valdis.Kletnieks
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=8842.1299212930@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).