In message <[EMAIL PROTECTED]>, "Andrew Reilly" 
writes:
> On Wed, Mar 14, 2001 at 01:31:16AM -0800, Jordan Hubbard wrote:
> > I'm just testing the 4.3-BETA2 on my standard scratchbox (a dual PIII/500
> > with two 9.1GB Quantum drives) and with the latest BETA build, I'm
> > seeing an unusual problem during extraction of the distribution bits:
> > 
> > First, I start getting the following message looping on the
> > console:
> > 
> > (da0:ahc0:0:0:0): Invalidating pack
> > <repeat about 5 times>
> > 
> > (cd0:ahc0:0:4:0): SCB 0x12 - timed out in Data-out phase, SEQADDR == 0x8
> > STACK == 0x3, 0x181, 0x16b, 0x0
> > SXFRCTL0 == 0x80
> > ahc0: Dumping Card State at SEQADDR 0x8
> > SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x0
> > SCB count = 90
> > Kernel NEXTQSCB = 20
> > Card NEXTQSCB = 20
> > QINFIFO entries:
> > Waiting Queue entries:
> > Disconnected Queue entries:
> > <what follows is a list of queue entry information too long to type>
> > 
> > Suffice it to say that the installation croaks at this point.  Now
> > here's the interesting bit: This only happens reliably if I enable
> > soft updates on the root partition.  Any real correlation?  I have no
> > idea.  Anyway, JFYI.  If I can start reproducing it in other ways,
> > I'll let you know whether I've started to consider it a release
> > show-stopper bug or not.
> 
> Here's a possible "me too".  I haven't reported this before
> because (a) da2 is my backup Fujitsu MO drive, and it does do
> odd things occasionally, and (b) the backup disk is currently
> full and I haven't thrown the requisite round-tuit at it.
> 
> If this actually represents a problem, and I can help with
> debugging it, please just say what you need...
> 
> Following are a chunk of kernel messages from /var/log/messages
> and the contents of /var/run/dmesg.boot.  The system is:
> 
> FreeBSD gurney.reilly.home 4.3-BETA FreeBSD 4.3-BETA #7: Sun Mar 11 13:38:49 
> EST 2001     [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GURNEY  i386
> Mar 14 03:11:24 gurney /kernel: (da2:ahc0:0:6:0): SCB 0x3 - timed out while
> idle, SEQADDR == 0x7

About a month ago I had this problem too.  At first it was infrequent 
becoming much worse later.  A scan by the the Adaptec disk scan utility 
showed me that the disk had gone bad.


Regards,                         Phone:  (250)387-8437
Cy Schubert                        Fax:  (250)387-5766
Team Leader, Sun/Alpha Team   Internet:  [EMAIL PROTECTED]
Open Systems Group, ITSD, ISTA
Province of BC



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to