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]
Message-ID: <alpine.LFD.2.01.0908050931390.3390@localhost.localdomain>
Date:	Wed, 5 Aug 2009 09:38:52 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Manuel Lauss <mano@...rinelk.homelinux.net>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Matthew Wilcox <willy@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andrew Patterson <andrew.patterson@...com>
Subject: Re: [Regression] PCI resources allocation problem on HP nx6325



On Wed, 5 Aug 2009, Linus Torvalds wrote:
> 
> So I think I understand the behavior on your box, and the warning was 
> actually correct and useful - our PCI layer is being stupid. We should 
> mark ROM resources as being prefetchable.
> 
> Hmm.. We do seem to _try_ do exactly that in pci_read_bases(). I wonder 
> what I'm missing, and where that bit is then cleared. Or whether we're 
> doing that ROM BAR probe somewhere else too..

Manuel, could you compile your kernel with CONFIG_PCI_DEBUG enabled, and
then boot it with "pci=earlydump", and send me the dmesg of a kernel boot? 

You may need to make sure that CONFIG_LOG_BUF_SHIFT is big enough to get 
it all, and perhaps use "dmesg -s 1000000" (some versions of dmesg will 
truncate the result to 64kB or something by default, and depending on just 
how verbose your boot ends up being, you migth lose things).

			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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ