lkml.org 
[lkml]   [2002]   [Aug]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.4.20-pre4-ac1 trashed my system
On Sat, Aug 31, 2002 at 12:04:20AM -0500, Mike Isely wrote:
>
>
> > OK, I have some good news and some bad news.
> >
> > The bad news is that I replicated the corruption.
> >
> > The good news is that I replicated the corruption. Oh, and I can
> > cause it on demand, and not lose my system in the process. I can
> > provide LOTS and LOTS of details now. What do you want to know?
> >
>
> [...]
>
> I've done some more tests and have more information now. No smoking
> gun yet, but a few more clues.
>
> 1. I moved the 160GB drive away from the Promise controller and
> reattached it to the motherboard chipset's controller ("VIA
> Technologies, Inc. Bus Master IDE (rev 06)", by the way according
> to lspci). Then I booted 2.4.20-pre4-ac1 (the "bad" kernel) and
> fsck'ed the big partition again. It passed. Then I moved the
> drive back to the Promise controller, booted the same OS and
> fsck'ed again. Failure.
>
> 2. I booted 2.4.19-ac4 with the 160GB drive attached to the Promise
> controller and watched the kernel log output. There's no message
> about any missing 80 pin cable. This is different than
> 2.4.20-pre4-ac1 which complains that I allegedly don't have an 80
> pin cable plugged. However the cable is there but the driver
> downshifts the interface to 33MHz anyway. I described this

Note that 33 MHz isn't 33 MB/sec (UDMA2). Question remains, what you wanted to
say.


--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.072 / U:7.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site