From: Borislav Petkov <bp@alien8.de>
To: Denis Lotarev <dlotarev@yahoo.com>
Cc: linux-kernel@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
Len Brown <len.brown@intel.com>
Subject: Re: [FIRMWARE BUG] Lenovo x120e
Date: Wed, 28 Nov 2012 16:12:47 +0100 [thread overview]
Message-ID: <20121128151247.GA14635@liondog.tnic> (raw)
In-Reply-To: <1354109265.69986.YahooMailClassic@web163004.mail.bf1.yahoo.com>
On Wed, Nov 28, 2012 at 05:27:45AM -0800, Denis Lotarev wrote:
> Im using kernel (Linux initbox 3.6.7-1-ARCH #1 SMP PREEMPT Sun Nov 18 10:11:22 CET 2012 x86_64 GNU/Linux) and i see some problems at booting... So dmesg output with BUG lines:
>
> $ dmesg |grep Bug
> [ 1.363154] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
> [ 1.373784] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
> [ 1.380827] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
> [ 1.433354] pnp 00:09: [Firmware Bug]: [mem 0x00000000-0xffffffffffffffff disabled] covers only part of AMD MMCONFIG area [mem 0xf8000000-0xf9ffffff]; adding more reservations
> [ 3.349658] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
Nothing to worry about, just ACPI in BIOS is not implementing _BQC
method with which you can query the initial brightness level of the
display device. Frankly, I'm not getting any smarter from the commit
message as to what it even got added for:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=98758faffc86ee6fe9504eeab75481ee7c1aa860
"kinda firmware bug"?? :-)
Maybe Zhang/Len can shed more light on the matter.
Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-11-28 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 13:27 Denis Lotarev
2012-11-28 15:12 ` Borislav Petkov [this message]
2012-11-28 15:20 ` Denis Lotarev
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=20121128151247.GA14635@liondog.tnic \
--to=bp@alien8.de \
--cc=dlotarev@yahoo.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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
all inboxes | Powered by JetHome®