This looks like a hardware problem to me. My XP1000 has the very same Cypress controller amd it always worked ok (as good as an ISA IDE controller will get). You might try using a different cable ora different cdr drive to see if the problem goes away. I doubt it's a software problem; what kernel version are you using?

This looks like a hardware problem to me. My XP1000 has the very same Cypress controller amd it always worked ok (as good as an ISA IDE controller will get). You might try using a different cable ora different cdr drive to see if the problem goes away. I doubt it's a software problem; what kernel version are you using?

Hm. Whatever the real cause is, I'd first try to eliminate hardware as the culprit. IDE CDR drives should be easy to come by (especially when just doing a quick test).

got wayy too many of those lying around

I don't think it's going to help, though, because #1: I'm not using the cd when it happens, #2, the livecd boots perfectly with the same drivers, and #3, the errors seem to indicate controller problems rather than drive problems.

I'll give it a try, and I'll also give a try to rebuilding using the livecd's config._________________iVBORw0KGgoAAAANSUhEUgAAA

avatar: new version of logo - see topic 838248. Potentially still a WiP.

I don't think it's going to help, though, because #1: I'm not using the cd when it happens, #2, the livecd boots perfectly with the same drivers, and #3, the errors seem to indicate controller problems rather than drive problems.

I'll give it a try, and I'll also give a try to rebuilding using the livecd's config.

Before you do that, make sure your SRM is up-to-date. You have to face the possibility that the baseboard has sustained some sort of hardware damage.

Also, not using the drive does not mean the OS and the controller and drive don't talk to each other.

I couldn't remember the version off-hand initially, but yep, that's the version I'm running.

I've already deduced that it both has to be a hardware problem (by the fact that it (mostly) works with the cable unplugged), and that it can't be a hardware problem (by the fact that the livecd boots perfectly..)

I'm doing a little more digging around in there... then I don't know what to do _________________iVBORw0KGgoAAAANSUhEUgAAA

avatar: new version of logo - see topic 838248. Potentially still a WiP.

I just re-compiled the kernel using the livecd's .config (from /proc/config.gz)... used oldconfig and defaults for the things it asked, and my kernel boots fine, even with the IDE cable attached (and even lets me use the keyboard).

So....... WTF?

Would someone mind looking at my .config, because I am genuinely confused._________________iVBORw0KGgoAAAANSUhEUgAAA

avatar: new version of logo - see topic 838248. Potentially still a WiP.

Ever find a resolution to this issue? I too have a Miata (500au) and have been unable to boot a new 2.6.30-gentoo-r6 kernel due to these 'lost interrupt' errors. However, I have a 2.6.27-gentoo-r8 kernel that runs perfectly. Even using the same config, the .30 kernel won't boot.

Dumping the IDE drive isn't an option, as I need an IDE drive to boot off of as SRM doesn't recognize my PCI-X LSI Fusion-MPT SCSI controller

Ever find a resolution to this issue? I too have a Miata (500au) and have been unable to boot a new 2.6.30-gentoo-r6 kernel due to these 'lost interrupt' errors. However, I have a 2.6.27-gentoo-r8 kernel that runs perfectly. Even using the same config, the .30 kernel won't boot.

Dumping the IDE drive isn't an option, as I need an IDE drive to boot off of as SRM doesn't recognize my PCI-X LSI Fusion-MPT SCSI controller

Any particular reason for the change from specifying the correct machine type?

I tried out a 2.6.29-gentoo-r6 kernel and it boots fine. It also seems to have resolved my "unable to handle kernel paging request at virtual address" errors as well. Since this kernel has ext4 support, is there any advantage to moving to 2.6.30?