Similar error but not quite the same. When I have more info I'll let you know.
Steve
----- Original Message -----
From: "Brian Szymanski" <[EMAIL PROTECTED]>
I sent an email to highpoint tech support detailing the problems, and have
had no response after an initial ping :( ... Here is a summary of what I
sent them:
For all tests, I ran bonnie++ over and over again while concurrently
copying the contents of /usr to the mounted disk, then rm -rf'ing
repeatedly.
I tried two configurations with 2 200G drives, one RAID-0, one RAID-1.
In raid-0 mode, the kernel error was:
IAL: COMPLETION ERROR, adapter 0, channel 1, flags=104
ATA regs: error 40, sector count 20, LBA low 5f, LBA mid 16, LBA high 5f,
device 4c, status 51
Reset channel
IAL: COMPLETION ERROR, adapter 0, channel 1, flags=104
ATA regs: error 40, sector count 20, LBA low 5f, LBA mid 16, LBA high 5f,
device 4c, status 51
Reset channel
...
hptmv: Device removed: controller 1 channel 1
(da0:hptmv0:0:0:0): Synchronize cache failed, status == 0x39, scsi status
== 0x0
Opened disk da0 -> 5
Opened disk da0 -> 5
...
At this point any attempts to access any mounted files or the raw device
die with an io error.
In raid-1 mode, I got a panic:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x400
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc073646c
stack pointer = 0x10:0xe4e05ba4
frame pointer = 0x10:0xe4e05bf0
code segment = base 0x0, limit 0xfffff, type 0x1b
- DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 3 (g_up)
trap number = 12
panic: page fault
I later tried a RAID-5 array, and doing the same basic stress testing, the
machine would panic after between 3-6 hours. I didn't record the error
message, but it was something about freeing an already free page.
I upgraded the BIOS to version 1.17c from the 1.13 that was on the cards
when they shipped. This seemed to improve things, but did not eliminate
the problems. I tried fbsd 5.4 and 6.0, with both a custom kernel and
GENERIC versions. Never was I able to stress test for more than about 8-10
hours without a panic or the device becoming inaccessible.
Of course, there is also the lack of management utilities while the OS is
running which has me looking elsewhere.
I'd be willing to try further tests if folks have patches or other ideas -
I have a couple more weeks before I have to RMA the suckers, and am
willing to do testing if someone wants to make a patch...
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone (023) 8024 3137
or return the E.mail to [EMAIL PROTECTED]
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
