Subject: Re: Problem with Adaptec AIC-6360 on SoundBlaster board and NetBSD-1.5
To: None <bouyer@antioche.lip6.fr>
From: Gerald C. Simmons <simmons@darykon.cet.com>
List: port-i386
Date: 07/30/2001 14:06:33
On Mon, 30 Jul 2001 Manuel Bouyer wrote:
> On Mon, Jul 30, 2001 at 09:33:29AM -0700, Gerald C. Simmons wrote:
> > On Fri, 27 Jul 2001 Manuel Bouyer wrote:
> > >
> > > On Sun, Jul 22, 2001 at 02:33:34PM -0700, Gerald C. Simmons wrote:
> > > > O.K.  Here it is (from booting boot1.fs then boot2.fs of NetBSD-1.5.1):
> > > > 
> > > > (null)(c0821d40,c05a9d14,c02ac68e,1,c05a9d24) at 0xc024e108
> > > > (null)(1) at 0xc02ac6d7
> > > > (null)(c0821d40,c058f0a0,c05a9d2c,c0101030,c081ee00) at 0xc02ac68e
> > > > (null)(c081ee00) at 0xc02ab769
> > > > (null)(0,0,10,10,c058f0a0) at 0xc0101030
> > > > (null)(c081ee44,c0365524,0,306370,0) at          0
> > > > 
> > > > Hope you know what it means!!
> > > 
> > > Just had some time to look at it, sorry.
> > > Well, it's not really interesting, unfortunably. What we have here is the stack
> > > since the keyboard interrupt. Before that we have 0 which isn't a valid
> > > function address :(
> > > 
> > > However, one thing you can do it boot this floppy set with '-d', and at 
> > > db promt:
> > > write c0365a48 ff
> > > c
> > > 
> > > Now the aic driver should tell what's he's doing.
> > > 
> > 
> > I also compiled a custom kernel with makeoptions DEBUG="-g", and got a very complete trace.
> > Just ask if you want it. 
> > 
> > Here are the boot messages:
> > 
> > NetBSD 1.5.1 (INSTALL)
> > cpu0: Intel Pentium (P54C) (586-class), 199.44 MHz
> > total mem  = 127 MB
> > avail mem = 115 MB
> > using 1659 buffers containing 6795264 bytes of memory
> > BIOS32 rev. 0 found at 0xfb330
> > mainbus0 (root)
> > pci0 at mainbus0 bus 0: configuration mode 1
> > pci0: i/o enabled, memory enabled
> > pchb0 at pci0 dev 0 function 0
> > pchb0: Intel 82439HX System Controller (TXC) (rev. 0x02)
> > pcib0 at pci0 dev 7 function 0
> > pcib0: Intel 82371SB PCI-to-ISA Bridge (PIIX3) (rev. 0x01)
> > pciide0 at pci0 dev 7 function 1: Intel 82371SB IDE Interface (PIIX3) (rev. 0x00)
> > pciide0: bus-master DMA support present
> > pciide0: primary channel wired to compatibility mode
> > wd0 at pciide0 channel 0 drive 0: <WDC WD43AA>
> > wd0: drive supports 16-sector pio transfers, lba addressing
> > wd0: 4112MB, 8355 cyl, 16 head, 63 sec, 512 bytes/sect x 8421840 sectors
> > wd0: 32-bits data port
> > wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4
> > pciide0: primary channel interrupting at irq 14
> > wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> > pciide0: disabling secondary channel (no drives)
> > ep1 at pci0 dev 18 function 0: 3Com 3c590 Ethernet
> > ep1: interrupting at irq 10
> > ep1: address 00:a0:24:4a:d5:0a, 32KB byte-wide FIFO, 1:1 Rx:Tx split
> > ep1: 10baseT, 10baseT-FDX, 10base5, 10base2 (default 10baseT)
> > vga1 at pci0 dev 19 function 0: ATI Technologies product 0x5245 (rev. 0x00)
> > wsdisplay0 at vga1: console (80x25, vt100 emulation)
> > isa0 at pcib0
> > aic: probing for aic-chip
> > AIC found ID: (C)1991ADAPTECAIC6360		chip revision 1
> > aic0 at isa0 port 0x340-0x35f irq 11
> > aic: probing for aic-chip
> > AIC found ID: (C)1991ADAPTECAIC6360		chip revision 1
> > aicattach scsibus0 at aic0: 8 targets, 8 luns per target
> > com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
> > com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
> > isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
> > npx0 at isa0 port 0xf0-0xff: using exception 16
> > pc0 at isa 0 port 0x60-0x6f irq 1 : color
> > pc0: console
> > fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
> > fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
> > fd1 at fdc0 drive 1: 1.2MB, 80 cyl, 2 head, 15 sec
> > isapnp0: no ISA Plug 'n Play devices found
> > biomask fbe5 netmask ffe5 ttymask ffe7
> > scsibus0: waiting 2 seconds for devices to settle ...
> > aic_scsi_cmd[0x0,6]->0 selecting 0:0
> 
> Hum, it looks like the driver didn't get any interrupt.
> To confirm this, can you move
> 	AIC_TRACE(("aicintr  "));
> at the very beggining of aicintr (just before the
> (sc->sc_dev.dv_flags & DVF_ACTIVE) test) ?
> 

O.K. Made requested change to aic6360.c. Recompiled - Rebooted w/ aic_debug set to 0xFF.
Nothing different happened.

What next???

Gerry