Soren Schmidt wrote:
>
[...]
>
> If you are using the newest code, then the problem might be that
> your disks doesn't work proberly with UDMA66. I've seen several
> newer disks that has problems here, and frankly Maxtor is not
> known for their quality in this respect.
I cvsupped this morning. AFAIK I have the newest code.
> You could try to disable the UDMA66 code on the HPT chips by
> ifdef'ing out the code that deals with it like below, if this
> helps you are most like dealing with disks that has problems
> with UDMA66. Dont be alarmed though, there is next to no
> performance difference for you...
Tried this patch, and the system does not hang any more. Even better,
I/O to this disk is still quite fast, at least way faster than using the
"standard" interface on this board (and even that is not really slow).
I'll run a "buildworld" as torture test this evening.
> Trying another disk is also an option, I know that the IBM's
> work just fine, and that some of the Quantums and WDC's are broken.
I'll try a WD from my other BP6 one off these days. Maybe I had better
buy IBM
in the future.
BTW, would it be possible to modify sysctl() to switch between UDMA66
and UDMA33, or maybe use "flags" like the old wd driver had. I fear that
a lot of "broken" hardware is around, and once FreeBSD 4.0 hits the
streets, you may expect a lot of problem reports.
> -Søren
Kind regards,
Hans
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
