Bug 18185

Summary: Adaptec 3950U2 errors during boot/probe
Product: Base System Reporter: satz
Component: i386Assignee: Justin T. Gibbs <gibbs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description satz 2000-04-24 05:20:00 UTC
Using a Tyan Tempest II (S1462) MB, upon booting up a 3.4-stable (or 4.0-release
for that matter) kernel, I get the following error messages:

Data Parity Error detected during address or write data phase
(probe14:ahc1:0:0:0) SCB 0xe timed out while idle, SEQADDR == 0x159
Queuing BDR SCB

Both of these messages are duplicated one for ahc1 and ahc2. The S1462 MB is a combo EISA/PCI
MB. ahc0 is an adaptec 1742 controller (eisa).

Fix: 

This might be a bad 3950U2 controller card but it could be a motherboard incompatibility or a software
issue.
How-To-Repeat: Boot with card installed
Comment 1 winter 2000-04-25 02:57:06 UTC
On Sun, 23 Apr 2000 satz@iranger.com wrote:
> FreeBSD fnu.iranger.com 3.4-STABLE FreeBSD 3.4-STABLE #44: Sun Apr 23 00:22:59 MDT 2000     root@fnu.iranger.com:/usr/src/sys/compile/FNU  i386
> >Description:
> Using a Tyan Tempest II (S1462) MB, upon booting up a 3.4-stable (or 4.0-release
> for that matter) kernel, I get the following error messages:
> 
> Data Parity Error detected during address or write data phase
> (probe14:ahc1:0:0:0) SCB 0xe timed out while idle, SEQADDR == 0x159
> Queuing BDR SCB
> 
> Both of these messages are duplicated one for ahc1 and ahc2. The S1462
> MB is a combo EISA/PCI MB. ahc0 is an adaptec 1742 controller (eisa).
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That would be impressive since the driver for the 174x card is 'ahb'.

Do you mean 2742?

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| winter@jurai.net |       2 x '84 Volvo 245DL        | ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |
Comment 2 satz 2000-04-25 05:56:36 UTC
on 4/24/00 7:57 PM, Matthew N. Dodd at winter@jurai.net wrote:

> On Sun, 23 Apr 2000 satz@iranger.com wrote:
>> FreeBSD fnu.iranger.com 3.4-STABLE FreeBSD 3.4-STABLE #44: Sun Apr 23
>> 00:22:59 MDT 2000     root@fnu.iranger.com:/usr/src/sys/compile/FNU  i386
>>> Description:
>> Using a Tyan Tempest II (S1462) MB, upon booting up a 3.4-stable (or
>> 4.0-release
>> for that matter) kernel, I get the following error messages:
>> 
>> Data Parity Error detected during address or write data phase
>> (probe14:ahc1:0:0:0) SCB 0xe timed out while idle, SEQADDR == 0x159
>> Queuing BDR SCB
>> 
>> Both of these messages are duplicated one for ahc1 and ahc2. The S1462
>> MB is a combo EISA/PCI MB. ahc0 is an adaptec 1742 controller (eisa).
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> That would be impressive since the driver for the 174x card is 'ahb'.
> 
> Do you mean 2742?

opps. yes, 2742.

Thanks,
Greg
Comment 3 Kenneth D. Merry freebsd_committer freebsd_triage 2000-04-27 20:45:33 UTC
Responsible Changed
From-To: freebsd-bugs->gibbs

Over to the author. 
Comment 4 Justin T. Gibbs freebsd_committer freebsd_triage 2001-02-24 20:06:32 UTC
State Changed
From-To: open->feedback

Is this still reproduceable?
Comment 5 Justin T. Gibbs freebsd_committer freebsd_triage 2005-08-15 14:04:49 UTC
State Changed
From-To: feedback->closed

These errors are caused by some other bus master on the PCI bus 
incorrectly setting parity on its bus transactions.  If the parity 
failure occurs on an address frame, the ahc device cannot determine 
if the transaction was for it or someone else, so the driver complains. 
Recent versions of the driver have been altered to only complain a 
few times before disabling the check for these failures so that a 
system that chronically experiences pci parity errors is not flooded 
with messages.