From: Voluspa <lista1@comhem.se>
To: "Ojciec Rydzyk" <69rydzyk69@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
be-news06@lina.inka.de, jengelh@linux01.gwdg.de, greg@kroah.com
Subject: Re: Several errors in kernel
Date: Mon, 19 Jun 2006 16:30:07 +0200 [thread overview]
Message-ID: <20060619163007.2a681aaa.lista1@comhem.se> (raw)
In-Reply-To: <32124b660606190706g2d44414ck3860fd6ae82ec628@mail.gmail.com>
On Mon, 19 Jun 2006 16:06:26 +0200 Ojciec Rydzyk wrote:
> And what is wrong with my BIOS that kernel cannot allocate mem
> resource. What is the reason? (I just would like to know what should I
> post to my BIOS vendor :P)
It's a good question, so I'm cc:-ing the rest of the thread recipients
and adding Greg KH, so he can fight it out with anyone interested. Me,
I've given up on the issue. But as I predicted, it will hunt the list
until hidden...
Greg, here's my reply, sorry didn't quote anything from the original
message, but thread starts at:
http://marc.theaimsgroup.com/?t=115066436000002&r=1&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=115066427121999&w=2
I wrote:
>>The nsxfeval is completely harmless and has been fixed in the
>>"ACPI: Subsystem revision 20060310" present in -mm kernels.
>>
>>The "Failed to allocate mem resource" is also harmless but Greg KH
>>has decided to not hide/fix it. Our BIOS vendors are to blame.
>>
>>For a summary see:
>>[Re: [2.6.16-rc2] Error - nsxfeval - And uncool silence from kernel
>>hackers.]
>>http://marc.theaimsgroup.com/?l=linux-kernel&m=113957514307078&w=2
>>
>>I started the thread at:
>>http://marc.theaimsgroup.com/?l=linux-kernel&m=113952620328363&w=2
Mvh
Mats Johannesson
--
next prev parent reply other threads:[~2006-06-19 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 13:58 Voluspa
[not found] ` <32124b660606190706g2d44414ck3860fd6ae82ec628@mail.gmail.com>
2006-06-19 14:30 ` Voluspa [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-18 20:54 Ojciec Rydzyk
2006-06-18 21:16 ` Bernd Eckenfels
2006-06-19 12:06 ` Jan Engelhardt
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=20060619163007.2a681aaa.lista1@comhem.se \
--to=lista1@comhem.se \
--cc=69rydzyk69@gmail.com \
--cc=akpm@osdl.org \
--cc=be-news06@lina.inka.de \
--cc=greg@kroah.com \
--cc=jengelh@linux01.gwdg.de \
--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
Powered by JetHome