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
| ||
|
Date: Wed, 19 Feb 2014 09:11:47 +0000 From: Steven Newbury <steve@...wbury.org.uk> To: "Rafael J. Wysocki" <rjw@...ysocki.net> Cc: Yinghai Lu <yinghai@...nel.org>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: pci-3.14 resource alloc On Tue, 2014-02-18 at 23:29 +0100, Rafael J. Wysocki wrote: > On Tuesday, February 18, 2014 10:52:54 AM Yinghai Lu wrote: > > On Tue, Feb 18, 2014 at 2:08 AM, Steven Newbury <steve@...wbury.org.uk> wrote: > > >> > > > >> > There's no pci bridge/bus hotplug though. Docking doesn't reveal the > > >> > pci-e->pci bridge or the (radeon) devices on the other side. > > >> > > >> oh, no. could be other regression in linus tree or pci/next. > > >> > > > > > > Previously I needed the busn work to get it working, this was included > > > in the resource-alloc branch. It never worked on mainline, the bridge > > > used to show up but never get scanned. Now it's not showing up at all > > > on hotplug. It could be a dock driver regression. > > > > I had the busn_res_alloc patches in the branch. > > > > There is some changes about acpi dock driver from Rafael in recent > > kernels. Maybe Rafael could suggest which commit could cause problem, > > then you could try revert them on top of branch. > > I kind of suspect what might have caused them, but that particular thing > would not be easy to revert. > > Steven, what was the last kernel in which the bridge showed up? > > Did you test 3.14-rc3? > > Rafael > I'll try a few different kernels today and see when it last worked. I hadn't updated the machine since some 3.12-rc + my local patches so I've no idea at the moment when it stopped working... -- 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/
Powered by blists - more mailing lists