From: Stephen Clark <Stephen.Clark@seclark.us>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] quiet MMCONFIG related printks
Date: Wed, 03 Jan 2007 14:29:34 -0500 [thread overview]
Message-ID: <459C041E.90409@seclark.us> (raw)
In-Reply-To: <1167843673.3127.162.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
>On Wed, 2007-01-03 at 08:49 -0800, Jesse Barnes wrote:
>
>
>>On Wednesday, January 3, 2007 5:53 am, Arjan van de Ven wrote:
>>
>>
>>>On Mon, 2007-01-01 at 21:01 -0800, Jesse Barnes wrote:
>>>
>>>
>>>>Using MMCONFIG for PCI config space access is simply an
>>>>optimization, not a requirement. Therefore, when it can't be used,
>>>>there's no need for KERN_ERR level message. This patch makes the
>>>>message a KERN_INFO instead to reduce some of the noise in a kernel
>>>>boot with the 'quiet' option. (Note that this has no effect on a
>>>>normal boot, which is ridiculously verbose these days.)
>>>>
>>>>
>>>this is wrong, please leave this loud complaint in...
>>>
>>>
>>So the issues as I understand them:
>> o some BIOSes are broken and don't properly map MCFG space (though
>> according to Petr V. reserving MCFG space in e820 is optional, so
>> the test may be slightly wrong as-is)
>>
>>
>
>it's optional but it's the best test we have for "is the bios total
>crap" ;(
>
>
>
>> o MCFG space is required for (many) PCIe devices (any regular PCI
>> devices?)
>>
>>
>
>it's not required for *many* (it can't be, windows XP doesn't use MCFG),
>but it's required for some of the advanced PCI-E features
>
>
>
>> o often, there's nothing the user can do to address the points above
>>
>>
>
>other than complain to the vendor.
>
>
>
>>So where does that leave us? I've got what I consider to be a stupid
>>error message in my log.
>>
>>
>
>contact your bios vendor.
>
>
>
>> My system behavior isn't affected in any way
>>(at least that I can tell), yet I get a loud complaint at boot time.
>>
>>I guess I just have to live with it?
>>
>>
>
>We really really should complain about bios issues. If only to make sure
>vendors who do pay attention to linux have a chance of finding and
>fixing them (and via the firmware kit, several big vendors pay attention
>early on nowadays)
>
>
>
Hi Arjan,
Do you have a list of E-Mail addresses for the people we should be
complaining to. I have an
Asus VBI laptop that spews all kinds of error messages when I boot the
firmware test kit cd, but
I have no idea who to complain to about this, ASUS? Intel? Heck Intel
puts out the test kit, if they
are going to say it is VBI why don't the make the vendors do the bios
correctly?
Regards,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next prev parent reply other threads:[~2007-01-03 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 5:01 [PATCH] quiet MMCONFIG related printks Jesse Barnes
2007-01-02 10:36 ` Alan
2007-01-02 16:37 ` Jesse Barnes
2007-01-03 13:52 ` Arjan van de Ven
2007-01-03 13:53 ` Arjan van de Ven
2007-01-03 16:49 ` Jesse Barnes
2007-01-03 17:01 ` Arjan van de Ven
2007-01-03 19:29 ` Stephen Clark [this message]
2007-01-03 17:20 ` Jesse Barnes
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=459C041E.90409@seclark.us \
--to=stephen.clark@seclark.us \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=jbarnes@virtuousgeek.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