Re: [2.6.16-rc2] Error - nsxfeval - And uncool silence from kernelhackers.

[Voluspa]

On Thu, 9 Feb 2006 20:24:19 -0800 Greg KH wrote:
> On Fri, Feb 10, 2006 at 03:50:51AM +0100, Voluspa wrote:
> > On Thu, 9 Feb 2006 15:32:33 -0800 Greg KH wrote:
> > > On Fri, Feb 10, 2006 at 12:01:01AM +0100, Voluspa wrote:
> > > > 
> > > > Booted 2.6.16-rc2 on my AMD x86_64 notebook and saw something new in the
> > > > log (different from 2.6.15):
> > > 
> > > So, 2.6.16-rc2 works just fine, with out your reversal of that one
> > > patch?
> > 
> > Eh, I bundled two issues in my rant. 1) nsxfeval, which the ACPI guys
> > have confirmed is pure noise and can be forgotten. 2) "PCI: Failed to
> > allocate mem resource" which has been there since the commit I pointed
> > to, and never has effected the machine negatively (as far as I can tell).
> > So yes, 2.6.16-rc2 seems fine, and I don't patch it for that PCI thing.
> > It's just that the message is present and will worry people 'forever'
> > if nothing is done.
> 
> As long as everything is working properly, you can happily ignore the
> issue and blame your bios vendor for making such a stupid mistake :)

The issue came bouncing in from fedora-list to lkml. I've never cared one
way or the other. And while I have no love for a BIOS maker (Phoenix) that
only give you options like "Are you happy with the settings as is: Yes/Yes",
the occasional kernel hacker has also been seen wearing brown paper bags.

Something like a quirk/white/black-list could be used to make it invisible.
But as I said, me not really care (and neither do you ;-) So let's just
bury this thread.

Mvh
Mats Johannesson
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/