> 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 standard
pc, 32MB ram, 333MHz celeron [pre-coppermine], 82371AB PIIX E-IDE/ACPI
chips,
Intel Motherboard, 66MHz bus), S3 Trio3D (IBM integrated - **does that
mean anything to you? XFree86-SVGA doesn't work on it, but XFree86-S3
version 4.0.1
-RH 7.0- seems to work fine with the s3virge driver) AGP graphics board
(2MB
vram) plus an Avance ALS4000 card are all I've got. I was worried
because
I 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), I
learnt 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 up
during 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 ;) as
gcc-2.95.3 for kernel builds? Jakub Jelinek seems to be doing a good job
on it...
- ioj
-----------------------------------------------------------------------
"And King Parakramabahu sent men with a bushel of Rice each to every
corner of the land, and the people returned saying that a bushel of Rice
could
be sold for two cents. Then the King knew that not enough food or his
people was being produced. He built tanks of water and cultivated more
land. Again deployed men. Now they returned saying that no one would
take the grain even
for free. The King was satisfied."
-
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/