atom feed20 messages in org.freebsd.freebsd-stableRe: Continuing ahc problems - also ca...
FromSent OnAttachments
Martin KraemerJul 20, 2001 1:50 am 
Matt DillonJul 25, 2001 10:11 am 
Martin KraemerJul 27, 2001 9:51 am 
Brandon D. ValentineJul 27, 2001 10:24 am 
Justin T. GibbsJul 27, 2001 11:58 am 
Martin KraemerJul 30, 2001 1:27 am 
Martin KraemerJul 30, 2001 5:30 am 
Justin T. GibbsJul 30, 2001 7:21 am 
Martin KraemerJul 30, 2001 8:33 am.dmesg, .pciconf, .messages
Martin KraemerJul 30, 2001 8:52 am 
Matt DillonJul 30, 2001 9:46 am 
Chad R. LarsonJul 30, 2001 9:59 am 
Cy Schubert - ITSD Open Systems GroupJul 30, 2001 11:10 am 
Martin KraemerJul 30, 2001 1:28 pm 
Mike HardingJul 30, 2001 9:14 pm 
Martin KraemerJul 30, 2001 11:44 pm 
Michael Sperber [Mr. Preprocessor]Jul 31, 2001 5:00 am.dmesg
Arno J. KlaassenJul 31, 2001 9:48 am 
Justin T. GibbsJul 31, 2001 1:00 pm 
Michael Sperber [Mr. Preprocessor]Aug 2, 2001 9:57 am 
Subject:Re: Continuing ahc problems - also cause fxp failure
From:Justin T. Gibbs (gib@scsiguy.com)
Date:Jul 31, 2001 1:00:59 pm
List:org.freebsd.freebsd-stable

I see an identical problem with and without this diff applied on an ASUS motherboard with onboard SCSI. No onboard Ethernet.

Your problem is actually quite different. In your case, the timeout occurs in a data-out phase and the chips status tells us:

1) The target still has us in data phase.

2) SCSI dma is still enabled.

3) Our data fifo is full of data to send on the SCSI bus, but its not going anywhere.

So, the aic7890 believes that the target has stopped requesting more data, but we still haven't changed phase. This is the classic symptom of a flaky bus where the signals for clocking data are degraded. The target probably didn't see one or more of the controller's ACKs, so we are stuck. Double check your termination, cabling, power supply, etc, etc.

-- Justin

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