linux-kernel - Re: post 2.6.26 requires pciehp_slot_with

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 24 Jul 2008 23:51:27 +0200
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org
Subject: Re: post 2.6.26 requires pciehp_slot_with_bus

On Thu, 24 Jul 2008 14:07:18 -0700
Jesse Barnes <jbarnes@...tuousgeek.org> wrote:

> On Thursday, July 24, 2008 1:39 pm Pierre Ossman wrote:
> >
> > This is a laptop with a single expressport that worked fine up until
> > this merge window. What changed and why is it no longer possible to
> > support this hardware without a kernel parameter?
> 
> Yeah we're being a bit more careful about registering hotplug slots these 
> days.  The fact that you got a conflict message indicates that more than one 
> driver is trying to bind to that PCIe port and handle hotplug for it.  I 
> guess acpiphp must already be loaded?
> 

Nope. Only pciehp is builtin, and acpiphp is not loaded. Anything
non-hotplug related that can block stuff?

Anyway, the port seems to work even with that warning present though
(sorry for not testing that properly earlier). Stray warnings is still
not pleasant though, so I can do some more testing if you have some
ideas.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)