public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: sean <seandarcy@hotmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: irq 16 : Nobody cared  - alsa v. io-apic in 2.6.5-rc3-bk2
Date: Fri, 02 Apr 2004 19:34:47 -0500	[thread overview]
Message-ID: <406E06A7.1000003@hotmail.com> (raw)
In-Reply-To: <1080897252.30361.147.camel@dhcppc4>

Len Brown wrote:
> On Thu, 2004-04-01 at 14:24, sean wrote:
> 
>>I have a VIA k400 motherboard.
>>
> 
> 
>>irq 16: nobody cared!
>>Call Trace:
>>  [<c0108508>] __report_bad_irq+0x28/0x80
........................
>>handlers:
>>[<c0395800>] (snd_cmipci_interrupt+0x0/0x130)
>>Disabling IRQ #16
>>..............

> 
> Does acpi=off make a difference and change how /proc/interrupts looks?
> 
> If yes, can you try the latest ACPI code that 2.6.5 is missing?
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.5/
> 
> thanks,
> -Len

Correct on all counts. acpi=off changed how /proc/interrupts looked.

Plain rc3-bk2:

cat /proc/interrupts
            CPU0
   0:   24465969    IO-APIC-edge  timer
   1:       3894    IO-APIC-edge  i8042
   2:          0          XT-PIC  cascade
   8:          1    IO-APIC-edge  rtc
   9:          0   IO-APIC-level  acpi
  11:          0    IO-APIC-edge  ohci1394, radeon@PCI:1:0:0
  12:     208554    IO-APIC-edge  i8042
  14:     484633    IO-APIC-edge  ide0
  15:         24    IO-APIC-edge  ide1
  16:     100000   IO-APIC-level  CMI8738-MC6
  18:      96443   IO-APIC-level  eth1
  21:          0   IO-APIC-level  ehci_hcd, uhci_hcd, uhci_hcd, uhci_hcd

With acpi=off:

cat /proc/interrupts
            CPU0
   0:     411879    IO-APIC-edge  timer
   1:       1037    IO-APIC-edge  i8042
   2:          0          XT-PIC  cascade
   8:          1    IO-APIC-edge  rtc
  12:      15358    IO-APIC-edge  i8042
  14:      13668    IO-APIC-edge  ide0
  15:         24    IO-APIC-edge  ide1
  16:      21258   IO-APIC-level  ohci1394, CMI8738-MC6, radeon@PCI:1:0:0
  18:        404   IO-APIC-level  eth1
  21:          0   IO-APIC-level  ehci_hcd, uhci_hcd, uhci_hcd, uhci_hcd


And the patch worked.

With the patch:

cat /proc/interrupts
            CPU0
   0:     138277    IO-APIC-edge  timer
   1:        942    IO-APIC-edge  i8042
   2:          0          XT-PIC  cascade
   8:          1    IO-APIC-edge  rtc
   9:          0   IO-APIC-level  acpi
  12:        918    IO-APIC-edge  i8042
  14:      11189    IO-APIC-edge  ide0
  15:         24    IO-APIC-edge  ide1
  16:       7731   IO-APIC-level  ohci1394, CMI8738-MC6, radeon@PCI:1:0:0
  18:        177   IO-APIC-level  eth1
  21:          0   IO-APIC-level  ehci_hcd, uhci_hcd, uhci_hcd, uhci_hcd


Thanks for all your help. When should we see the patch in the kernel?

sean


  reply	other threads:[~2004-04-03  0:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615F7212@hdsmsx402.hd.intel.com>
2004-04-02  9:14 ` irq 16 : Nobody cared - alsa v. io-apic in 2.6.5-rc3-bk2 Len Brown
2004-04-03  0:34   ` sean [this message]
2004-04-03  1:16     ` Len Brown
2004-04-01 19:24 sean

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=406E06A7.1000003@hotmail.com \
    --to=seandarcy@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox