public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn <core@enodev.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Buffer I/O error on device hde3, logical block 4429
Date: 30 Jul 2003 12:21:52 -0500	[thread overview]
Message-ID: <1059585712.11341.24.camel@localhost> (raw)

I am running 2.6.0-test2-mm1, and upon boot have received a gift of many
"Buffer I/O error on device hde3" messages in my log. After they quit,
they never seem to come back.

I'd just like to know what might cause this? I see fs/buffer.c is
telling me this, but I don't know what is failing.

One thing of note, I just upgraded my CPU from an Athlon XP 1800+ to a
2400+, and had to disable IO-APIC, and shut APIC off in my BIOS.

My hardware: http://www.enodev.com/info.html
(If I should include more info let me know)

             reply	other threads:[~2003-07-30 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 17:21 Shawn [this message]
2003-07-30 19:15 ` Buffer I/O error on device hde3, logical block 4429 Shawn
2003-07-30 19:25   ` Marc-Christian Petersen
2003-07-30 19:39     ` Shawn
2003-07-30 22:16 ` 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=1059585712.11341.24.camel@localhost \
    --to=core@enodev.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