From: Arjan van de Ven <arjan@linux.intel.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Thomas Renninger <trenn@suse.de>, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, Bob Moore <robert.moore@intel.com>,
Lin Ming <ming.m.lin@intel.com>, Len Brown <len.brown@intel.com>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Huang Cheng <cheng.huang@intel.com>,
firmwarekit-discuss@bughost.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Check for BIOS bugs - Original Subject: Re: [PATCH 23/70] ACPICA: Workaround for reversed _PRT entries from BIOS
Date: Tue, 08 Jul 2008 08:40:21 -0700 [thread overview]
Message-ID: <48738A65.9060905@linux.intel.com> (raw)
In-Reply-To: <20080707111207.GH5643@ucw.cz>
Pavel Machek wrote:
> Hi!
>
>>> Some BIOSs erroneously reverse the _PRT SourceName and the
>>> SourceIndex. Detect and repair this problem. MS ACPI also allows
>>> and repairs this problem, thus ACPICA must also.
>> It would be great to have an interface to report this as a BIOS defect.
>>
>> Something like:
>>
>> FIRMWARE_BUG_ON(FIRM_WARN, "erroneously reversed the _PRT source_name", ACPI_
>> Bug);
>>
>> FIRMWARE_BUG_ON(severity, description, component);
>
> Yes, please.
>
> I'd also like HARDWARE_BUG_ON(), with similar usage.
>
> With all the preload-linux-on-foo project, we have some chance to make
> BIOS vendors fix their stuff if we can easily diagnose errors in
> there.
also we can tie this to kerneloops.org to make a list of top known firmware/hardware bugs, seperate from the kernel code bugs
>
next prev parent reply other threads:[~2008-07-08 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1213947852-10924-1-git-send-email-lenb@kernel.org>
[not found] ` <deade3c973eb9c98d2a6cfed658bbb49e693894a.1213947350.git.len.brown@intel.com>
2008-07-01 8:33 ` Check for BIOS bugs - Original Subject: Re: [PATCH 23/70] ACPICA: Workaround for reversed _PRT entries from BIOS Thomas Renninger
2008-07-07 11:12 ` Pavel Machek
2008-07-08 15:40 ` Arjan van de Ven [this message]
2008-07-08 19:34 ` Brown, Len
2008-07-08 22:11 ` Pavel Machek
2008-07-09 8:51 ` Thomas Renninger
2008-07-17 20:31 ` Brown, Len
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=48738A65.9060905@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=cheng.huang@intel.com \
--cc=firmwarekit-discuss@bughost.org \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=pavel@suse.cz \
--cc=robert.moore@intel.com \
--cc=trenn@suse.de \
/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