> IRQ7 is asserted when the PIC sees an interrupt but nobody appears to be> generating it when it looks.> -

I had the same symptoms on an uniprocessor IBM PC300GL (pretty standardpc, 32MB ram, 333MHz celeron [pre-coppermine], 82371AB PIIX E-IDE/ACPIchips,Intel Motherboard, 66MHz bus), S3 Trio3D (IBM integrated - **does thatmean anything to you? XFree86-SVGA doesn't work on it, but XFree86-S3version 4.0.1-RH 7.0- seems to work fine with the s3virge driver) AGP graphics board(2MBvram) plus an Avance ALS4000 card are all I've got. I was worriedbecauseI don't have any 8259A's on my motherboard and this led me to kgcc. The problem occured _only_ when I, unknowingly, used RH 7.0's gcc 2.96(not one of the updated 2.96's). With that build (a 2.4.8 kernel), Ilearnt my lesson when linux got utterly stuck twice in a single day.Since then, builds with standard gcc's recommended by Linus (egcs/kgcc&& gcc 2.95.3) have seen the end of this problem. The message came upduring normal use, not in a special situation such as bootup, etc. Hope this has been of some help.

PS: Is gcc-2.96.99 currently in RawHide as good (or better ;) asgcc-2.95.3 for kernel builds? Jakub Jelinek seems to be doing a good jobon it...

- ioj

----------------------------------------------------------------------- "And King Parakramabahu sent men with a bushel of Rice each to everycorner of the land, and the people returned saying that a bushel of Ricecouldbe sold for two cents. Then the King knew that not enough food or hispeople was being produced. He built tanks of water and cultivated moreland. Again deployed men. Now they returned saying that no one wouldtake the grain evenfor free. The King was satisfied."-To unsubscribe from this list: send the line "unsubscribe linux-kernel" inthe body of a message to majordomo@vger.kernel.orgMore majordomo info at http://vger.kernel.org/majordomo-info.htmlPlease read the FAQ at http://www.tux.org/lkml/