Bug 48986

Summary: 5.0-R/4.7R system hangs on HighPoint RAID w/ ata driver
Product: Base System Reporter: Robert Eckardt <Robert.Eckardt>
Component: kernAssignee: Søren Schmidt <sos>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 5.0-RELEASE   
Hardware: Any   
OS: Any   

Description Robert Eckardt 2003-03-06 22:10:07 UTC
FreeBSD's ATA-driver recogizes the RAID-controller and can start installation.
Controlling the RAID with atacontrol (in the emergency shell) works.
On unpacking the distributions the system hangs (not always at the same point).
### This is also valid for 4.7-RELEASE. ###

Fix: 

HighPoint (www.highpoint-tech.com) provides kernel modules for
FreeBSD 4.{1,3,4,5,6.2,7}-RELEASE for controller BIOS v2.34, which
works fine (even with BIOS v2.32). RAID is attached as SCSI device da:
pci1: <PCI bus> on pcib1
hpt37x20: <HPT372 UDMA/ATA133 RAID Controller> port 0xa000-0xa0ff,0x9c00-0x9c03,0x9800-0x9807,0x9400-0x9403,0x9000-0x9007 irq 11 at device 0.0 on pci1
 [...]
Device Driver for HPT37x2 ATA RAID Controller Version 1.31
 [...]
Waiting 5 seconds for SCSI devices to settle
da0 at hpt37x20 bus 0 target 0 lun 0
da0: <HPT Inc. HPT37x2   RAID 1 1.05> Fixed Direct Access SCSI-2 device 
da0: 73308MB (150136560 512 byte sectors: 255H 63S/T 9345C)

Though, for 5.0-RELEASE no workaround known.
How-To-Repeat: Install 4.7-RELEASE or 5.0-RELEASE on platform with EP-4GEA+ mainboard and
a RAID attached to the HighPoint controller and produce heavy disk I/O.
Comment 1 dwmalone freebsd_committer freebsd_triage 2003-03-13 21:42:39 UTC
Responsible Changed
From-To: freebsd-bugs->sos

Highpoint ATA Raid PR for Soren.
Comment 2 Søren Schmidt freebsd_committer freebsd_triage 2003-04-28 19:35:44 UTC
State Changed
From-To: open->feedback

Does this still happen on a very resent -current ?
Comment 3 marko 2003-05-11 16:33:27 UTC
Commentate agp off to kernel and works fine.
Comment 4 Søren Schmidt freebsd_committer freebsd_triage 2003-09-08 20:03:04 UTC
State Changed
From-To: feedback->closed

If i read this correctly disabling agp solved the problem.
Comment 5 Robert Eckardt 2003-09-09 21:40:19 UTC
On Mon, 8 Sep 2003 12:04:01 -0700 (PDT), Søren Schmidt wrote
> Synopsis: 5.0-R/4.7R system hangs on HighPoint RAID w/ ata driver
>
> State-Changed-From-To: feedback->closed
> State-Changed-By: sos
> State-Changed-When: Mon Sep 8 12:03:04 PDT 2003
> State-Changed-Why:
> If i read this correctly disabling agp solved the problem.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=48986

Hi Søren,

NO, it didn't solve the problem at all!

Currently, I'm running FreeBSD-5.0-R with HighPoint's driver HPT372-1.32.
Since HighPoint is always some time behind the recent RELEASE (esp. for
FreeBSD), the latest release that runs on my hardware, and by carefully
avoiding the RAID-functionality in FreeBSD, is 5.0-R.
Despite the fact that 5.0 was not intended for "long-time" production
systems, I won't grade-up my system any time soon now.

As I wrote in private mail to you on 28 May 2003, "Someone [marko] on
the list recommended to deactivate AGP, which didn't help however ...
and which is very difficult when the installation itself already fails."
Though, I never received a reply from you.
The statement is still true. Commenting off "device agp" did not avoid
the freeze.

My systems's reaction on using the GENERIC kernel as on CD (latest:
5.0-CURRENT-20030505-JPSNAP.iso) while creating RAID1 ar0 on ad4 and
ad6 also was a panic:
quasar# atacontrol create RAID1 ad4 ad6
ar0: 73308MB  <ATA RAID1 array> [9345/255/63] status: READY subdisks:
disk0 READY on ad4 at ata2-master
disk1 READY on ad6 at ata3-master
panic: mutex Giant not owned at /usr/src/sys/kern/kern_exit.c:122
Debugger("panic")
Stopped at      Debugger+0x54:  xchgl   %ebx,in_Debugger.0
db>

Another answer to my reply to a posting with title "Raid0 mit IDE-Raid"
by Dominik Noetzel was that he was also using HighPoint's driver,
which, however, recognized his controller as HPT372A whereas FreeBSD
only saw HPT372.

My controller is recognized by both (HighPoint and FreeBSD) as HPT372.

This is, what I'm currently working with:
(I modified the kernel-Makefiles to automatically copy hpt37x2.ko to
the new kernel modules, since otherwise ...)

FreeBSD 5.0-RELEASE #5: Mon Aug 25 22:41:44 CEST 2003
   root@quasar:/src/src/sys/i386/compile/QUASAR50v5
Preloaded elf kernel "/boot/kernel/kernel" at 0xc05df000.
Preloaded elf module "/boot/kernel/hpt37x2.ko" at 0xc05df0a8.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05df154.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 2019893756 Hz
CPU: Pentium 4 (2019.89-MHz 686-class CPU)
<...>
hpt37x20: <HPT372 UDMA/ATA133 RAID Controller> port
0xb000-0xb0ff,0xac00-0xac03,0xa800-0xa807,0xa400-0xa403,0xa000-0xa007 irq 10
at device 0.0 on pci1
<...>
Device Driver for HPT37x2 ATA RAID Controller Version 1.32  
<...>
Waiting 5 seconds for SCSI devices to settle
sa0 at sym0 bus 0 target 2 lun 0
sa0: <HP C1533A A708> Removable Sequential Access SCSI-2 device
sa0: 10.000MB/s transfers (10.000MHz, offset 8)    
da0 at hpt37x20 bus 0 target 0 lun 0
da0: <HPT Inc. HPT37x2   RAID 1 1.05> Fixed Direct Access SCSI-2 device
da0: 73308MB (150136560 512 byte sectors: 255H 63S/T 9345C)

Therefore I plead for re-openinig the PR and fixing the ATA driver,
although some people for now have a workaround provided by HighPoint
Technologies.

Regards,
Robert

--
Dr. Robert Eckardt    ---    Robert.Eckardt@Robert-Eckardt.de