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 <[email protected]>
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 <[email protected]>
Reviewed-by: Hanjun Guo <[email protected]>
Acked-by: Bjorn Helgaas <[email protected]>
Signed-off-by: Rafael J. Wysocki <[email protected]>
: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.
On 2015/11/7 15:56, Arthur Marsh wrote:
> 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 <[email protected]>
> 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 <[email protected]>
> Reviewed-by: Hanjun Guo <[email protected]>
> Acked-by: Bjorn Helgaas <[email protected]>
> Signed-off-by: Rafael J. Wysocki <[email protected]>
>
> :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.
Hi Arthur,
Sorry for the regression. Could you please also help to
provide the ACPI tables from the affected system? You may get
ACPI tables by installing acpidump and then 'acpidump > acpitables.bin'.
Thanks,
Gerry
>
> Arthur.
>
>
Jiang Liu wrote on 08/11/15 23:33:
> On 2015/11/7 15:56, Arthur Marsh wrote:
>> 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 <[email protected]>
>> 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 <[email protected]>
>> Reviewed-by: Hanjun Guo <[email protected]>
>> Acked-by: Bjorn Helgaas <[email protected]>
>> Signed-off-by: Rafael J. Wysocki <[email protected]>
>>
>> :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.
> Hi Arthur,
> Sorry for the regression. Could you please also help to
> provide the ACPI tables from the affected system? You may get
> ACPI tables by installing acpidump and then 'acpidump > acpitables.bin'.
> Thanks,
> Gerry
Done!
Arthur.
On 2015/11/7 15:56, Arthur Marsh wrote:
> 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 <[email protected]>
> 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 <[email protected]>
> Reviewed-by: Hanjun Guo <[email protected]>
> Acked-by: Bjorn Helgaas <[email protected]>
> Signed-off-by: Rafael J. Wysocki <[email protected]>
>
> :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.
Hi Arthur,
Could you please help to try the attached test patch?
Thanks,
Gerry
>
> Arthur.
>
>
Jiang Liu wrote on 09/11/15 18:22:
> Hi Arthur,
> Could you please help to try the attached test patch?
> Thanks,
> Gerry
>
Thanks, I applied the patch, rebuilt and installed the resulting kernel
and it booted fine.
dmesg output from booting with this patch applied attached.
Arthur.
