From: "Robbert Kouprie" <robbert@radium.jvb.tudelft.nl>
To: "'Helge Hafting'" <helgehaf@aitel.hist.no>
Cc: "'Raphael Manfredi'" <Raphael_Manfredi@pobox.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: The buggy APIC of the Abit BP6
Date: Tue, 18 Jun 2002 11:53:26 +0200 [thread overview]
Message-ID: <003501c216ad$ff50bdb0$020da8c0@nitemare> (raw)
Helge Hafting wrote:
> I'll try it. Have you considered resubmitting the patch,
> hidden behind a CONFIG_BROKEN_APIC? That'll keep the code
> clean for those with better hardware.
We might as well move the kick_IO_APIC_irq call to the
arch/i386/kernel/irq.c:ack_none function then, surrounded by proper
#ifdefs. The ack_none is the function that does the printk("unexpected
IRQ trap at vector %02x\n", irq), which I see everytime the bug
triggers.
And looking at the comment of the end_level_ioapic_irq function in
io_apic.c, is there a possibility to replace the kick_IO_APIC_irq call
entirely with a end_level_ioapic_irq call? I see lots of similarities in
these two functions.
I didn't test this yet, as I'm still running on Raphael's patch, waiting
for the bug to trigger. (Anyone got a reliable way of triggering it?)
Regards,
- Robbert Kouprie
next reply other threads:[~2002-06-18 9:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 9:53 Robbert Kouprie [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-14 16:49 The buggy APIC of the Abit BP6 Robbert Kouprie
2002-06-14 18:41 ` Raphael Manfredi
2002-06-18 7:33 ` Helge Hafting
2002-06-12 22:33 Robbert Kouprie
2002-06-13 9:05 ` Helge Hafting
2002-06-13 13:30 ` Robbert Kouprie
2002-06-14 10:54 ` Helge Hafting
2002-06-18 15:30 ` Robbert Kouprie
2002-06-18 15:17 ` Zwane Mwaikambo
2002-06-19 12:47 ` Maciej W. Rozycki
2002-06-19 13:23 ` Robbert Kouprie
2002-06-19 14:03 ` Keith Owens
2002-06-19 14:35 ` Maciej W. Rozycki
2002-06-20 1:50 ` Robbert Kouprie
2002-06-19 14:22 ` Maciej W. Rozycki
2002-06-20 12:21 ` Helge Hafting
2002-06-20 13:10 ` Maciej W. Rozycki
2002-06-21 13:02 ` Helge Hafting
2002-06-20 22:29 ` Kevin Krieser
2002-06-14 15:07 ` Raphael Manfredi
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='003501c216ad$ff50bdb0$020da8c0@nitemare' \
--to=robbert@radium.jvb.tudelft.nl \
--cc=Raphael_Manfredi@pobox.com \
--cc=helgehaf@aitel.hist.no \
--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