From: Andi Kleen <ak@muc.de>
To: Sid Boyce <sboyce@blueyonder.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc3-mm1
Date: Wed, 31 Mar 2004 09:30:22 +0200 [thread overview]
Message-ID: <m3vfkl4goh.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1FzAR-1qq-3@gated-at.bofh.it> (Sid Boyce's message of "Wed, 31 Mar 2004 00:10:09 +0200")
Sid Boyce <sboyce@blueyonder.co.uk> writes:
> Before the messages above ---
> ********* Please consider a BIOS update.
> ********* Disabling USB legacy in the BIOS may also help.
You should really update your BIOS. With this BIOS bug you can
get basically random crashes on 64bit systems. The kernel tries
to work around them in the idle loop, but they can happen elsewhere
too.
-Andi
next parent reply other threads:[~2004-03-31 7:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1Fylv-df-27@gated-at.bofh.it>
[not found] ` <1FzAR-1qq-5@gated-at.bofh.it>
[not found] ` <1FzAR-1qq-3@gated-at.bofh.it>
2004-03-31 7:30 ` Andi Kleen [this message]
2004-03-31 22:47 ` 2.6.5-rc3-mm1 Sid Boyce
[not found] ` <1FzKy-1xG-11@gated-at.bofh.it>
[not found] ` <1FAwU-2gc-11@gated-at.bofh.it>
[not found] ` <1FAQv-2wA-57@gated-at.bofh.it>
2004-03-31 7:34 ` 2.6.5-rc3-mm1 Andi Kleen
2004-03-31 8:29 ` 2.6.5-rc3-mm1 Danny ter Haar
2004-03-31 23:05 ` 2.6.5-rc3-mm1 Sid Boyce
2004-03-31 5:29 2.6.5-rc3-mm1 Paul Blazejowski
-- strict thread matches above, loose matches on Subject: below --
2004-03-30 20:44 2.6.5-rc3-mm1 Sid Boyce
[not found] ` <1080681249.3547.51.camel@watt.suse.com>
2004-03-30 21:57 ` 2.6.5-rc3-mm1 Sid Boyce
2004-03-30 22:04 ` 2.6.5-rc3-mm1 Chris Mason
2004-03-30 22:50 ` 2.6.5-rc3-mm1 Sid Boyce
2004-03-30 23:22 ` 2.6.5-rc3-mm1 Sid Boyce
2004-03-30 22:52 ` 2.6.5-rc3-mm1 Jason Munro
2004-03-30 10:34 2.6.5-rc3-mm1 Andrew Morton
2004-03-31 0:03 ` 2.6.5-rc3-mm1 Greg KH
2004-03-31 0:28 ` 2.6.5-rc3-mm1 Andrew Morton
2004-03-31 2:26 ` 2.6.5-rc3-mm1 Andrew Morton
2004-03-31 7:25 ` 2.6.5-rc3-mm1 Russell King
2004-03-31 8:51 ` 2.6.5-rc3-mm1 Andrew Morton
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=m3vfkl4goh.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/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