mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: kernel@Expansa.sns.it (Luigi Genoni)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	linux-kernel@vger.kernel.org (Linux Kernel)
Subject: Re: spurious interrupt with ac kernel but not with vanilla 2.4.9
Date: Fri, 21 Sep 2001 18:03:56 +0100 (BST)	[thread overview]
Message-ID: <E15kTiW-0000X2-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.33.0109211828390.31425-100000@Expansa.sns.it> from "Luigi Genoni" at Sep 21, 2001 06:39:05 PM

> I noticed that on the abit kt7A MBs that i have, with via KT133A chipset,
> after i installed the kernel 2.4.9-ac10 (ac11 and 12 as well),
> at boot i get this message,
> 
> Sep 21 11:52:11 DarkStar kernel: ice 00:0b.0
> Sep 21 11:52:11 DarkStar kernel: spurious 8259A interrupt: IRQ7.
>  immediatelly before scsi adaptec detection and inizzializzation.

Thats indicating an IRQ appeared and vanished. IRQ 7 is the IRQ that happens
to occur for this.

> I was thinking to an HW problem, but with vanilla 2.4.9 kernel I do not
> get this message, and the code in arch/i386/kernel/i8259.c that should
> detect this spurious interrup is just the same on those two kernels.
> Changes are related to X86_IO_APIC, and I think this is the reason why
> this spurious interrupt is detected, but I would like to know if i should
> think I have some HW problem going on that stardard kernels do not detect.

The APIC only applies to multiprocessor boxes unless you are building with
uniprocessor apic support. Build a non SMP kernel without apic support
and let me know what that does

  reply	other threads:[~2001-09-21 16:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-16 21:43 [patch] block highmem zero bounce v14 Jens Axboe
2001-09-16 21:48 ` Linus Torvalds
2001-09-16 22:00   ` Jens Axboe
2001-09-16 23:10     ` Alan Cox
2001-09-16 23:13       ` Jens Axboe
2001-09-21 15:44     ` Arjan van de Ven
2001-09-21 16:13       ` Alan Cox
2001-09-21 16:39         ` spurious interrupt with ac kernel but not with vanilla 2.4.9 Luigi Genoni
2001-09-21 17:03           ` Alan Cox [this message]
2001-09-21 17:14             ` Luigi Genoni
2001-09-21 17:28               ` Alan Cox
2001-09-21 17:33                 ` Luigi Genoni
2001-09-22 14:39                 ` John Levon
2001-09-22 11:00       ` [patch] block highmem zero bounce v14 Jens Axboe
2001-09-22 11:18         ` Arjan van de Ven
2001-09-22 12:11           ` Jens Axboe
2001-09-22 16:32           ` Alan Cox
2001-09-22 16:35             ` Jens Axboe
2001-09-22 16:41               ` Alan Cox
2001-09-22 16:56                 ` Jens Axboe
2001-09-22 17:05                 ` Arnaldo Carvalho de Melo
2001-09-20 23:43 ` David S. Miller
2001-09-21  5:56   ` Jens Axboe

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=E15kTiW-0000X2-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=kernel@Expansa.sns.it \
    --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

all inboxes | Powered by JetHome®