Re: FS-corrupting IDE bug still in 2.4.20-rc3

Neil Conway (nconway_kernel@yahoo.co.uk)
Wed, 27 Nov 2002 12:36:34 +0000 (GMT)


Hi Marc...

--- Marc-Christian Petersen <m.c.p@wolk-project.de> wrote:
> You may try that patch with a VIA boxen and I am quite sure you may
> experience
> a bug that none of your harddisks may be recognized and result in a
> panic();

Aha... Actually, if you read the patch, you'll see why that's no
longer the case. I had in fact forgotten that I'd had to patch the
patch to make my VIA box boot (it was 6 months ago now!). I now do "if
(hwgroup) ..." in the test-for-busy section. So, the new patch does
NOT now cause panics on VIA.

> I had the same Fix in WOLK some time ago and many users with VIA
> chipset
> complained that with the fix their mashine does not recognize any
> harddisks
> and after trying to recognize they had a panic();

Yes, only some chipsets end up in ide_config_drive_speed() at bootup;
notably the PIIX doesn't and the VIA does. Mea culpa! I should have
posted the fixed patch perhaps, but then it was deprecated and I
thought Andre had a better fix in hand. (BTW, when you say you had
"the same fix", you mean you fixed it independently or you used my
patch from May '02?)

> Maybe it's working for you with some VIA chipsets but I removed that
> fix and
> after removal all users with VIA were happy. I've never heard of a FS
> corruption of them.

Well, do they have the trigger ingredients? You MUST have an IDE CDROM
sharing a bus with a HDD. Also, the perfect recipe for disk corruption
is to reboot, and then log in to your chosen desktop, and while it's
hammering the disk starting everything up, it should fire off
"magicdev", which in turn loads ide-cd: BOOM. RedHat 7.x with GNOME
does things in this order. YMMV.

Neil

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
-
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/