public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: avuton@gmail.com, yakui.zhao@intel.com, shaohua.li@intel.com,
	bjorn.helgaas@hp.com, trenn@suse.de,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org
Subject: Re: a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0 sound card
Date: Thu, 31 Jan 2008 14:58:20 -0800	[thread overview]
Message-ID: <20080131145820.44171af2.akpm@linux-foundation.org> (raw)
In-Reply-To: <479CCAAD.4080706@shaw.ca>

On Sun, 27 Jan 2008 12:17:17 -0600
Robert Hancock <hancockr@shaw.ca> wrote:

> Avuton Olrich wrote:
> > With v2.6.24 my second ALSA sound device stopped working.
> > 
> > After bisection it says this was the offending commit.
> > 
> > a7839e960675b549f06209d18283d5cee2ce9261 is first bad commit
> > commit a7839e960675b549f06209d18283d5cee2ce9261
> > Author: Zhao Yakui <yakui.zhao@intel.com>
> > Date:   Wed Nov 28 16:21:21 2007 -0800
> > 
> >     PNP: increase the maximum number of resources
> > 
> >     On some systems the number of resources(IO,MEM) returnedy by PNP device is
> >     greater than the PNP constant, for example motherboard devices.  It brings
> >     that some resources can't be reserved and resource confilicts.  This will
> >     cause PCI resources are assigned wrongly in some systems, and cause hang.
> >     This is a regression since we deleted ACPI motherboard driver and use PNP
> >     system driver.
> > 
> >     [akpm@linux-foundation.org: fix text and coding-style a bit]
> >     Signed-off-by: Li Shaohua <shaohua.li@intel.com>
> >     Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
> >     Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
> >     Cc: Thomas Renninger <trenn@suse.de>
> >     Cc: <stable@kernel.org>
> >     Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> >     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> > 
> > The audio device is 00:1b.0 (see my lspci -vvv output), the other
> > audio device works fine.
> > 
> > http://avuton.googlepages.com/v2.6-before (dmesg revision before)
> > http://avuton.googlepages.com/v2.6-after (dmesg broken revision)
> > http://avuton.googlepages.com/lspci-vvv
> > http://avuton.googlepages.com/config (from the broken revision)
> > http://avuton.googlepages.com/iomem
> > http://avuton.googlepages.com/ioports

I don't think anything has happened yet on this?

> Here's why the driver fails to load:
> 
> [   31.133060] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, 
> low) -> IRQ 22
> [   31.133141] PCI: Unable to reserve mem region #1:4000@febf8000 for 
> device 0000:00:1b.0
> [   31.133197] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> [   31.133244] HDA Intel: probe of 0000:00:1b.0 failed with error -16
> 
> The iomem location of the HDA controller conflicts with this reservation 
> by the BIOS:
> 
> [   22.906654] system 00:08: iomem range 0xfebfa000-0xfebfac00 has been 
> reserved
> 
> There was a patch floating around to ignore PnPACPI reservations which 
> conflict with PCI BARs, which appears to be what's happening in this 
> case. That patch originally worked for any board, but was later made 
> specific to a certain Supermicro motherboard which had the sata_nv 
> controller MMIO regions marked as reserved, preventing the driver from 
> loading. We may need a more general solution. See:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=313491

Thanks.  If we were to remove the supermicro-specificity, would this be a
sufficiently general solution?


  reply	other threads:[~2008-01-31 22:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.Kmpf0B4W44W1VefIME7+BnfUouY@ifi.uio.no>
2008-01-27 18:17 ` a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0 sound card Robert Hancock
2008-01-31 22:58   ` Andrew Morton [this message]
2008-02-01  0:14     ` Robert Hancock
2008-02-01  0:50       ` Linus Torvalds
2008-02-04 17:39         ` Bjorn Helgaas
2008-02-04 18:18           ` Linus Torvalds
2008-02-04 20:41             ` Bjorn Helgaas
2008-02-04 21:16               ` Linus Torvalds
2008-02-05  7:03                 ` Bjorn Helgaas
2008-02-05 16:46                   ` Avuton Olrich
2008-02-05 18:15                   ` Linus Torvalds
2008-02-05 20:12                     ` Bjorn Helgaas
2008-02-13 22:33                       ` Avuton Olrich
2008-02-14 18:51                       ` Bjorn Helgaas
2008-02-14 19:42                         ` Linus Torvalds
2008-02-14 20:07                           ` Bjorn Helgaas
2008-02-14 20:26                             ` Linus Torvalds
2008-02-14 21:01                               ` Bjorn Helgaas
2008-02-14 21:37                                 ` Linus Torvalds
2008-02-14 22:28                                   ` Bjorn Helgaas
2008-02-14 22:57                                     ` Linus Torvalds
2008-02-14 23:14                                       ` Linus Torvalds
2008-02-15  0:13                                         ` Bjorn Helgaas
2008-02-15  0:40                                           ` Linus Torvalds
2008-02-27 17:43                                             ` Bjorn Helgaas
2008-01-27 14:40 Avuton Olrich
2008-01-27 21:50 ` Linus Torvalds
2008-01-28  1:15   ` Shaohua Li

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=20080131145820.44171af2.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=avuton@gmail.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=trenn@suse.de \
    --cc=yakui.zhao@intel.com \
    /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