Common misconception. I wrote 2.4-ac, not 2.4 vanilla tre. 2.4-ac is in
flux, 2.5 is too. There are some quirks, most of the 'doesnt work'
nature and not the 'corrupting data' kind.
> - I have several boxes with decent PCI chipsets (BX, HX) but old disks.
> With 2.5.39, they tend to spew a couple of ..._intr errors on boot.
> (Sorry, can't be more specific right now. I won't be near those
> boxes until Saturday.)
But they come up?
> - Same ..._intr errors on my 486 with a qd6580 VLB controller.
> It also has, in post-2.5.36 kernels, an instant-reboot problem which
> occurs whenever I pass the ide0=qd65xx kernel option required to
> activate its chipset support. (I _believe_ this is because the code
> does something, like a kmalloc, which is illegal at the early
> point IDE's __setup runs.) With 2.5.3x kernels, this box also sees
> a steady stream of spurious interrupts while doing a kernel recompile,
> something it doesn't see in older kernels.
Ok this is a new one, at least to me
> - My Intel AL440LX box (440LX chipset, 20G Quantum Fireball) worked
> brilliantly up to 2.5.36, but hangs *hard* with 2.5.39 as soon
> as I tar zxf the kernel source tarball.
> (May or may not be IDE. I'll try a minimal 2.5.39 tonight.)
Probably not ide, no important changes in there in between 2.6.36 and
present.
> All of these work perfectly with 2.4.20-pre8, indeed all previous 2.4
> standard kernels, 2.2 + Andre's ide-patch, and with the exception of
> the ..._intr errors, 2.5.36.
If you (or anyone else for that matter) come across ide oddities in 2.5,
please try 2.4.20-pre-ac kernels and see if you can reproduce.
-- Jens Axboe- 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/