All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Swingley <cswingle@iarc.uaf.edu>
To: Len Brown <len.brown@intel.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: IRQ issues, (nobody cared, disabled), not USB
Date: Mon, 12 Jul 2004 06:43:18 -0800	[thread overview]
Message-ID: <20040712144318.GB2113@iarc.uaf.edu> (raw)
In-Reply-To: <1089514128.32038.62.camel@dhcppc2>

Len,

* Len Brown <len.brown@intel.com> [2004-Jul-10 18:48 AKDT]:
> It would be interesting if the IRQ failure was always on IRQ7.
> 
> When you moved slots, did the device move to a different
> IRQ and fail there too?

I can't remember for sure.  My system logs go back to June, and all of 
the errors back to then are on IRQ 7.  But I don't remember when I tried 
a different slot.

> Running ACPI, you may be able to move that device off of
> IRQ7 with "acpi_irq_balance" plus "acpi_isa_irq=7".

I'm giving this a go now that 2.6.5 didn't help.  With these parameters, 
/proc/interrupts looks like:


           CPU0       
  0:     509088          XT-PIC  timer
  1:       2408          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  8:          4          XT-PIC  rtc
  9:          0          XT-PIC  acpi
 10:      41821          XT-PIC  eth0, mga@PCI:1:0:0
 11:          0          XT-PIC  uhci_hcd, uhci_hcd, uhci_hcd, EMU10K1, eth1
 12:       2102          XT-PIC  i8042
 14:     236597          XT-PIC  ide0
 15:        328          XT-PIC  ide1
NMI:          0 
LOC:     509008 
ERR:       1693
MIS:          0

Seems like a lot of stuff on IRQ 11. . .

> Hardware routes spurious interrupts to IRQ7, so your
> device may be an innocent victim of those.  Also,
> there may be some motherboard device pulling on IRQ7
> that Linux doesn't know about -- so see if you can
> disable any extra motherboard devices in BIOS setup.

I already have everything I'm not using (serial, parallel ports) 
disabled.

> Finally, you might run a kernel with the IOAPIC enabled,
> such as the CONFIG_SMP kernel, to see if you have an
> IOAPIC on the board and if that mode works differently.

I'll maybe give that a try at some point, if the IRQ balancing doesn't 
help.

Thanks again,

Chris
-- 
Christopher S. Swingley          email: cswingle@iarc.uaf.edu (work)
Intl. Arctic Research Center            cswingle@gmail.com (personal)
University of Alaska Fairbanks   www.frontier.iarc.uaf.edu/~cswingle/


  reply	other threads:[~2004-07-12 14:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615FFACC@hdsmsx403.hd.intel.com>
2004-07-11  2:48 ` IRQ issues, (nobody cared, disabled), not USB Len Brown
2004-07-12 14:43   ` Christopher Swingley [this message]
2004-07-08 15:53 Christopher Swingley
2004-07-09  5:05 ` Andrew Morton
2004-07-09 15:32   ` Christopher Swingley
2004-07-11  8:39   ` Ville Herva
2004-07-13 10:49     ` Ville Herva
2004-07-12 14:38   ` Christopher Swingley

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=20040712144318.GB2113@iarc.uaf.edu \
    --to=cswingle@iarc.uaf.edu \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.