From: Tejun Heo <tj@kernel.org>
To: heinzm@redhat.com
Cc: Matthew Garrett <mjg59@srcf.ucam.org>, linux-ide@vger.kernel.org
Subject: Re: Check for broken HP bioses in ahci.c appears too broad
Date: Mon, 09 Nov 2009 13:29:25 +0900 [thread overview]
Message-ID: <4AF79AA5.2030803@kernel.org> (raw)
In-Reply-To: <1257525348.20269.19.camel@o>
Heinz Mauelshagen wrote:
> On Fri, 2009-11-06 at 16:28 +0000, Matthew Garrett wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=533402 describes a case
>> where a machine is falling foul of the hp dv6 check in ahci.c. However,
>> BIOS version F.04 appears to be the latest available for this machine -
>> I suspect that the dv6 parameter is too broad and is picking up machines
>> outside those with the affected BIOSes.
>>
>> Heinz, could you attach the contents of
>> /sys/devices/virtual/dmi/id/product_name,
>> /sys/devices/virtual/dmi/id/product_version and
>> /sys/devices/virtual/dmi/id/bios_*?
Maybe we should use date instead of version?
Thanks.
--
tejun
prev parent reply other threads:[~2009-11-09 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 16:28 Check for broken HP bioses in ahci.c appears too broad Matthew Garrett
2009-11-06 16:35 ` Heinz Mauelshagen
2009-11-09 4:29 ` Tejun Heo [this message]
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=4AF79AA5.2030803@kernel.org \
--to=tj@kernel.org \
--cc=heinzm@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=mjg59@srcf.ucam.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).