public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Marc Perkel <marc@perkel.com>
Cc: Vladimir Lazarenko <vlad@lazarenko.net>, linux-kernel@vger.kernel.org
Subject: Re: sata_nv + SMP = broken?
Date: Fri, 21 Oct 2005 22:38:25 +0200	[thread overview]
Message-ID: <200510212238.25614.rjw@sisk.pl> (raw)
In-Reply-To: <4359144F.8090504@perkel.com>

Hi,

On Friday, 21 of October 2005 18:16, Marc Perkel wrote:
> 
> Vladimir Lazarenko wrote:
> 
> > Hello,
> >
> > 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.
> >
> 
> For what it's worth I too have seen this same problem. It happens when I 
> use the stock Fedora kernels but not my custom compiled kernel. I'm not 
> sure what I compiled differently but at the time I thought that 
> something in the new kernel fixed it.

I only use kernel.org kernels, so perhaps there's a problem with the Fedora
kernel.

> 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.

Greetings,
Rafael

  reply	other threads:[~2005-10-21 20:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21 10:33 sata_nv + SMP = broken? Vladimir Lazarenko
2005-10-21 12:04 ` Rafael J. Wysocki
2005-10-21 16:16 ` Marc Perkel
2005-10-21 20:38   ` Rafael J. Wysocki [this message]
2005-10-21 20:46     ` Vladimir Lazarenko
2005-10-22  9:15     ` Vladimir Lazarenko
2005-10-22 18:40       ` Rafael J. Wysocki
2005-10-22 19:59         ` Vladimir Lazarenko
2005-10-26  1:03           ` Vladimir Lazarenko
2005-10-26  9:39             ` Rafael J. Wysocki
2005-10-26 12:01               ` Vladimir Lazarenko
  -- strict thread matches above, loose matches on Subject: below --
2005-10-26 18:34 Allen Martin
2005-10-26 19:49 ` Vladimir Lazarenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200510212238.25614.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@perkel.com \
    --cc=vlad@lazarenko.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox