Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Oct 2008 06:57:04 -0700
From:      Jeremy Chadwick <koitsu@FreeBSD.org>
To:        Scott Long <scottl@samsco.org>
Cc:        Adam McDougall <mcdouga9@egr.msu.edu>, freebsd-stable@freebsd.org, JoaoBR <joao@matik.com.br>, freebsd-amd64@freebsd.org
Subject:   Re: am2 MBs - 4g + SCSI wipes out root partition
Message-ID:  <20081013135704.GA20521@icarus.home.lan>
In-Reply-To: <48F34FA0.10503@samsco.org>
References:  <200810101429.37244.joao@matik.com.br> <20081011165250.GA67552@icarus.home.lan> <48F2217C.9010000@samsco.org> <200810130947.28905.joao@matik.com.br> <48F34FA0.10503@samsco.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 13, 2008 at 07:39:44AM -0600, Scott Long wrote:
> JoaoBR wrote:
>> On Sunday 12 October 2008 14:10:36 Scott Long wrote:
>>
>>>>> I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS
>>>>> controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac
>>>>> driver) with a 5th generation RAID card with 8G of ram, both have no
>>>>> such corruption problems.  Providing this as a counter-example just to
>>>>> document some evidence of which products seem to work fine.
>>>> Is your LSI SAS controller driven by mpt(4) or mfi(4)?
>>> I can personal vouch for MPT and MFI drivers working just fine with >4GB.
>>>
>>
>>
>> let narrow this a little bit, are you talking about AM2 sockets? 
>>
>> because on AM2 the MPT drv is faulty as AHC, AHD and AACD with => 4Gigs
>>
>>
>>
>
> Sounds to me like this is a problem either with AM2 systems, or an  
> infrastructure problem in the OS that is triggered by these AM2 systems.
> Either way, it's not a SCSI driver problem.

Fully acknowledged.  I'll add an entry to my Wiki describing this
compatibility problem, but it *will not* fall under the SCSI subsection.

It sounds as if there's an implementation/design problem either in
FreeBSD's hardware compatibility support for AM2 (probably something
very low-level) systems, or there is a bug with these Gigabyte boards;
it could be either, or possibly both.  It might work in Linux because,
for all we know, Linux may have workarounds in place for whatever the
problem may be.  We simply do not know at this point.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081013135704.GA20521>