From: "Brian P. Austin" <baustin@codemonsters.net>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: Reproduction of NFTL Bug with DOC 2000 288MB FULL DEBUG
Date: Fri, 1 Mar 2002 13:28:34 -0600 [thread overview]
Message-ID: <000f01c1c157$47698de0$5a01a8c0@devicemonsters.com> (raw)
In-Reply-To: 10097.1015010046@redhat.com
I shut down syslog, and everything is going out to the terminal now,
however, it just keeps scrolling
_DoC_WaitReady called for out-of-line wait
accross all my tty's, and I can't stop it!
----- Original Message -----
From: "David Woodhouse" <dwmw2@infradead.org>
To: "Brian P. Austin" <baustin@codemonsters.net>
Cc: <linux-mtd@lists.infradead.org>
Sent: Friday, March 01, 2002 1:14 PM
Subject: Re: Reproduction of NFTL Bug with DOC 2000 288MB FULL DEBUG
>
> Hmm. Did you do this from scratch, starting by reformatting the NFTL
again?
> It doesn't look like it.
>
> Use the M-Systems DFORMAT (version 4.2) if you can, rather than
nftl_format.
> If you do use nftl_format, make sure the NFTL kernel module isn't loaded
> while you do so.
>
> Then get logs again, preferably over a serial console, because syslog is
> lossy.
>
> I may have a 288MiB unit here, in fact - I'll see if I can reproduce it
> myself.
>
> --
> dwmw2
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2002-03-01 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 19:59 Reproduction of NFTL Bug with DOC 2000 288MB FULL DEBUG Brian P. Austin
2002-03-01 19:14 ` David Woodhouse
2002-03-01 19:28 ` Brian P. Austin [this message]
2002-03-01 19:49 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2002-03-01 20:39 Brian P. Austin
2002-03-01 21:27 Brian P. Austin
2002-03-01 22:56 ` David Woodhouse
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='000f01c1c157$47698de0$5a01a8c0@devicemonsters.com' \
--to=baustin@codemonsters.net \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.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