public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: regression, 2.6.26-rc7, pnp: quirk_system_pci_resources()
Date: Sun, 22 Jun 2008 00:54:53 +0200	[thread overview]
Message-ID: <485D86BD.5050803@keyaccess.nl> (raw)
In-Reply-To: <485D356A.402@keyaccess.nl>

On 21-06-08 19:07, Rene Herman wrote:

> On 21-06-08 04:12, Rene Herman wrote:
> 
>> I have been running with pnpacpi=off due to testing ISAPnP/PnPBIOS but 
>> when testing some other ACPI related problem tonight I removed that 
>> and found that unfortunately something seems to have regressed. My 
>> soundcard driver (snd-es1968) won't load anymore on current mainline:
>>
>> ===
>> ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 10 (level, 
>> low) -> IRQ 10
>> PCI: Unable to reserve I/O region #1:100@de00 for device 0000:00:0a.0
>> ACPI: PCI interrupt for device 0000:00:0a.0 disabled
>> ES1968 (ESS Maestro): probe of 0000:00:0a.0 failed with error -16
>> ===
>>
>> 00:01 (PNP0c02) is keeping its I/O region occupied:
>>
>> ===
>> # cat /sys/bus/pnp/devices/00\:01/resources
>> state = active
>> io 0xde00-0xde03
>> ===
>>
>> Sound used to work back when I wasn't yet booting with pnpacpi=off but 
>> I don't quite recall when I started doing that nor have I looked yet 
>> at why quirk_system_pci_resources() isn't doing its job. I'll 
>> investigate if you need me to but thought I'd first throw a heap of 
>> information your way and hope you'll have a patch for me when I wake 
>> up :-/
> 
> Well, why the quirk wasn't helping is fairly obvious -- but given that I 
> definitely didn't need anything like this on .25 I wonder why PnPACPI is 
> all of a sudden claiming those 4 ports in the first place.
> 
> As in, this works for me and might not be bogus due to the symmetry and 
> all but still needs some head scratching. In any case, I do definitely 
> need something for .26...
> 
> I'll go recompile .25 onto here and see if's just my BIOS being funny or 
> something to do with the kernel.
> 
> Signed-off-by: Rene Herman <rene.herman@gmail.com>

My BIOS is being funny. I all of a sudden have the same behaviour back 
on .25 and .24. Quite frankly, I haven't a single clue what's going on 
and why my BIOS is grabbing 0xde00-0xde03. The BIOS didn't change, it's 
BIOS SETTINGS didn't change. I did remove the soundcard, booted without 
it and put it back later (same slot) which may have triggered some odd 
BIOS reconfig. Already tried resetting the ESCD which isn't making a 
difference.

You'll have to decide if the patch as posted in parent makes sense. I 
guess it's not a kernel regression as such after all, but I do still 
need something like it to have my soundcard functional.

Rene.

  reply	other threads:[~2008-06-21 22:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-21  2:12 regression, 2.6.26-rc7, pnp: quirk_system_pci_resources() Rene Herman
2008-06-21 17:07 ` [PATCH] " Rene Herman
2008-06-21 22:54   ` Rene Herman [this message]
2008-06-24 15:17     ` Bjorn Helgaas
2008-06-25 18:08       ` Rene Herman

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=485D86BD.5050803@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=bjorn.helgaas@hp.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