public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Panin <pazke@orbita.don.sitek.net>
To: Brian Gerst <bgerst@didntduck.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IRQ conflicts
Date: Tue, 13 Feb 2001 12:44:00 +0300	[thread overview]
Message-ID: <20010213124400.A1860@debian> (raw)
In-Reply-To: <E14RfhV-0002A1-00@the-village.bc.nu> <3A85D79C.3DE3A527@didntduck.org>
In-Reply-To: <3A85D79C.3DE3A527@didntduck.org>; from bgerst@didntduck.org on Sat, Feb 10, 2001 at 07:06:52PM -0500

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

On Sat, Feb 10, 2001 at 07:06:52PM -0500, Brian Gerst wrote:
> Alan Cox wrote:
> > 
> > > <SoundBlaster EMU8000 (RAM2048k)>
> > > ACPI: Core Subsystem version [20010208]
> > > ACPI: SCI (IRQ9) allocation failed
> > > ACPI: Subsystem enable failed
> > > Trying to free free IRQ9
> > 
> > That seems to indicate acpi is freeing a free irq. Turn ACPI off. Its a
> > good bet it will fix any random irq/driver problem right now
> 
> Looking at this a bit further, I realised that when the sound driver was
> compiled in the kernel, it is initialised before ACPI.  The BIOS has
> assigned IRQ9 to ACPI, but the PCI code does not know this because of:
> 
> PCI: 00:07.3: class 604 doesn't match header type 00. Ignoring class. 
> 
> The ISAPnP code then assigns IRQ9 to the sound card, causing the ACPI
> code to fail to allocate it.  If I compile sound as a module then the
> ACPI driver grabs IRQ9 and the sound get IRQ7.
> 

Hi Brian,

please test this patch with ACPI enabled and sound driver compiled in kernel.
IMHO it should fix this problem.

Best regards.

-- 
Andrey Panin            | Embedded systems software engineer
pazke@orbita1.ru        | PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-02-13  9:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-10 16:55 IRQ conflicts Brian Gerst
2001-02-10 17:26 ` Brian Gerst
2001-02-10 19:28   ` Alan Cox
2001-02-11  0:06     ` Brian Gerst
2001-02-13  9:44       ` Andrey Panin [this message]
2001-02-13  9:52         ` Andrey Panin
2001-02-13 22:51           ` Brian Gerst
  -- strict thread matches above, loose matches on Subject: below --
2001-06-05  7:56 753 user
2001-06-05 12:52 753 user
2001-06-05 17:22 ` Alan Cox

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=20010213124400.A1860@debian \
    --to=pazke@orbita.don.sitek.net \
    --cc=bgerst@didntduck.org \
    --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