linux-kernel - Re: [Broken] PCI: clean up resource alignment management

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.1.10.0804221020470.2779@woody.linux-foundation.org>
Date:	Tue, 22 Apr 2008 10:25:34 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jeff Chua <jeff.chua.linux@...il.com>
cc:	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Greg KH <gregkh@...e.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Broken] PCI: clean up resource alignment management



On Wed, 23 Apr 2008, Jeff Chua wrote:
> 
> I'm having problem loading pccard (Sony PC300 broadband card) with the
> recent git download, and bisected down to this commit.
> 
> commit 884525655d07fdee9245716b998ecdc45cdd8007
> Author: Ivan Kokshaysky <ink@...assic.park.msu.ru>
> Date:   Sun Mar 30 19:50:14 2008 +0400
> 
>     PCI: clean up resource alignment management

Ok, at worst we'll have to revert it, but before doing that, can you set 
up a bugzilla entry with a before-and-after version of "lspci -vv", full 
dmesg, and the output of /proc/iomem and /proc/ioports?

> The symptom that I'm seeing is ...
> 
> yenta_cardbus 0000:15:00.0: device not available because of BAR 7 [100:1ff] collisions
> yenta_cardbus: probe of 0000:15:00.0 failed with error -16

I suspect there wasn't a _real_ collision there, but the allocation failed 
because of the alignment bits not being set up right for cardbus bridges, 
but I'm not seeing the bug right now.

Ivan?

			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/