Eric,
I have a printk immediately after the lines of the patch
#if 1
console_drivers = &minimal_serial_console;
#endif
printk("setup_arch\n");
The serial output I get from the kernel is:
setup_arch
Unknown interrupt
Unknown interrupt
....
I have looked at the PIC setup - no change - the IDT is the same...
I am not sure where to look next
Hamish
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Eric W Biederman
> Sent: 18 July 2002 05:41
> To: [EMAIL PROTECTED]
> Cc: Ronald G Minnich; LinuxBIOS
> Subject: Re: mkelfImage
>
>
> "Hamish Guthrie \(Mail Lists\)" <[EMAIL PROTECTED]> writes:
>
> > Ron, thanks for that patch - it is now almost as clear as mud!
> >
> > I now get a continuous stream of 'Unknown interrupt'
>
> Generally this is a sign that the code is getting an exception,
> as interrupts are actually disabled until this point. If it is an
> exception the code get's stuck there because the exception handler
> does not remove the reason for the exception, and then when it returns
> to the same location the exception occurs again.
>
> > What is strange to me is that this stuff works with 2.4.5 - I wonder if
> > something has changed in the way the IDT is set up, or maybe
> the way the PCI
> > is set up?
> >
> > I will dig more.
>
> Sounds good. If you can give the kernel messages before you get
> the unknown interrupt stream that would be interesting.
>
>
> Eric
