All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test1 - CRC errors on floppy block the whole system
Date: Wed, 16 Jul 2003 14:27:52 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0307161415210.29886@chaos> (raw)
In-Reply-To: <200307162159.16021.arvidjaar@mail.ru>

On Wed, 16 Jul 2003, Andrey Borzenkov wrote:

> Under KDE I went into floppy and made rm *. After this keyboard was lost -
> even CAPS LED did not respond to keypress. I stil could use mouse to start
> new windows and even execute some commands by copy'n'paste from available
> text :)
>
> Attempt to exit KDE ended in black screen. I had to press reset; after that
> the following text was found in syslog (slightly abridged, it had much more
> those "floppy driver state"s).
>
> Floppies are not that robust, everyone knows it. It is rather unfriendly to
> handle media errors in such manner :)
[SNIPPED...]

Yes. You should see how it handles a SCSI disk error!

A media error when running `badblocks` on Linux Version 2.6.0 results
in the same misbehavior with a BusLogic controller.

I tried to boot, it came up but encountered some kind of disk
error. I tried to run `badblocks` on an unmounted partition
that reported zillions of errors during the normal e2fsck check
upon startup.

I booted several times with `init=/bin/bash`. Most times it would
panic with 'trying to kill init' errors. One time I was able to
get it up and I attempted to run badblocks. --Impossible... It
thinks everything is bad and badblocks doesn't help by re-reading
bad blocks. The SCSI system takes 1 minute to reset after a bad
block. I gave up around noon after trying since 8:00 in the AM.
Because of the re-read by badblocks, it's possible that there
may be only one bad block that it never gets past!

With 2.4.20, badblocks reports no errors and e2fsck was able to
rebuild all partitions trashed by version 2.6.0.

If anybody has a Buslogic driver fix, I'll be happy to try it.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
            Note 96.3% of all statistics are fiction.


      reply	other threads:[~2003-07-16 18:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 17:59 2.6.0-test1 - CRC errors on floppy block the whole system Andrey Borzenkov
2003-07-16 18:27 ` Richard B. Johnson [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=Pine.LNX.4.53.0307161415210.29886@chaos \
    --to=root@chaos.analogic.com \
    --cc=arvidjaar@mail.ru \
    --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.