Miquel van Smoorenburg wrote:
> I was running 2.5.72-mm2 on our transit usenet news server
> (700 GB in/day and 1 TB out/day) which ran just fine, until I
> had some ext3 corruption on the /news partition. I remember
> having seen something about this in the -mm changelogs.
> So I tried 2.5.74 and 2.5.74-mm2, but with those kernels the
> siimage.c driver doesn't work. The card is detected, but a bit
> later in the boot process its IRQ is disabled and it won't work.
Ok. Can you send me the "lspci -vxx" output for your IDE chip?
The most likely reason for the breakage is that the siimage thing claims it
isn't a proper IDE storage device in legacy mode, and that means that newer
kernels won't try to probe for interrupts: they will just use the PCI
interrupt directly. That helps on machines with shared interrupts where
probing really doesn't work that well, but it can cause problems if the
PCI IDE controller is confused (and tries to implement a legacy IDE device,
but does it wrong).
If this is indeed the problem, then you could try fixing it by adding these
two lines to the top of init_chipset_siimage():
/* Mark it as a IDE device in legacy mode! */
dev->class = (PCI_CLASS_STORAGE_IDE << 8) | 0;
which just tells the IDE layer that it's not a regular PCI device and might
be using the legacy ISA interrupts - so that the code will know to probe
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 15 2003 - 22:00:28 EST