mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	fernando@quatro.com.br, linux-kernel@vger.kernel.org
Subject: Re: 2.4.18-rcx: Dual P3 + VIA + APIC
Date: Mon, 25 Feb 2002 14:19:23 +0100	[thread overview]
Message-ID: <20020225131923.GY13774@os.inf.tu-dresden.de> (raw)
In-Reply-To: <20020223231850.4ea9d3ca.skraw@ithnet.com> <58726664.1014540170@[10.10.2.3]>
In-Reply-To: <58726664.1014540170@[10.10.2.3]>

On Sun Feb 24, 2002 at 08:42:52 -0800, Martin J. Bligh wrote:
> If you are crashing near the wait_init_idle fix, you might
> try Ingo's scheduler patch - it has a different way of
> fixing this race condition.

I tried sched-O1-2.4.18-pre8-K3 and it didn't work with a SMP kernel
either.

Furthermore it also doesn't work with a UP kernel with Local IO APIC support
(CONFIG_X86_UP_IOAPIC). Without it does work. It reliably hangs in
arch/i386/kernel/io_apic.c:check_timer (in 2.4.18-pre8-K3 about line 1510)

        printk(KERN_INFO "..TIMER: vector=0x%02X pin1=%d pin2=%d\n", vector, pin1, pin2);

        if (pin1 != -1) {
                /*
                 * Ok, does IRQ0 through the IOAPIC work?
                 */
          printk(KERN_ERR "1\n");
                unmask_IO_APIC_irq(0);
          printk(KERN_ERR "2\n");
                if (timer_irq_works()) {

The "1" still occurs, then it hangs...


Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
..TIMER: vector=0x31 pin1=2 pin2=0
1




Adam
-- 
Adam                 adam@os.inf.tu-dresden.de
  Lackorzynski         http://a.home.dhs.org

  reply	other threads:[~2002-02-25 13:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 10:41 Adam Lackorzynski
2002-02-20 15:24 ` Alan Cox
2002-02-20 15:40   ` Adam Lackorzynski
2002-02-21 17:58 ` Fernando Korndorfer
2002-02-21 20:11 ` Stephan von Krawczynski
2002-02-22 13:02   ` Adam Lackorzynski
2002-02-22 13:11   ` Stephan von Krawczynski
2002-02-22 13:54     ` Fernando Korndorfer
2002-02-22 16:45     ` Adam Lackorzynski
2002-02-22 17:04     ` Stephan von Krawczynski
2002-02-22 18:20       ` Adam Lackorzynski
2002-02-23 16:38     ` Stephan von Krawczynski
2002-02-23 17:22       ` Alan Cox
2002-02-23 22:18       ` Stephan von Krawczynski
2002-02-24 16:42         ` Martin J. Bligh
2002-02-25 13:19           ` Adam Lackorzynski [this message]
2002-02-25 15:32             ` Martin J. Bligh
2002-02-25 16:17               ` Adam Lackorzynski

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=20020225131923.GY13774@os.inf.tu-dresden.de \
    --to=adam@os.inf.tu-dresden.de \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=fernando@quatro.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.com \
    /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®