[3536] in linux-scsi channel archive
Re: SMP 2.1.90-pre3 SCSI kernel panic
daemon@ATHENA.MIT.EDU (Doug Ledford)
Mon Mar 16 08:04:56 1998
Date: Mon, 16 Mar 1998 07:02:37 -0600 (CST)
From: Doug Ledford <dledford@dialnet.net>
To: sistema@readysoft.es
cc: eowmob@exp-math.uni-essen.de, linux-scsi@vger.rutgers.edu
In-Reply-To: <199803161248.NAA25525@macia.readysoft.es>
On Mon, 16 Mar 1998 sistema@readysoft.es wrote:
> Ok. Iīve already activated remapping bits, running 2.0.33.
> But Iīve been able to backup all scsi devices with no read error many
> times and keep on working. No SCSI errors.
>
> Why does 2.1.89 and over generate so many failures doing exactly the
> same? It doesnīt look as a hardware problem. Maybe itīs an SMP issue or
> a scsi problem. I would discard HD errors.
Because 2.1.x is *not* doing exactly the same. If it were, it would be
2.0.33 wouldn't it? You're making the assumption that much of the code in
the linux kernel is static and does things exactly the same from version
to version. This assumption is false. Secondly, those errors you posted
were Peripheral Write Fault errors. That's not reading. That also goes
back to what I mentioned about the possible usage of portions of the
ext2fs that haven't been used in the past. In short, there are a lot of
possibilities and to discount anything yet is premature. What we do know,
is that the HD is saying it can't write something that it accepted as a
valid command. It wasn't out of range, it suppossedly went to real
sectors, etc, but the drive says it can't do it. That's the reason that
I've been bringing up hardware.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
