Re: sata_nv + SMP = broken?

[Rafael J. Wysocki]

Hi,

On Saturday, 22 of October 2005 11:15, Vladimir Lazarenko wrote:
> >>>Yesterday I've tried launching various kernels on Ahtlon64 Dual-core 
> >>>X2 3800+ with MSI Neo4 Platinum SLI motherboard.
> >>>
> >>>The results were a total catastrophica failure. As soon as I enable 
> >>>SMP in the kernel, the sata driver would randomly hang after a bit of 
> >>>disk activity.
> >>>
> >>>Whenever apic is enabled, the system won't even be able to boot up 
> >>>completely, and will hang VERY soon. Whenever I disable apic, the 
> >>>system is able to bootup, but when the software mirror that I use will 
> >>>try to resync for 2-3-10 mins, it will throw up a message and freeze 
> >>>again.
> >>>
> >>>Whenever I disable apic AND lapic, the system is able to bootup AND 
> >>>work, however after same 5-10 minutes it start spitting messages, 
> >>>which are somewhat different thou and don't hang the system completely 
> >>>but render it rather unusable anyway.
> >>>
> >>>As soon as I disable SMP - everything works like a charm.
> >>>
> >>I too am running an Athlon X2 using sata_nv. I have an ASUS motherboard. 
> >>But what I noticed was that the problem went away if I used 2 gigs of 
> >>ram instead of 4 gigs. When you use the whole 4 gigs there is some 
> >>memory mapping going on and I thought perhaps the problem was related to 
> >>the sata_nv not liking the memory mapped over the 4gig barrier.
> > 
> > That's possible.  Unfortunately I cannot verify this, since there are 2GB of
> > RAM in my box.
> > 
> > I remeber someone having a problem with sata_nv DMAing over 2GB of RAM,
> > so there may be something wrong with it.
> 
> On a second thought. Why would that only occur in SMP mode? Since now 
> the box is with 3G ram, no SMP and it works like a charm. If I enable 
> SMP - the hell breaks loose.

It looks like an obscure issue.  Apparently, to trigger it you need _both_
more that 2GB of RAM and SMP.

OTOH, today I played with Tyan Thunder K8WE, based on the Nvidia
CK8-04 chipset (not that much different to the regular Nforce4) in
a 2-processor configuration and 8GB of RAM, and it had no issues at all
(I installed SuSE 9.3 with the distro kernel on it).  Anyway its SATA
controller is handled by the sata_nv driver, so the problem you describe
does not seem to be software-related.

I guess it's a hardware problem with the single-processor Nforce4 chipset
and a dual-core CPU.  Still I have no idea what exactly it may be.

[Jeff, could you please say if this is a known problem?]

Greetings,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/