From: Manfred Spraul <manfred@colorfullife.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Frank de Lange <frank@unternet.org>,
dwmw2@infradead.org, linux-kernel@vger.kernel.org, mingo@elte.hu,
torvalds@transmeta.com
Subject: Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware
Date: Sat, 13 Jan 2001 01:06:24 +0100 [thread overview]
Message-ID: <3A5F9C00.959DF2BB@colorfullife.com> (raw)
In-Reply-To: <E14HDjY-0005Ei-00@the-village.bc.nu>
Alan Cox wrote:
>
> > Could you disable both bandaids? I disabled them, no problems so far.
> > Now back to the disable_irq_nosync().
>
> Ok so it looks like the disable_irq code is buggy. Unfortunately its not
> just used for these drivers they are just the heaviest users.
>
> Given that we can see the IRQ is still set on the APIC can we fake an IRQ in
> that condition ?
Switch to edge triggered, wait , switch back to level triggered - I've
added that to my sysrq commands, and it clears the IRR bit in the IO
APIC. Sometimes 2 or 3 attempts are required.
I tried several changes to the ioapic code, but without success.
I found:
* the io_apic_sync() in __mask_IO_APIC_irq() is probably wrong, I'd say
it should be _after_ the io_apic_modify, but currently it is before the
io_apic_modify(). 2.2 uses the same code, that doesn't explain the
problem.
* this comment in
http://oss.sgi.com/www.linux.sgi.com/intel/visws/visws.2210.28jul99.patch
+/* XXX ouch... is this really our only choice for masking this
interrupt? */
+/* XXX not fully safe for 2 reasons:
+ * 1) should not touch an apic entry while (whole) apic is enabled
+ * 2) careful about storing to IRR bit (unless we know this intr is
idle)
+ */
+static void disable_cobalt_irq(unsigned int irq) /* disable_irq()
*/
+{
+ int ent = is_co_apic(irq);
+ if (ent == -1) {
+ return; /* could actually be a panic */
+ }
+
+ /* Note: h/w nada like read-mod-write! Vec saved in
IRQ_VECTOR() */
+ co_apic_write(CO_APIC_LO(ent), CO_APIC_MASK);
+ (void)co_apic_read(CO_APIC_LO(ent)); /* sync cpu to cobalt apic
*/
+}
+
It's possible that the comment is about an cobalt specific problem, the
IRR bit is - according the Intel documentation - read only.
--
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 prev parent reply other threads:[~2001-01-13 0:06 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 17:16 QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related? 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 20:11 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardwarerelated? Manfred Spraul
2001-01-12 20:16 ` Frank de Lange
2001-01-12 20:19 ` Ingo Molnar
2001-01-12 20:26 ` Frank de Lange
2001-01-12 20:31 ` Ingo Molnar
2001-01-12 20:35 ` Frank de Lange
2001-01-12 20:37 ` Ingo Molnar
2001-01-12 20:46 ` David Woodhouse
2001-01-12 20:46 ` Frank de Lange
2001-01-12 20:51 ` Ingo Molnar
2001-01-12 21:05 ` Frank de Lange
2001-01-15 2:00 ` Jorge Nerin
2001-01-13 0:15 ` Linus Torvalds
2001-01-13 0:19 ` Frank de Lange
2001-01-13 0:29 ` Alan Cox
2001-01-12 20:54 ` Manfred Spraul
2001-01-12 21:07 ` Frank de Lange
2001-01-12 21:31 ` Manfred Spraul
2001-01-12 23:50 ` Alan Cox
2001-01-12 21:21 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related? Frank de Lange
2001-01-12 23:35 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware Alan Cox
2001-01-13 0:06 ` Manfred Spraul [this message]
2001-01-13 0:36 ` Linus Torvalds
2001-01-13 0:48 ` Frank de Lange
2001-01-13 0:56 ` Linus Torvalds
2001-01-13 1:27 ` Frank de Lange
2001-01-13 1:51 ` Manfred Spraul
2001-01-13 2:11 ` Frank de Lange
2001-01-13 1:49 ` Jens Axboe
2001-01-13 2:12 ` Andrew Morton
2001-01-13 2:48 ` Linus Torvalds
2001-01-13 3:24 ` Andrew Morton
2001-01-13 12:37 ` Russell King
2001-01-13 15:18 ` Call for testers: ne2k-pci and io apic (was: Re: QUESTION: Network hangs with BP6...) Manfred Spraul
2001-01-13 23:55 ` Manfred Spraul
2001-01-14 0:18 ` Call for testers: ne2k-pci and io apic J . A . Magallon
2001-01-14 0:23 ` Call for testers: ne2k-pci and io apic (was: Re: QUESTION: Network hangs with BP6...) J . A . Magallon
2001-01-14 2:14 ` Call for testers: ne2k-pci and io apic J . A . Magallon
2001-01-15 16:15 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware Zdenek Kabelac
2001-01-13 1:38 ` Manfred Spraul
2001-01-13 2:10 ` Andrew Morton
2001-01-12 17:49 ` Alan Cox
2001-01-12 18:08 ` Manfred Spraul
2001-01-12 18:16 ` Ingo Molnar
2001-01-12 18:45 ` Manfred Spraul
2001-01-12 18:48 ` Ingo Molnar
2001-01-12 18:28 ` Linus Torvalds
2001-01-12 23:27 ` Alan Cox
2001-01-13 0:35 ` Linus Torvalds
2001-01-13 0:43 ` Alan Cox
2001-01-13 0:48 ` Linus Torvalds
2001-01-12 19:05 ` Frank de Lange
2001-01-12 20:04 ` Linus Torvalds
2001-01-15 14:36 ` Roeland Th. Jansen
2001-01-12 22:03 ` Latest status of IDE patches from Andre Jeff Nguyen
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=3A5F9C00.959DF2BB@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=frank@unternet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.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