linux-kernel - Re: PCI resources allocation problem on Toshiba Satellite A40

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.01.0908131843200.3162@localhost.localdomain>
Date:	Thu, 13 Aug 2009 18:47:40 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Frans Pop <elendil@...net.nl>
cc:	mano@...rinelk.homelinux.net, rjw@...k.pl, willy@...ux.intel.com,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	akpm@...ux-foundation.org, andrew.patterson@...com
Subject: Re: PCI resources allocation problem on Toshiba Satellite A40



On Fri, 14 Aug 2009, Frans Pop wrote:
> 
> The commit that resulted in the messages disappearing was:
> commit a76117dfd687ec4be0a9a05214f3009cc5f73a42
> Author: Matthew Wilcox <willy@...ux.intel.com>
> Date:   Wed Jun 17 16:33:35 2009 -0400
>     x86: Use pci_claim_resource
> 
> The commit that caused the messages to return is:
> commit 79896cf42f6a96d7e14f2dc3473443d68d74031d
> Author: Linus Torvalds <torvalds@...ux-foundation.org>
> Date:   Sun Aug 2 14:04:19 2009 -0700
>     Make pci_claim_resource() use request_resource() rather than insert_resource()
> 
> The affected devices are the two USB UHCI controllers.

Ok, it's the same behavior that mano had, but since the warning didn't go 
away with the trial patch, it's not exactly the same situation.

Can you send

 - output of /proc/ioports both with the current kernel (or the 2.6.30 
   kernel - they should be identical) and with one of the kernels in 
   between that didn't warn

 - send the full bootup dmesg with CONFIG_PCI_DEBUG enabled

and we can probably figure it out.

That said, since it's not a regression, I'm not going to _do_ anything 
about it until after 2.6.31, but I might have a test-patch for you to try 
ot something.

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/