Re: 5.1 panics on a Challenge S

On Wed, 16 Feb 2011 08:03:05 -0500 (EST)
Jared McNeill <[email protected]> wrote:

> On Tue, 15 Feb 2011, George Harvey wrote:
> > The panel code seems to be getting a -1 irq level from the pi1ppc table
> > entry but I can't work out how that is happening.
> 
> Try changing pi1ppc_match to:

Ahh, that's better, it fixed the panic but I got an extra panel
attach that shouldn't have been there. Adding a similar strcmp() into
the panel_match() function fixed that and the boot messages now look
normal. I've included part of the dmesg below (still with some extra
debug printfs).

Thanks,
George

=== partial dmesg from patched kernel ===
hpc_attach: wdsc: irq=1
wdsc0 at hpc0 offset 0x44000int_intr_establish: level=1
: WD33C93B (20.0 MHz clock, BURST DMA, SCSI ID 0)
wdsc0: microcode revision 0x0d, Fast SCSI
scsibus0 at wdsc0: 8 targets, 8 luns per target
hpc_attach: dsclock: irq=-1
dsclock0 at hpc0 offset 0x60000
hpc_attach: haltwo: irq=12
haltwo at hpc0 offset 0x58000 not configured
hpc_attach: pi1ppc: irq=-1
pi1ppc0 at hpc0 offset 0x59800
pi1ppc0: capabilities=8<PS2>
ppbus0 at pi1ppc0
ppbus0: No IEEE1284 device found.
lpt0 at ppbus0: port mode = 1<COMPATIBLE>
hpc_attach: panel: irq=9
panel0 at hpc0 offset 0x59850
int_intr_establish: level=9
=== end ===