From: David Ford <david+cert@blue-labs.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, "Adam J. Richter" <adam@yggdrasil.com>
Subject: Re: 2.5.59 OOPS w/ fdisk & devfs
Date: Thu, 06 Feb 2003 17:54:47 -0500 [thread overview]
Message-ID: <3E42E7B7.2080900@blue-labs.org> (raw)
In-Reply-To: <20030206135138.3c083007.akpm@digeo.com>
Well, don't jump too fast :)
I have been having extreme hardware issues with this box for the past
several hours. I thought it was 2.5.59 giving me grief but an old
kernel I had laying around presented similar issues. I'm busy swapping
cables, memory, etc to see who is being the bad guy.
So far, I've had issues with reiserfs, raw dd, mkreiserfs, tar, cp, mv
(insert a lot of shell commands), interpreters, you name it. Nothing
seems common except that it all occurs when hda data is going somewhere
else. I just swapped my udma66 cable on hda and I'm trying to stress
test hda now.
David
Andrew Morton wrote:
>David Ford <david+cert@blue-labs.org> wrote:
>
>
>>Unable to handle kernel paging request at virtual address 6b6b6b87
>>...
>>EIP is at _devfs_unhook+0x2b/0x70
>>
>>
>
>
>Look. devfs is sick. Richard has disappeared. Al did some work on it and
>also disappeared. Adam laid it on the ground and drove a truck over it, and
>I had that patch in -mm for two or three weeks and had one single, sole, sad,
>sorry report from a tester.
>
>
prev parent reply other threads:[~2003-02-06 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 21:15 2.5.59 OOPS w/ fdisk & devfs David Ford
2003-02-06 21:51 ` Andrew Morton
2003-02-06 22:54 ` David Ford [this message]
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=3E42E7B7.2080900@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=adam@yggdrasil.com \
--cc=akpm@digeo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.