pci 0000:00:1f.0: BAR 13: [io 0x0800-0x087f] has bogus alignment

[dino99]

Journalctl have logged that error

kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 05] add_size 1000
kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 05] add_size 400000
kernel: pci 0000:00:1f.0: BAR 13: [io 0x0800-0x087f] has bogus alignment
kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 400000
kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xc0100000-0xc04fffff]
kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-7-generic 3.19.0-7.7
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: oem 1650 F.... pulseaudio
 /dev/snd/pcmC0D0p: oem 1650 F...m pulseaudio
 /dev/snd/controlC0: oem 1650 F.... pulseaudio
CurrentDesktop: GNOME
Date: Tue Mar 10 07:55:57 2015
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 eth1 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc3-vivid/

[dino99 (9d9)]

I have not seen that error logged with 3.19.0.6
Looks like this happened with the many systemd changes the past days, even if i was already booting with systemd-sysv since a while.
It seems to be a race with the faulty address (maybe 2 processes try to use it at the same time)
So is it a kernel issue per se ? not sure at first glance.

[dino99 (9d9)]

Have also tested the latest upstream: get the same issue

but that faulty address is refering to an old known error reported many times since kernel 3 family:
 kernel: pci 0000:00:1f.0: can't claim BAR 13 [io 0x0800-0x087f]: address conflict with ACPI CPU throttle [io 0x0810-0x0815]

https://bugs.freedesktop.org/attachment.cgi?id=113465
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1353916
and many others; its an upstream issue (some suggest that hpsa driver could be blamed)

[dino99 (9d9)]

kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
kernel: ACPI Warning: SystemIO range 0x000004b0-0x000004bf conflicts with OpRegion 0x00000480-0x000004bf (\_SB_.PCI0.SBRG.GPIO) (20141107/utaddress-258)
kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
kernel: ACPI Warning: SystemIO range 0x00000480-0x000004af conflicts with OpRegion 0x00000480-0x000004bf (\_SB_.PCI0.SBRG.GPIO) (20141107/utaddress-258)
kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich

[penalvch (penalvch)]

dino99, could you please advise what specific usability impact this issue has, if any?

As well, did this issue not occur in a release prior to Vivid?

[dino99 (9d9)]

@Christopher

- this is quite old as it appear around the HAL drop and kernel moving from 2 family to 3, so you confirm you does not read #5
- the system is able to get around that issue, reallocating a new address as the first checked is faulty
- so known trouble for user, only this mess

So the solution, maybe, is to blacklist that address for the booting process

[penalvch (penalvch)]

dino, just to clarify, you personally did not experience this on a 2.x series kernel (not someone else on some other report)?

[dino99 (9d9)]

@#10
never seen that issue when kernel 2 family was used with the current stock ubuntu

[penalvch (penalvch)]

dino99, the next step is to fully commit bisect from kernel 2 to 3.19 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[herauthon (herauthon)]

My dmesg for : Linux optiplex 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) i686 GNU/Linux

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.16.0-4-686-pae (<email address hidden>) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000017feffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000017ff0000-0x0000000017ff2fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000017ff3000-0x0000000017ffffff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffff0000-0x00000000ffffffff] reserved
[ 0.000000] Notice: NX (Execute Disable) protection missing in CPU!
[ 0.000000] SMBIOS 2.3 present.
[ 0.000000] DMI: VIA Technologies, Inc. KT333-8235/KT333-8235, BIOS 6.00 PG 08/19/2002
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x17ff0 max_arch_pfn = 0x1000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-AFFFF uncachable
[ 0.000000] B0000-BFFFF write-combining
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-DFFFF uncachable
[ 0.000000] E0000-EFFFF write-protect
[ 0.000000] F0000-FFFFF uncachable
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask FF0000000 write-back
[ 0.000000] 1 base 010000000 mask FF8000000 write-back
[ 0.000000] 2 base 0E0000000 mask FFC000000 write-combining
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 base 0E0000000 mask FFC000000 write-combining
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] found SMP MP-table at [mem 0x000f4df0-0x000f4dff] mapped at [c00f4df0]
[ 0.000000] initial memory mapped: [mem 0x00000000-0x01bfffff]
[ 0.000000] Base memory trampoline at [c009b000] 9b000 size 16384
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x17c00000-0x17dfffff]
[ 0.000000] [mem 0x17c00000-0x17dfffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x14000000-0x17bfffff]
[ 0.000000] [mem 0x14000000-0x17bfffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0x13ffffff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0x13ffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x17e00000-0x17feffff]
[ 0.000000] [mem 0x17e00000-0x17feffff] p...

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]