Subject: Re: NetBSD 3.0 on E420R - esiop cmd time out locks system
To: doomwarrior <doomwarriorx@gmail.com>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: port-sparc64
Date: 01/03/2006 21:50:09
On Tue, Jan 03, 2006 at 08:13:20PM +0100, doomwarrior wrote:
> hello
> 
> i got a new machine (Enterprise 420R) and try to install NetBSD on it. 
> But the Systems locks while booting the installation kernel
> 
> Trace:
> 
> ok boot cdrom
> [...]
> esiop0 at pci0 dev 3 function 0: Symbios Logic 53c875 (ultra-wide scsi)
> esiop0: using on-board RAM
> esiop0: interrupting at ivec 20
> scsibus0 at esiop0: 16 targets, 8 luns per target
> esiop1 at pci0 dev 3 function 1: Symbios Logic 53c875 (ultra-wide scsi)
> esiop1: using on-board RAM
> esiop1: interrupting at ivec 26
> scsibus1 at esiop1: 16 targets, 8 luns per target
> psycho1 at mainbus0 addr 0xfffc6000
> SUNW,psycho: impl 0, version 4: ign 7c0 bus range 128 to 128; PCI bus 128
> pci1 at psycho1
> pci1: i/o space, memory space enabled
> timer0 at mainbus0 addr 0xfff9fc00 irq vectors 7ec and 7ed
> pcons at mainbus0 not configured
> wskbd0 at kbd0 mux 1
> kbd0: reset failed
> Kernelized RAIDframe activated
> md0: internal 5120 KB image area
> scsibus0: waiting 2 seconds for devices to settle...
> scsibus1: waiting 2 seconds for devices to settle...
> probe(esiop0:0:0:0): command timeout, CDB: 0x12 00 00 00 24 00

This is an interrupt routing issue. The esiop driver isn't getting any
interrupts.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--