and still the patch I included applied to 2.5.14-dj2...
> > I found this the hard way: severe filesystem damage and system lockup and a
> > kernel (2.4.19-pre8) panic because the root partition could not be mounted
> > (as reported before).
>Ah, 2.4.19 would be Marcelo's world.
sorry for the misunderstanding, after the crash I booted into 2.4.19-pre8
to recover my system and that did not work because the 2.5.14-dj2 kernel
destroyed the first descriptors of my ext2-filesystem. It was not meant to
report the kernel panic but to show the severity of the problem that was
done by the 2.5.14-dj2 kernel...
> > The following patch fixes this, apllies with an offset of -2 lines:
> > -- begin patch --
> > --- linux-2.5.10/drivers/ide/ide-taskfile.c Wed Apr 24 16:15:19 2002
> > +++ linux/drivers/ide/ide-taskfile.c Fri Apr 26 15:44:42 2002
> > @@ -202,7 +202,7 @@
> > ata_write_slow(drive, buffer, wcount);
> > else
> > #endif
> > - ata_write_16(drive, buffer, wcount<<1);
> > + ata_write_16(drive, buffer, wcount);
> > }
> > }
>Yes, it does look like a variant of this patch is missing there too.
>Andre, Confirm? Line 112 looks suspect back there. Or is 2.4 doing
>different voodoo with the wcount ?
So this patch applied to 2.5.14-dj2 and I did not try to apply it to a 2.4
tree... again sorry for the misunderstanding.
> > 2) After boot the system is not responsive to the keyboard, logging in via
> > ssh and doing a `insmod psmouse` followed by a `rmmod psmouse` results in a
> > working keyboard...
> > before and after insmod there is no interrupt 1 listed in /proc/interrupts,
> > but after doing the rmmod it is listed: " 1: 52 XT-PIC
> > i8042"
> > the mouse interrupt is listed as " 12: 154 XT-PIC i8042"
> > the following message was issued after `rmmod psmouse`: "input: AT Set 2
> > keyboard on isa0060/serio0"
>Odd, That's one for Vojtech to think about 8-)
2.5.13-dj2 also had this problem, I can't remember if 2.5.13-dj1 had the
>Thanks for the report.
No thanks, it's fun to play with these kernels (even to recover a heavily
damaged system :)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/