From: Johannes Erdfelt <jerdfelt@valinux.com>
To: Shane Wegner <shane@cm.nu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.20pre1: Problems with SMP
Date: Mon, 7 May 2001 11:18:22 -0700 [thread overview]
Message-ID: <20010507111822.I903@valinux.com> (raw)
In-Reply-To: <20010506175050.A1968@cm.nu> <E14wiNn-0003JF-00@the-village.bc.nu> <20010507102053.A2276@cm.nu> <20010507110250.H903@valinux.com> <20010507111436.A17314@cm.nu>
In-Reply-To: <20010507111436.A17314@cm.nu>; from shane@cm.nu on Mon, May 07, 2001 at 11:14:36AM -0700
On Mon, May 07, 2001, Shane Wegner <shane@cm.nu> wrote:
> On Mon, May 07, 2001 at 11:02:50AM -0700, Johannes Erdfelt wrote:
> > On Mon, May 07, 2001, Shane Wegner <shane@cm.nu> wrote:
> > >
> > > That does indeed correct the problem. 2.2.20pre1 now works
> > > as expected.
> >
> > Hmm, that uses a VIA based chipset. I didn't know they did SMP yet. Does
> > 2.4 work on this system?
>
> The last 2.4 kernel I tried was 2.4.3 I believe and it
> worked fine more or less. I haven't tried any later 2.4
> kernels yet.
That's fine. The I/O APIC code is different and I tried to make the 2.2
code work like the 2.4 code with minimal changes. However, the changes
aren't trivial. I'll take a quick look and see if I can find any more
significant differences.
I wonder if I have a VIA board laying around here.
JE
next prev parent reply other threads:[~2001-05-07 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 0:50 2.2.20pre1: Problems with SMP Shane Wegner
2001-05-07 10:36 ` Alan Cox
2001-05-07 17:20 ` Shane Wegner
2001-05-07 18:02 ` Johannes Erdfelt
2001-05-07 18:14 ` Shane Wegner
2001-05-07 18:18 ` Johannes Erdfelt [this message]
2001-05-16 19:56 ` Johannes Erdfelt
2001-05-17 2:27 ` Shane Wegner
2001-05-17 3:38 ` Johannes Erdfelt
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=20010507111822.I903@valinux.com \
--to=jerdfelt@valinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=shane@cm.nu \
/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.