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]
Date:	Thu, 15 Mar 2007 11:06:47 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Francis Moreau" <francis.moro@...il.com>
Cc:	linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>
Subject: Re: PCI probing failure in 2.6.21-rc3

> On Wed, 14 Mar 2007 09:47:42 +0100 "Francis Moreau" <francis.moro@...il.com> wrote:
> I already posted this issue but it was on a 2.6.19.7 kernel
> (2.6.19-1.2911.6.5.fc6 to be accurate). So it doesn't seem to be a
> regression.
> 
> During boot the console shows up this:
> 
> [...]
> PCI: Probing PCI hardware (bus 00)
> PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
> PCI quirk: region 1180-11bf claimed by ICH6 GPIO
> 0000:00:1f.2: trying to change BAR0 from 0000 to 01F0
> 0000:00:1f.2: trying to change BAR1 from 0000 to 03F4
> 0000:00:1f.2: trying to change BAR2 from 0000 to 0170
> 0000:00:1f.2: trying to change BAR3 from 0000 to 0374
> Boot video device is 0000:01:00.0
> PCI: Transparent bridge - 0000:00:1e.0
> PCI: Bus #07 (-#0a) is hidden behind transparent bridge #06 (-#07)
> (try 'pci=assign-busses')
> Please report the result to linux-kernel to fix this permanently
> [...]
> 
> I haven't time to test 'pci=assign-busses' option, I'll do it later,
> but I wanted to report this ASAP.

Greg, could we please either 

a) start doing something about these reports or
b) publish sufficient info to permit others to do something about these
   reports or 
c) remove the printk?

Thanks.
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ