From: Manfred Spraul <manfred@colorfullife.com>
To: frank@unternet.org, linux-kernel@vger.kernel.org
Subject: Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related?
Date: Fri, 12 Jan 2001 17:53:43 +0100 [thread overview]
Message-ID: <3A5F3697.38DEA1FE@colorfullife.com> (raw)
Let's decode it:
> IO APIC #2......
> NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
> 12 0FF 0F 0 1 0 1 0 1 1 91
> 13 0FF 0F 0 1 1 1 0 1 1 99
IRR for interrupt 19 is set, that means the IO APIC has sent the
interrupt to a cpu but not yet received the corresponding EOI.
That bit is read only, so we can't set it to 0 to kick the io apic.
The Vector is 99, we must check that bit in the ISR, TMR and IRR of both
cpus.
cpu1:
> ISR: all bits 0
> TMR: only bit 0x99 is set
> IRR: all bits 0
cpu0:
> ISR: all bits 0
> TMR: only bit 0x89 is set
> IRR: bit 0xfc and bit 0xef are set.
ISR is the in-server register, 0 means that the cpu is not processing an
interrupt right now.
TMR is the trigger mode registers, 1 means that the local apic should
send an EOI to the io apic when the cpu signals the EOI to the local
apic.
IRR is the list of pending interrupts:
0xef is the local timer interrupt,
0xfc is the reschedule interrupt
(see include/asm-i386/hw_irq.h)
These bits are also read only.
If you search the IO APIC documentation: number 29056601 - just search
with google. The local APIC is documented in the main cpu handbook (PPro
or later), in the chapter about multiple processor management
--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-12 16:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 16:53 Manfred Spraul [this message]
2001-01-12 17:02 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related? David Woodhouse
[not found] <20010112165104.A22465@unternet.org>
2001-01-16 19:23 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2001-01-12 17:16 Manfred Spraul
2001-01-12 17:33 ` Frank de Lange
2001-01-12 17:51 ` Manfred Spraul
2001-01-12 18:25 ` Frank de Lange
2001-01-12 19:04 ` Manfred Spraul
2001-01-12 19:07 ` Frank de Lange
2001-01-12 19:21 ` Frank de Lange
2001-01-12 19:33 ` Manfred Spraul
2001-01-12 19:52 ` Frank de Lange
2001-01-12 19:59 ` Linus Torvalds
2001-01-12 20:03 ` Ingo Molnar
2001-01-14 0:13 ` Roeland Th. Jansen
2001-01-14 0:23 ` Frank de Lange
2001-01-12 20:05 ` Frank de Lange
2001-01-12 21:21 ` Frank de Lange
2001-01-10 21:30 Frank de Lange
2001-01-10 22:21 ` Manfred Spraul
2001-01-10 22:29 ` Frank de Lange
2001-01-10 22:40 ` Frank de Lange
2001-01-11 11:48 ` Andrew Morton
2001-01-11 15:22 ` Frank de Lange
2001-01-11 16:55 ` Frank de Lange
2001-01-11 19:18 ` Frank de Lange
[not found] ` <3A5E0849.EB428D70@mandrakesoft.com>
2001-01-12 0:28 ` Frank de Lange
2001-01-12 11:40 ` Andrew Morton
2001-01-12 15:06 ` Frank de Lange
2001-01-12 15:36 ` Frank de Lange
2001-01-11 19:38 ` Frank de Lange
2001-01-11 19:49 ` Frank de Lange
2001-01-11 21:09 ` Frank de Lange
2001-01-11 21:47 ` Jeff Garzik
2001-01-11 21:53 ` Frank de Lange
2001-01-12 14:35 ` David Woodhouse
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=3A5F3697.38DEA1FE@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=frank@unternet.org \
--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