From: Christoph Hellwig <hch@infradead.org>
To: Matthew Harrell <mharrell-dated-1048647183.ec4450@bittwiddlers.com>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.65 jaz drive devfs oops
Date: Fri, 21 Mar 2003 09:05:11 +0000 [thread overview]
Message-ID: <20030321090510.A28886@infradead.org> (raw)
In-Reply-To: <20030321025300.GA13772@bittwiddlers.com>; from mharrell-dated-1048647183.ec4450@bittwiddlers.com on Thu, Mar 20, 2003 at 09:53:00PM -0500
On Thu, Mar 20, 2003 at 09:53:00PM -0500, Matthew Harrell wrote:
>
> And, even with "devfs=nomount" on the boot line and no devfs used I still
> get the same error once the jaz drive totally cycles down.
Is the OOPS with devfs=nomount exactly the same? If no or you're
unsure please post it, too.
> Besides building the kernel without devfs is there a good solution for this?
Well, not compiling in devfs is always a good idea :) But we should fix
this anyway.
next prev parent reply other threads:[~2003-03-21 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 19:14 2.5.65 jaz drive devfs oops Matthew Harrell
2003-03-19 19:34 ` Christoph Hellwig
2003-03-19 21:45 ` Matthew Harrell
2003-03-19 23:57 ` Matthew Harrell
2003-03-21 2:53 ` Matthew Harrell
2003-03-21 9:05 ` Christoph Hellwig [this message]
2003-03-21 12:14 ` Matthew Harrell
2003-03-21 14:38 ` Matthew Harrell
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=20030321090510.A28886@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mharrell-dated-1048647183.ec4450@bittwiddlers.com \
/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