>David Greenman wrote:
>>
>> >> So if this problem is NOT related to specific hardware, how can we get
>> >> the driver fixed?
>> >
>> >Talk to the maintainer (David). We've offered him cores and kernels
>> >before. Alternatively, you'll need to experiment with your setup to
>> >determine what characterises the failures and help David out with more
>> >data.
>>
>> Hotmail has troubleshooted the problem down to the NCR controller. It
>> appears that the problem only occurs when using one of those. If they plug
>> in an Adaptec 2940 and use it instead of the onboard NCR then the problems
>> disappear.
>
> Well that's not good, since I have almost convinced my boss to replace
>the crappy IDE drives on our shiny new Intel N440BX mb's with scsi
>drives since the controller is built in. :-/ Does this look like a
>soluble problem, or is it just going to be a case of "don't do that?"
>Anything I can do to help mail me and let me know.
Intel generally makes good stuff. On the other hand, I'm not too happy with
the NCR/Symbios support in FreeBSD...the conversion to CAM wasn't all that
great and the driver really needs a rewrite. I wouldn't personally put a
machine with an NCR/Symbios into production - I have just too much negative
history with it.
I don't understand why some machines are having this problem with the Intel
Pro/100B/100+ and (most) others never do. All indications right now is that it
is a DMA corruption problem of some kind, but I don't have any clue what might
be causing it. I don't think it is a software bug, but it's conceivable that
the problem could be worked around with software if I knew what was causing
it.
-DG
David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
