From: Athanasius <link@miggy.org>
To: Danny ter Haar <dth@uucp.cistron.nl>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
andre@linux-ide.org, andre@linuxdiskcert.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: Linux 2.4.21-rc1
Date: Wed, 23 Apr 2003 17:40:16 +0100 [thread overview]
Message-ID: <20030423164015.GJ25981@miggy.org> (raw)
In-Reply-To: <20030423153603.GI25981@miggy.org>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
On Wed, Apr 23, 2003 at 04:36:04PM +0100, Athanasius wrote:
> On Wed, Apr 23, 2003 at 05:21:44PM +0200, Danny ter Haar wrote:
> > In article <cistron.20030423150956.GH25981@miggy.org> you write:
> > > I'm still seeing a problem with my primary IDE channel locking up for
> > >10-15s at a time, an event I can trigger by running updatedb (i.e. the
> > >database update for 'locate').
> > >
> >
> > I have similar problems.
> > I "cured" it with dis-abling "IO-APIC"
> >
> > Could you recompile a kernel without the io-apic option ?
> >
> > local-apic on UP is ok, only disable io-apic.
>
> Aha, a reply about this at last. I forgot to put my config in on the
> original post, was going to follow up with it when I saw the post come
> up. Anyway, yes, I have:
>
> # CONFIG_SMP is not set
> CONFIG_X86_UP_APIC=y
> CONFIG_X86_UP_IOAPIC=y
> CONFIG_X86_LOCAL_APIC=y
> CONFIG_X86_IO_APIC=y
>
> currently, I'll go try with all but CONFIG_X86_LOCAL_APIC set to n
> then.
Yup, that *seems* to have fixed it. Booted up, updatedb run, compile
of a few things done, running X, even burned a CD, no sign of the
reported problem.
This could do with some easily accessible documentation someplace, but
I'm not sure *where* such should go.
-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2003-04-23 16:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cistron.Pine.LNX.4.53L.0304211545580.12940@freak.distro.conectiva>
[not found] ` <E198M48-0000tC-00@ncc1701.cistron.net>
2003-04-23 15:36 ` Linux 2.4.21-rc1 Athanasius
2003-04-23 16:40 ` Athanasius [this message]
2003-04-25 16:17 ` Bill Davidsen
2003-04-25 20:30 ` Athanasius
2003-05-06 4:30 ` Mike Fedyk
2003-04-21 18:47 Marcelo Tosatti
2003-04-21 19:58 ` Stephan von Krawczynski
2003-04-21 22:49 ` Ben Greear
2003-04-21 23:24 ` Willy Tarreau
2003-04-21 23:10 ` J.A. Magallon
2003-04-22 3:00 ` Corey Minyard
2003-04-22 21:49 ` Marcelo Tosatti
2003-04-22 22:54 ` Corey Minyard
2003-04-22 13:42 ` Geert Uytterhoeven
2003-04-22 17:09 ` Rene Rebe
2003-04-22 19:15 ` Lukasz Trabinski
2003-04-22 22:59 ` J.A. Magallon
2003-04-23 8:08 ` Jerome Chantelauze
2003-04-23 15:09 ` Athanasius
2003-04-23 20:46 ` Olaf Hering
2003-04-30 21:30 ` Carl-Daniel Hailfinger
2003-04-25 3:06 ` Lucas Correia Villa Real
2003-06-07 19:35 ` Adrian Bunk
2003-06-11 4:27 ` Lucas Correia Villa Real
2003-04-25 3:13 ` Lucas Correia Villa Real
2003-04-25 14:15 ` Andreas Metzler
2003-04-25 14:27 ` Martin Josefsson
2003-04-25 14:46 ` Andreas Metzler
2003-04-25 16:19 ` Zed Pobre
2003-04-25 16:24 ` Marc-Christian Petersen
2003-05-06 2:57 ` Mike Fedyk
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=20030423164015.GJ25981@miggy.org \
--to=link@miggy.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=andre@linuxdiskcert.org \
--cc=dth@uucp.cistron.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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;
as well as URLs for NNTP newsgroup(s).