From dgilbert@daveg.ca  Fri Jun 30 15:46:22 2006
Return-Path: <dgilbert@daveg.ca>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 46B3216A415
	for <freebsd-gnats-submit@freebsd.org>; Fri, 30 Jun 2006 15:46:22 +0000 (UTC)
	(envelope-from dgilbert@daveg.ca)
Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 025F043D48
	for <freebsd-gnats-submit@freebsd.org>; Fri, 30 Jun 2006 15:46:21 +0000 (GMT)
	(envelope-from dgilbert@daveg.ca)
Received: by ox.eicat.ca (Postfix, from userid 66)
	id A1EE91D59B; Fri, 30 Jun 2006 11:46:20 -0400 (EDT)
Received: by canoe.dclg.ca (Postfix, from userid 101)
	id D37E34AC2B; Fri, 30 Jun 2006 11:46:21 -0400 (EDT)
Message-Id: <20060630154621.D37E34AC2B@canoe.dclg.ca>
Date: Fri, 30 Jun 2006 11:46:21 -0400 (EDT)
From: David Gilbert <dgilbert@daveg.ca>
Reply-To: David Gilbert <dgilbert@daveg.ca>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: SiI 3112 controller hangs with read/write load
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         99649
>Category:       kern
>Synopsis:       [ata] SiI 3112 controller hangs with read/write load
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 30 15:50:16 GMT 2006
>Closed-Date:    Mon Jul 03 21:02:13 GMT 2006
>Last-Modified:  Mon Jul 03 21:02:13 GMT 2006
>Originator:     David Gilbert
>Release:        FreeBSD 6.1-STABLE i386
>Organization:
DaveG.ca
>Environment:
FreeBSD virtual.accountingreality.com 6.1-RELEASE-p2 FreeBSD 6.1-RELEASE-p2 #2: Wed Jul 26 22:50:39 EDT 2006     root@virtual.accountingreality.ca:/usr/obj/usr/src/sys/VR  amd64

>Description:
The system has an onboard nVidia nForce MCP51 SATA300 controller ...
which (in some other PR) has a known issue where you can only attach
one drive to it.

Since I had a SiI 3112 SATA150 controller PCI card lying around, 
I attached one drive to the motherboard and one drive to the SiI.

The problem occurs under heavy write load with some reading.  fsck
alone will not trigger the problem.  A Geom mirror sync works fine,
too.  The fact that the geom sync worked fine (which writes at
65 to 75 megabytes per second) gave the the idea that write-only
was good.

Anyways... some moderate amount of tars running causes the system to
hang with WRITE_DMA48 timeouts.

The system will run fine with geom_mirror on prefer ... such that the
SiI connected drive receives only write requests.
>How-To-Repeat:
I copy a bunch of data from one place to another place on the drive.

It's possible that this is queue related because the L(q) parameter
on gstat tends to be more than 100 when it hangs.
>Fix:

	None known.


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: brooks 
State-Changed-When: Mon Jul 3 21:00:58 UTC 2006 
State-Changed-Why:  
This controler is well known to be broken. Don't use it, it won't work. 
See the archives of -stable, -current, -hardware, etc for details and 
lots of other reports. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=99649 
>Unformatted:
