From: Gilles May <gilles@jekyll.org>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: SMP trouble
Date: Fri, 20 Jan 2006 03:58:22 +0100 [thread overview]
Message-ID: <43D051CE.8060609@jekyll.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0601191826520.1579@montezuma.fsmlabs.com>
Zwane Mwaikambo wrote:
>On Thu, 19 Jan 2006, Gilles May wrote:
>
>
>
>>I don't think it has something to do with the USB card, nor the HDD oder the
>>DVD writer connected to it..
>>Just to be sure I bought a new USB card with a different chip even, hangs with
>>both controllers..
>>Besides it freezes aswell if I do the ping and IDE to IDE copies and listening
>>music.. Looks like high
>>IO loads brings it down, no matter where it comes from..
>>The wierd part is that it's only with Linux SMP, not with UP, and no problems
>>like that on WindowsXP SP2..
>>
>>This starts giving me serious headaches.. ;)
>>
>>
>
>Trying to isolate things here, do you need the ping/network load to
>trigger it? How about only network load?
>
>
Hmm good question, I'll do further tests, but from my past experiences I
got the feeling that it's rather the sound that is needed to trigger the
freeze, not the network load.
A few lines from dmesg puzzle me too, like:
spurious 8259A interrupt: IRQ7. -> What is that, and why?
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration. -> Maybe not corrected correctly?
BIOS failed to enable PCI standards compliance, fixing this error. ->
Maybe not really fixed?
Thanks for your effort,
Gilles May
PS: Am I the only one with a K7D Master-L and problems like that?
prev parent reply other threads:[~2006-01-20 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 2:05 SMP trouble Gilles May
2006-01-19 5:16 ` Zwane Mwaikambo
2006-01-19 18:20 ` Gilles May
2006-01-19 19:32 ` Zwane Mwaikambo
2006-01-19 19:45 ` Gilles May
2006-01-20 2:27 ` Zwane Mwaikambo
2006-01-20 2:58 ` Gilles May [this message]
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=43D051CE.8060609@jekyll.org \
--to=gilles@jekyll.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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