linux-kernel - lock-up on boot with x86/PCI/ACPI: Use common interface to support PCI host bridge

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: <563DAE9A.5050904@internode.on.net>
Date:	Sat, 7 Nov 2015 18:26:10 +1030
From:	Arthur Marsh <arthur.marsh@...ernode.on.net>
To:	Jiang Liu <jiang.liu@...ux.intel.com>
Cc:	Hanjun Guo <hanjun.guo@...aro.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: lock-up on boot with x86/PCI/ACPI: Use common interface to support
 PCI host bridge

Hi, I've run into a situation where I've been getting a lock-up a few 
seconds into the boot process on a machine with an ASUS A8V-MX 
motherboard, BIOS 0503    12/06/2005 with AMD Athlon(tm) 64 Processor 
3200+ (single core) with kernel compiled in 32 bit mode (config attached 
was used for both the problem kernel and kernel with the patch reverted, 
dmesg attached was for the kernel with the patch reverted).

A git bisect traced the problem back to:

git bisect good
4d6b4e69a245e9df4b84dba387596086cb66887d is the first bad commit
commit 4d6b4e69a245e9df4b84dba387596086cb66887d
Author: Jiang Liu <jiang.liu@...ux.intel.com>
Date:   Wed Oct 14 14:29:41 2015 +0800

      x86/PCI/ACPI: Use common interface to support PCI host bridge

      Use common interface to simplify ACPI PCI host bridge implementation.

      Signed-off-by: Jiang Liu <jiang.liu@...ux.intel.com>
      Reviewed-by: Hanjun Guo <hanjun.guo@...aro.org>
      Acked-by: Bjorn Helgaas <bhelgaas@...gle.com>
      Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>

:040000 040000 a3447eea376b5a3e6f57deb35cf064c5481b45e3 
f64d8e49fd87b776933dfa3dfefcb33509004d3f M      arch

 From the boot-up I get the message as shown in the images at: 
http://www.users.on.net/~arthur.marsh/20151107601.jpg and
http://www.users.on.net/~arthur.marsh/20151107602.jpg

The boot-up suggests trying rebooting with pci=alloc but that didn't help.

The errors shown include
"BAR 0: trying firmware assignment [io  size 0x0020]"
"BAR 0: [io  size 0x0020] conflicts with PCI Bus #00 [io  0x0000-0xffff]
"BAR 0: failed to assign [io  size 0x0020]

After reverting the patch and installing the resulting kernel I was able 
to boot normally.

I'd be happy to provide any further information and run further tests to 
help identify and resolve the proble.

Arthur.

View attachment "20151107reverted-dmesg.txt" of type "text/plain" (53116 bytes)

View attachment "20151107reverted-config.txt" of type "text/plain" (61367 bytes)