From nobody@FreeBSD.org  Tue Sep  7 17:11:55 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 30F3216A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Tue,  7 Sep 2004 17:11:55 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2ACE443D2F
	for <freebsd-gnats-submit@FreeBSD.org>; Tue,  7 Sep 2004 17:11:55 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i87HBsnu053356
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 7 Sep 2004 17:11:54 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i87HBslE053355;
	Tue, 7 Sep 2004 17:11:54 GMT
	(envelope-from nobody)
Message-Id: <200409071711.i87HBslE053355@www.freebsd.org>
Date: Tue, 7 Sep 2004 17:11:54 GMT
From: Burgarello Valerio <valerio@dogweb.be>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Asus P4P800-E Promise 20378 RAID 1 problem
X-Send-Pr-Version: www-2.3

>Number:         71470
>Category:       i386
>Synopsis:       [hang] Asus P4P800-E Promise 20378 RAID 1 problem [5.3-BETA3]
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-i386
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep 07 17:20:19 GMT 2004
>Closed-Date:    Sun Jan 29 05:19:54 GMT 2006
>Last-Modified:  Sun Jan 29 05:19:54 GMT 2006
>Originator:     Burgarello Valerio
>Release:        5.3-BETA3
>Organization:
>Environment:
it happens on boot, can't log to the pc
>Description:
When i boot the FreeBSD 5.3-BETA3 CD, it freeze on error message and i can't go further :

ata1-slave : FAILURE - ATA_IDENTIFY status=3f<DMA_READY,DSC,DRQ,CORRECTABLE,INDEX,ERROR> error=7f<UNCORRECTABLE,MEDIA_CHANGED,MID_NOT_FOUND,MEDIA_CHANGE_REQUEST,ABORTED,NO_MEDIA,ILLEGAL_LENGTH>  LBA=0

It's a brand new pc, with 2 identical HarDrives Maxtor 80Gb IDE
MotherBoard : Asus P4P800-E with disk controller Promise 20378
The RAID1's array is correct on the FastTrackBios, status : FUNCTIONAL
First Disk on the cable : Master
Second disk on the cable : Slave
the cable is connected to the raid controller (promise 20378)

>How-To-Repeat:
      
>Fix:
      
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: remko 
State-Changed-When: Fri Nov 4 11:38:30 GMT 2005 
State-Changed-Why:  
Requested whether this still applies to more recent versions 
and what kind of IDE cable had been used. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=71470 

Adding to audit trail from misfiled PR kern/89440:

Date: Tue, 22 Nov 2005 18:40:52 -0500
From: Gordon Jenkins <ez771@ncf.ca>

 The problem is operating system independent.  I have an ASUS A8V Deluxe 
 board with Athlon 3500+, 2 x Hitachi 250G x 16Meg buf. SATA drives + 
 250 G Maxtor IDE x16 meg. buf. on IDE Pri. Master. They work fine on 
 the VIA RAID controller VT8237, only when Promise 20378 is disabled.  
 When I hook my SATA drives to the PROMISE 20378 controller, computer 
 boots ok (Windows XP Pro).  When I enable the Promise 20378 controller, 
 I get boot problems because it fails MEM TEST.  Enabling Promise 20378 
 on ASUS Board causes memory problems and therefore boot problems.  
 Doesn't matter what memory timing you use.  I am on full auto mem clock 
 timings.  (OCZ Dual Channel, Premiere, 4 x 512M).  ASUS BIOS Flashed to 
 1014, tried 1015 BIOS Beta, more support for ECC Ram but still same 
 boot problems, went back to 1014 BIOS.  So, work around was to disable 
 Promise 20378 in BIOS and switch drives to VIA VT8237 controller in 
 RAID 1 mode, works ok.   Use HT clock of 800 MHZ for  8x AGP instead of 
 1000 MHZ for Sapphire Radeon ATI 9800SE, otherwise you get video 
 lockups. Its kind of sad these ASUS boards don't work 
 as "PROMISE"'d ;)  
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Sun Jan 29 05:18:28 UTC 2006 
State-Changed-Why:  
Feedback timeout.  A reply in the audit trail indicated that this is a 
known issue with this motherboard (all OSes). 

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