From: Voluspa <lista1@telia.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.16-rc2] Error - nsxfeval - And uncool silence from kernel hackers.
Date: Fri, 10 Feb 2006 13:37:14 +0100 [thread overview]
Message-ID: <20060210133714.1863aab5.lista1@telia.com> (raw)
In-Reply-To: <20060210042419.GA27457@kroah.com>
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
--
next prev parent reply other threads:[~2006-02-10 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 23:01 [2.6.16-rc2] Error - nsxfeval - And uncool silence from kernel hackers Voluspa
2006-02-09 23:32 ` Greg KH
2006-02-10 2:50 ` Voluspa
2006-02-10 4:24 ` Greg KH
2006-02-10 12:37 ` Voluspa [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-09 23:13 Moore, Robert
2006-02-10 2:15 ` Voluspa
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=20060210133714.1863aab5.lista1@telia.com \
--to=lista1@telia.com \
--cc=greg@kroah.com \
--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