From: Andreas Haumer <andreas@xss.co.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Reid Hekman <reid.hekman@ndsu.nodak.edu>, linux-kernel@vger.kernel.org
Subject: Re: Linux-2.2.20 SMP & Asus CUR-DLS: "stuck on TLB IPI wait (CPU#3)"
Date: Sun, 13 Jan 2002 12:45:40 +0100 [thread overview]
Message-ID: <3C417364.5358BEDD@xss.co.at> (raw)
In-Reply-To: <E16PZxl-0003lQ-00@the-village.bc.nu>
Hi!
Alan Cox wrote:
>
> > > 2.2 does not support VIA SMP, its probably not a good kernel to choose for
> > > the buggy VIA chipsets either.
> >
> > So ServerWorks (re: his Asus CUR-DLS) is right out as well?
>
> Serverworks I don't know. I've got reports of serverworks SMP working perfectly
> well in the 2.2 tree so I don't know what the full story is there.
This board worked fine for several months under 2.2.18
I then upgraded to 2.2.20 yesterday and noticed this problem
for the first time (I didn't try 2.2.19 on it)
I still have the full 2.2.18 installation (I did the 2.2.20
installation on a separate SCA harddisk) so I can easily
switch. To see if it's a hardware problem I already switched
back to 2.2.18 once, and the problem went away.
Under 2.2.20 I have to boot with "noapic" to have it running
smoothly.
So if someone wants me to try or test something, just send
me a short note.
- andreas
--
Andreas Haumer | mailto:andreas@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
next prev parent reply other threads:[~2002-01-13 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 22:02 Linux-2.2.20 SMP & Asus CUR-DLS: "stuck on TLB IPI wait (CPU#3)" Andreas Haumer
2002-01-12 22:34 ` Benjamin LaHaise
2002-01-12 23:01 ` Andreas Haumer
2002-01-12 23:14 ` Benjamin LaHaise
2002-01-13 1:39 ` Alan Cox
2002-01-13 1:45 ` Reid Hekman
2002-01-13 2:01 ` Alan Cox
2002-01-13 11:45 ` Andreas Haumer [this message]
2002-01-13 15:39 ` Alan Cox
2002-01-13 15:55 ` Andreas Haumer
2002-01-13 16:26 ` Andreas Haumer
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=3C417364.5358BEDD@xss.co.at \
--to=andreas@xss.co.at \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=reid.hekman@ndsu.nodak.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.