last_ipl[2] etc etc

[Alan B. <al...@ms...>]

hi,

<quote>

     FROM: Roman Zippel
     DATE: 11/04/2001 17:48:50
     SUBJECT:  Interrupt code update
      
     Hi,

     > Log message:
     >   use general interrupt management code

     This was a major surgery, I hoped everything still works as before,
     please test it carefully.
     Biggest visible difference is a new /proc/interrupts format, which is
     now the same as for other ppc machines. Otherwise there is now finally
     that annoying "Trying to enable auto-vector" print gone. I left another
     print in (last_ipl[x] already set to...), it should only occur rarely
     and shouldn't be a problem. I'll remove it later again.

     bye, Roman

</unquote>

interesting....this is the sort of error my Amiga is throwing up
before doing nothing else... (see below)


ide0: Gayle IDE interface (A1200 style)
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xe0)
hda: FUJITSU MPE3084AE, ATA DISK drive
hdb: probing with STATUS(0x00) instead of ALTSTATUS(0xe0)
hdb: probing with STATUS(0x00) instead of ALTSTATUS(0xe0)
last_ipl[2] already set to 2f, now 2d!
818: 2 -2 2 -2 2 -2 2 -2 2 -2 2 -2 2 3 -3 2
last_ipl[2] already set to 2f, now 2d!
3329: 2 -2 2 -2 2 -2 2 -2 2 -2 2 -2 2 3 -3 2
amikeyb: unknown keyboard communication code 0xff
<<<<<<<<<<<<<<<<<<<<

would the RTC have anoything to do with this interupt freeze/problem?

thanks

Alan