Re: 5.1_RC2 panics on Challenge S

[George Harvey <fr30%dial.pipex.com@localhost>]

On Thu, 10 Jun 2010 17:45:58 -0400
Michael <macallan%netbsd.org@localhost> wrote:

> > ppbus0 at pi1ppc0
> > ppbus0: No IEEE1284 device found.
> > panel0 at hpc0 offset 0x59800
> > panic: invalid interrupt level
> 
> This is weird.
> There is nothing in the panel driver which differentiates between Indy  
> and Challenge S, the interrupt level is the same, I see no reason why  
> it would panic on a Challenge but not an Indy.
> On the other hand - does the Challenge have more than one hpc? If so  
> the panel driver may try to attach to the wrong one. In the example  
> above it's the onboard hpc though.
> Could you build a kernel without the panel driver and post the  
> resulting dmesg?

The Challenge S does have a second hpc. 5.1_RC2 works with the panel
driver removed, dmesg below.

George

NetBSD 5.1_RC2 (INDY3) #1: Fri Jun 11 09:53:58 BST 2010
        
georgeh%indy4.ceiridos.co.uk@localhost:/usr/src/sys/arch/sgimips/compile/INDY3
total memory = 98304 KB
(768 KB reserved for ARCS)
avail memory = 91936 KB
timecounter: Timecounters tick every 10.000 msec
mainbus0 (root): SGI-IP22 [SGI, 690ac9fb], 1 processor
cpu0 at mainbus0: MIPS R5000 CPU (0x2310) Rev. 1.0 with built-in FPU
Rev. 1.0 cpu0: 32KB/32B 2-way set-associative L1 Instruction cache, 48
TLB entries cpu0: 32KB/32B 2-way set-associative write-back L1 Data
cache cpu0: 512KB/32B direct-mapped write-through L2 Data cache
ioc0 at mainbus0 addr 0x1fbd9800: rev 0, machine Indy (Guinness), board
rev 0 int0 at mainbus0 addr 0x1fbd9880
int0: bus 90MHz, CPU 180MHz
imc0 at mainbus0 addr 0x1fa00000: revision 3
gio0 at imc0
giopci0 at gio0 slot 1 addr 0x1f400000: Phobos G130 10/100 Ethernet
pci0 at giopci0 bus 0
pci0: memory space enabled
tlp0 at pci0 dev 0 function 0: DECchip 21143 Ethernet, pass 4.1
tlp0: interrupting at slot EXP0
tlp0: Ethernet address 00:60:f5:08:23:07
lxtphy0 at tlp0 phy 1: LXT970 10/100 media interface, rev. 3
lxtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
hpc0 at gio0 addr 0x1fb80000: SGI HPC3 (onboard)
zsc0 at hpc0 offset 0x59830
zstty0 at zsc0 channel 1 (console i/o)
zstty1 at zsc0 channel 0
pckbc0 at hpc0 offset 0x59840
sq0 at hpc0 offset 0x54000: SGI Seeq 80c03
sq0: Ethernet address 08:00:69:0a:c9:fb
wdsc0 at hpc0 offset 0x44000: 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
dsclock0 at hpc0 offset 0x60000
pi1ppc0 at hpc0 offset 0x58000
pi1ppc0: capabilities=8<PS2>
ppbus0 at pi1ppc0
ppbus0: No IEEE1284 device found.
pi1ppc at hpc0 offset 0x59800 not configured
panel at hpc0 offset 0x59850 not configured
hpc1 at gio0 addr 0x1fb00000: SGI HPC3 (IOPLUS mezzanine)
hpc1: using EXP1's DMA channel
sq1 at hpc1 offset 0x54000: SGI Seeq 80c03
sq1: Ethernet address 08:00:69:02:96:48
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
timecounter: Timecounter "mips3_cp0_counter" frequency 90000000 Hz
quality 100 scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 1 lun 0: <IBM, DCAS-34330, S60B> disk fixed
sd0: 4134 MB, 8205 cyl, 6 head, 171 sec, 512 bytes/sect x 8467200
sectors sd0: sync (100.00ns offset 12), 8-bit (10.000MB/s) transfers,
tagged queueing sd1 at scsibus0 target 2 lun 0: <SGI, IBM DORS-32160,
W80D> disk fixed sd1: 2049 MB, 6703 cyl, 5 head, 125 sec, 512 bytes/sect x 
4197405 sectors
sd1: sync (100.00ns offset 12), 8-bit (10.000MB/s) transfers, tagged
queueing boot device: sd0
root on sd0a dumps on sd0b
root file system type: ffs