Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Nov 1998 14:49:15 +0100
From:      Ron Klinkien <root@zappa.demon.nl>
To:        freebsd-questions@FreeBSD.ORG
Subject:   Adaptec SCSI messages
Message-ID:  <19981114144915.A244@zappa.demon.nl>

next in thread | raw e-mail | index | archive | help

I have my FreeBSD system running for a few weeks now,
but during bootup there is a long timeout and a message
displayed from the adaptec scsi adapter when
there is a probe on my scsi disc.

Any scsi wizards know what this mean, and what to do?

Snippits from dmesg:
---
ahc0: <Adaptec aic7890/91 Ultra2 SCSI adapter> rev 0x00 int a irq 10 on pci0.6.0
ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs  
---
Waiting 4 seconds for SCSI devices to settle
(probe6:ahc0:0:6:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xf4
SEQADDR == 0x15b
SSTAT1 == 0x2
(probe6:ahc0:0:6:0): Queuing a BDR SCB
(probe6:ahc0:0:6:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xf4
SEQADDR == 0x15b
SSTAT1 == 0x2
(probe6:ahc0:0:6:0): no longer in timeout, status = 34b
ahc0: Issued Channel A Bus Reset. 8 SCBs aborted
changing root device to da0s1a
da0 at ahc0 bus 0 target 6 lun 0
da0: <QUANTUM VIKING II 4.5WLS 3506> Fixed Direct Access SCSI2 device
da0: 40.0MB/s transfers (20.0MHz, offset 31, 16bit), Tagged Queueing Enabled
da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) 
---
cd0 at ahc0 bus 0 target 1 lun 0
cd0: <PLEXTOR CD-ROM PX-32TS 1.03> Removable CD-ROM SCSI2 device
cd0: 20.0MB/s transfers (20.0MHz, offset 15)
cd0: Attempt to query device size failed: NOT READY, Medium not present
(da0:ahc0:0:6:0): tagged openings now 63
---
zappa# uname -a
FreeBSD zappa.demon.nl 3.0-CURRENT FreeBSD 3.0-CURRENT #6: Thu Nov 12 21:04:50
 CET 1998     root@zappa.demon.nl:/usr/src/sys/compile/UMRK5  i386
---
The cdrom device msg comes after 10 seconds during the rest of the bootup.

What does the tagged openings msg mean? I get them only if the
scsi devices are getting more work to do.

It doens't seem to matter how long the scsi timeout is set in the kernel.
The Quantum disk is an UltraWide2 type, and so is the onboard scsi controller 
(Asus P2BS mainboard.)

Can I alter scsi driver or kernel parameters to get rid of this timeout delay?
Maybe it has something to do with the hd firmware like with some other Quantum disks.
 
All works ok, but the bootup takes a long time. 

Regards,
Ron.

--
Running Solaris/SPARC at work, enjoying FreeBSD/PII at home.

Ron Klinkien			System Engineer
ron@zappa.demon.nl		http://www.zappa.demon.nl

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981114144915.A244>