mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Drew Bertola <drew@drewb.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problems w/ 2.6.6 on smp system...
Date: Mon, 24 May 2004 03:56:37 -0700	[thread overview]
Message-ID: <1085396197.2870.27.camel@ws.thecoop.net> (raw)
In-Reply-To: <1085373949.2758.12.camel@ws.thecoop.net>

[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]

[Again, sorry to reply to my own post.  Someone's bound to email me in 6
or 8 months wondering if I ever found a solution.  My second post in
this thread has dmesg output, etc.]

On Sun, 2004-05-23 at 21:45, Drew Bertola wrote:
> On Sun, 2004-05-23 at 00:55, Drew Bertola wrote:
> > I've installed FC2 and am experiencing problems with usb devices and
> > ethernet cards (it might be everything on the pci bus).  I don't
have
> > this problem with their UP kernel, but I do have it with their SMP
> > kernel.
> > 
> > I decided to build a 2.6.6 using the FC2 i686-smp config to see if
that
> > would help, but I have the same problems.

Passing "noapic" as a kernel option fixes this.

[For anyone wondering how, read the bottom of this post].

This is a bit of voodoo to me.  I didn't seem to be able to configure
out the CONFIG*_APIC_* options when I built the kernel.  Even if I
manually edited the .config file, the options were re-inserted.  I
believe this is due to my choice of arch and SMP.

CONFIG_MPENTIUMIII=y
...
CONFIG_SMP=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_SMP=y
...
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y

> > The system is a Tyan Tiger 230T (S2507T) with dual 800MHz PIIIs. 
This
> > board has a Via Apollo Pro133T chipset, a VT82C694T north bridge,
and a
> > VT82CC686B south bridge.  lspci output is below.
> 
> 1 GB ram.
> 
> > I have 2 nics installed (e100 and 8139too).  Both have the right
modules
> > loaded and are configured properly (including routes), but I can't
ping
> > out of the system nor do anything else over the network other than
> > pinging the nics themselves.
> > 
> > My usb hosts are detected, but nothing attached works.  My usb
optical
> > mouse doesn't even light up.
> > 
> > All of these problems go away in UP mode.

To recap the solution, pass the "noapic" option to the kernel at boot
time.  Typically, edit grub.conf with "noapic" appended to the kernel
line like so:

title Custom 2.6.7-rc1-smp
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.7-rc1 ro root=LABEL=/ noapic
        initrd /boot/initrd-2.6.7-rc1.img

You might have other options as well.

--
Drew

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-05-24 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-23  7:55 Drew Bertola
2004-05-24  4:45 ` Drew Bertola
2004-05-24 10:56   ` Drew Bertola [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=1085396197.2870.27.camel@ws.thecoop.net \
    --to=drew@drewb.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®