Bug#637659: Linux kernel: 2.6.32.42: (Debian Bug#637659): pci 0000:00:00.0: BAR 0: address space collision on of device
reopen 637659
quit
Dear Linux kernel and Debian folks,
with the longterm Linux kernel 2.6.32 I am getting the following error
pci 0000:00:00.0: BAR 0: address space collision on of device [0xc8000000-0xcfffffff]
It is already reported to the Debian BTS as report #613979 [2]. I hope
the following information will get you up to date regarding this issue
and hopefully you can help out.
Am Mittwoch, den 24.08.2011, 14:22 +0100 schrieb Ben Hutchings:
> On Wed, 2011-08-24 at 11:40 +0200, Paul Menzel wrote:
> > Am Mittwoch, den 24.08.2011, 03:53 +0100 schrieb Ben Hutchings:
> > > On Sat, 2011-08-13 at 16:27 +0200, Paul Menzel wrote:
[…]
> > > > with Linux kernel 2.6.32 the following message is shown on each boot.
> > > >
> > > > [ 0.206656] pci 0000:00:00.0: BAR 0: address space collision on of device [0xc8000000-0xcfffffff]
> > > >
> > > > Testing 3.0.0-1 this message is *not* shown, so it seems to have been
> > > > fixed in the meanwhile. There is a related Launchpad bug report (linked
> > > > from [1]) [2] indicating that the patch in the Linux patch queue [3]
> > > > fixes this issue.
> > > [...]
> > >
> > > This fix was included in longterm update 2.6.32.42 and will be in the
> > > next stable point release (Debian 6.0.3).
> >
> > Thank you for the information. So if it really is the patch from
> > Patchwork entry #39988 [3], then it should be the following commit
> > [4][5] in the changelog for Linux kernel 2.6.32.42 [6].
> >
> > commit d93bd2d1eda2105d8685792ea16f33dae6fd8abc
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > Date: Mon Nov 9 12:04:32 2009 -0800
> >
> > PCI: allow matching of prefetchable resources to non-prefetchable windows
> >
> > commit 8c8def26bfaa704db67d515da3eb92cf26067548 upstream.
> >
> > Is that correct?
>
> Right. Not sure it's exactly the same as the patch in Patchwork, but it
> is the version that ended up in later versions of Linux.
Upgrading yesterday to version 2.6.32-38 which includes longterm release
2.6.32.43, unfortunately I have to report that the problem has not been
fixed by the above patch. The following message is still shown.
[ 0.207342] pci 0000:00:00.0: BAR 0: address space collision on of device [0xc8000000-0xcfffffff]
I guess this error is somehow related to the problem I got with later
Linux versions [1] (Debian BTS: #613979 [2]). The problem seems to be
that »the system has a single HyperTransport I/O chain, but has two PCI
host bridges to buses 00 and 80.« [4].
Commit 29cf7a30 [3] addresses this issue for my board by adding a quirk.
commit 29cf7a30f8a0ce4af2406d93d5a332099be26923
Author: Paul Menzel <paulepanter@users.sourceforge.net>
Date: Wed Aug 31 17:07:10 2011 +0200
x86/PCI: use host bridge _CRS info on ASUS M2V-MX SE
Although with 2.6.32 loading snd-hda-intel does not crash.
Commit 2491762c [4] has more information regarding this issue.
x86/PCI: use host bridge _CRS info on ASRock ALiveSATA2-GLAN
This DMI quirk turns on "pci=use_crs" for the ALiveSATA2-GLAN because
amd_bus.c doesn't handle this system correctly.
The system has a single HyperTransport I/O chain, but has two PCI host
bridges to buses 00 and 80. amd_bus.c learns the MMIO range associated
with buses 00-ff and that this range is routed to the HT chain hosted at
node 0, link 0:
[…]
Unfortunately I do not have outputs from `dmesg` anywhere from older
Linux versions so I do not know when this problem started. I am pretty
sure though that they have not been there since the beginning.
I would try to avoid trying to bisect that again. I guess I can try to
also use the host bridge _CRS information with this Linux version by
adding `pci=use_crs` to the Linux kernel command line. Although I am not
sure that this is supported since `dmesg | grep -i crs` does not return
anything.
Bjorn, do you have an idea what commit could have caused this collision?
Furthermore it would be interesting if this address space collision can
cause any system freezes or if this is just “cosmetic”(?).
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-38) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Oct 3 05:45:56 UTC 2011
** Kernel log:
[ 1.969117] usb 3-2: New USB device found, idVendor=058f, idProduct=9254
[ 1.969121] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.969124] usb 3-2: Product: Generic USB Hub
[ 1.969126] usb 3-2: Manufacturer: ALCOR
[ 1.969225] usb 3-2: configuration #1 chosen from 1 choice
[ 1.972188] hub 3-2:1.0: USB hub found
[ 1.974114] hub 3-2:1.0: 4 ports detected
[ 20.292396] PM: Starting manual resume from disk
[ 20.292401] PM: Resume from partition 253:2
[ 20.292403] PM: Checking hibernation image.
[ 20.293266] PM: Error -22 checking image file
[ 20.293269] PM: Resume from disk failed.
[ 20.350212] kjournald starting. Commit interval 5 seconds
[ 20.350240] EXT3-fs: mounted filesystem with ordered data mode.
[ 21.974587] <30>udevd[474]: starting version 172
[ 22.657456] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[ 22.657470] ACPI: Sleep Button [SLPB]
[ 22.657544] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
[ 22.657548] ACPI: Power Button [PWRB]
[ 22.657621] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[ 22.657625] ACPI: Power Button [PWRF]
[ 22.671794] processor LNXCPU:00: registered as cooling_device0
[ 22.672085] processor LNXCPU:01: registered as cooling_device1
[ 22.757024] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 22.796647] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 22.946071] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
[ 23.075615] parport_pc 00:04: reported by Plug and Play ACPI
[ 23.075663] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[ 23.134115] EDAC MC: Ver: 2.1.0 Oct 3 2011
[ 23.449967] EDAC amd64_edac: Ver: 3.2.0 Oct 3 2011
[ 23.450650] EDAC amd64: ECC is enabled by BIOS.
[ 23.450689] EDAC MC: Rev F or later detected
[ 23.450755] EDAC MC0: Giving out device to 'amd64_edac' 'RevF': DEV 0000:00:18.2
[ 23.450786] EDAC PCI0: Giving out device to module 'amd64_edac' controller 'EDAC PCI controller': DEV '0000:00:18.2' (POLLED)
[ 23.801762] alloc irq_desc for 17 on node 0
[ 23.801766] alloc kstat_irqs on node 0
[ 23.801776] HDA Intel 0000:20:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 23.801859] HDA Intel 0000:20:01.0: setting latency timer to 64
[ 23.801864] HDA Intel 0000:20:01.0: PCI: Disallowing DAC for device
[ 23.882460] input: HDA Digital PCBeep as /devices/pci0000:20/0000:20:01.0/input/input5
[ 24.298713] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input6
[ 24.316775] ioctl32(fsck.ext3:847): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(ffca43d8) on /dev/dm-1
[ 24.316887] ioctl32(fsck.ext3:847): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(ffca43d8) on /dev/dm-1
[ 24.395101] EXT3 FS on dm-1, internal journal
[ 24.874632] loop: module loaded
[ 25.004438] kvm: Nested Virtualization enabled
[ 26.702781] Adding 4194296k swap on /dev/mapper/speicher-swap. Priority:-1 extents:1 across:4194296k
[ 26.715021] ioctl32(fsck.ext3:1090): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff5f5a8) on /dev/md0
[ 26.715476] ioctl32(fsck.ext3:1090): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff5f5a8) on /dev/md0
[ 26.785895] ioctl32(fsck.ext3:1093): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff90f78) on /dev/dm-6
[ 26.821972] ioctl32(fsck.ext3:1093): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff90f78) on /dev/dm-6
[ 27.369764] ioctl32(fsck.ext3:1098): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff5e848) on /dev/dm-3
[ 27.389020] ioctl32(fsck.ext3:1098): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff5e848) on /dev/dm-3
[ 27.889114] ioctl32(fsck.ext3:1102): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(ffad6cc8) on /dev/dm-4
[ 27.924852] ioctl32(fsck.ext3:1102): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(ffad6cc8) on /dev/dm-4
[ 28.600283] fuse init (API version 7.13)
[ 28.812319] kjournald starting. Commit interval 5 seconds
[ 28.844426] EXT3 FS on md0, internal journal
[ 28.844431] EXT3-fs: mounted filesystem with ordered data mode.
[ 29.119131] kjournald starting. Commit interval 5 seconds
[ 29.194923] EXT3 FS on dm-6, internal journal
[ 29.194931] EXT3-fs: mounted filesystem with ordered data mode.
[ 29.313414] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 29.314965] SGI XFS Quota Management subsystem
[ 29.406078] XFS mounting filesystem dm-7
[ 29.732665] Ending clean XFS mount for filesystem: dm-7
[ 29.944405] XFS mounting filesystem dm-8
[ 30.210437] Ending clean XFS mount for filesystem: dm-8
[ 30.300263] REISERFS (device dm-5): found reiserfs format "3.6" with standard journal
[ 30.300304] REISERFS (device dm-5): using ordered data mode
[ 30.307728] REISERFS (device dm-5): journal params: device dm-5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[ 30.309347] REISERFS (device dm-5): checking transaction log (dm-5)
[ 30.341246] REISERFS (device dm-5): Using r5 hash to sort names
[ 30.413826] kjournald starting. Commit interval 5 seconds
[ 30.414410] EXT3 FS on dm-3, internal journal
[ 30.414417] EXT3-fs: mounted filesystem with ordered data mode.
[ 30.446499] kjournald starting. Commit interval 5 seconds
[ 30.446798] EXT3 FS on dm-4, internal journal
[ 30.446804] EXT3-fs: mounted filesystem with ordered data mode.
[ 35.360686] powernow-k8: Found 1 AMD Athlon(tm) X2 Dual Core Processor BE-2350 processors (2 cpu cores) (version 2.20.00)
[ 35.360745] powernow-k8: 0 : fid 0xd (2100 MHz), vid 0xe
[ 35.360748] powernow-k8: 1 : fid 0xc (2000 MHz), vid 0xf
[ 35.360750] powernow-k8: 2 : fid 0xa (1800 MHz), vid 0x11
[ 35.360753] powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x16
[ 36.004024] Clocksource tsc unstable (delta = -261871484 ns)
[ 69.750801] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 71.392312] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 71.845650] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 78.671648] [drm] Initialized drm 1.1.0 20060810
[ 78.869715] alloc irq_desc for 16 on node 0
[ 78.869723] alloc kstat_irqs on node 0
[ 78.869746] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 78.871097] [drm] Initialized via 2.11.1 20070202 for 0000:01:00.0 on minor 0
[ 78.871744] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0106407){t:'d';sz:16} arg(ff82b200) on /dev/dri/card0
[ 78.871790] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0106407){t:'d';sz:16} arg(ff82b200) on /dev/dri/card0
[ 78.871807] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0086401){t:'d';sz:8} arg(ff82b1f8) on /dev/dri/card0
[ 78.946336] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0246400){t:'d';sz:36} arg(09b5df10) on /dev/dri/card0
[ 78.971230] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0246400){t:'d';sz:36} arg(09b5df10) on /dev/dri/card0
[ 80.344020] eth0: no IPv6 routers present
[ 193.434434] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 0304
board_vendor: ASUSTeK Computer INC.
board_name: M2V-MX SE
board_version: Rev x.xx
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] [1106:3230] (rev 11) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:8297]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (500ns min)
Interrupt: pin A routed to IRQ 16
Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
Region 1: Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at fbef0000 [disabled] [size=64K]
Capabilities: <access denied>
20:01.0 Audio device [0403]: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) [1106:3288] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8290]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fbffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: HDA Intel
** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c312 Logitech, Inc. DeLuxe 250 Keyboard
Bus 003 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.32-5-amd64 depends on:
ii debconf [debconf-2.0] 1.5.41
ii initramfs-tools [linux-initramfs-tool] 0.99
ii linux-base 3.3
ii module-init-tools 3.16-1
Versions of packages linux-image-2.6.32-5-amd64 recommends:
ii firmware-linux-free 3
ii libc6-i686 2.13-21
Versions of packages linux-image-2.6.32-5-amd64 suggests:
pn grub | lilo <none>
pn linux-doc-2.6.32 <none>
Versions of packages linux-image-2.6.32-5-amd64 is related to:
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
pn firmware-iwlwifi <none>
pn firmware-linux <none>
pn firmware-linux-nonfree <none>
pn firmware-qlogic <none>
pn firmware-ralink <none>
pn xen-hypervisor <none>
Bug#637659: Linux kernel: 2.6.32.42: (Debian Bug#637659): pci 0000:00:00.0: BAR 0: address space collision on of device
reopen 637659
quit
Dear Linux kernel and Debian folks,
with the longterm Linux kernel 2.6.32 I am getting the following error
pci 0000:00:00.0: BAR 0: address space collision on of device [0xc8000000-0xcfffffff]
It is already reported to the Debian BTS as report #613979 [2]. I hope
the following information will get you up to date regarding this issue
and hopefully you can help out.
Am Mittwoch, den 24.08.2011, 14:22 +0100 schrieb Ben Hutchings:
> On Wed, 2011-08-24 at 11:40 +0200, Paul Menzel wrote:
> > Am Mittwoch, den 24.08.2011, 03:53 +0100 schrieb Ben Hutchings:
> > > On Sat, 2011-08-13 at 16:27 +0200, Paul Menzel wrote:
[…]
> > > > with Linux kernel 2.6.32 the following message is shown on each boot.
> > > >
> > > > [ 0.206656] pci 0000:00:00.0: BAR 0: address space collision on of device [0xc8000000-0xcfffffff]
> > > >
> > > > Testing 3.0.0-1 this message is *not* shown, so it seems to have been
> > > > fixed in the meanwhile. There is a related Launchpad bug report (linked
> > > > from [1]) [2] indicating that the patch in the Linux patch queue [3]
> > > > fixes this issue.
> > > [...]
> > >
> > > This fix was included in longterm update 2.6.32.42 and will be in the
> > > next stable point release (Debian 6.0.3).
> >
> > Thank you for the information. So if it really is the patch from
> > Patchwork entry #39988 [3], then it should be the following commit
> > [4][5] in the changelog for Linux kernel 2.6.32.42 [6].
> >
> > commit d93bd2d1eda2105d8685792ea16f33dae6fd8abc
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > Date: Mon Nov 9 12:04:32 2009 -0800
> >
> > PCI: allow matching of prefetchable resources to non-prefetchable windows
> >
> > commit 8c8def26bfaa704db67d515da3eb92cf26067548 upstream.
> >
> > Is that correct?
>
> Right. Not sure it's exactly the same as the patch in Patchwork, but it
> is the version that ended up in later versions of Linux.
Upgrading yesterday to version 2.6.32-38 which includes longterm release
2.6.32.43, unfortunately I have to report that the problem has not been
fixed by the above patch. The following message is still shown.
[ 0.207342] pci 0000:00:00.0: BAR 0: address space collision on of device [0xc8000000-0xcfffffff]
I guess this error is somehow related to the problem I got with later
Linux versions [1] (Debian BTS: #613979 [2]). The problem seems to be
that »the system has a single HyperTransport I/O chain, but has two PCI
host bridges to buses 00 and 80.« [4].
Commit 29cf7a30 [3] addresses this issue for my board by adding a quirk.
commit 29cf7a30f8a0ce4af2406d93d5a332099be26923
Author: Paul Menzel <paulepanter@users.sourceforge.net>
Date: Wed Aug 31 17:07:10 2011 +0200
x86/PCI: use host bridge _CRS info on ASUS M2V-MX SE
Although with 2.6.32 loading snd-hda-intel does not crash.
Commit 2491762c [4] has more information regarding this issue.
x86/PCI: use host bridge _CRS info on ASRock ALiveSATA2-GLAN
This DMI quirk turns on "pci=use_crs" for the ALiveSATA2-GLAN because
amd_bus.c doesn't handle this system correctly.
The system has a single HyperTransport I/O chain, but has two PCI host
bridges to buses 00 and 80. amd_bus.c learns the MMIO range associated
with buses 00-ff and that this range is routed to the HT chain hosted at
node 0, link 0:
[…]
Unfortunately I do not have outputs from `dmesg` anywhere from older
Linux versions so I do not know when this problem started. I am pretty
sure though that they have not been there since the beginning.
I would try to avoid trying to bisect that again. I guess I can try to
also use the host bridge _CRS information with this Linux version by
adding `pci=use_crs` to the Linux kernel command line. Although I am not
sure that this is supported since `dmesg | grep -i crs` does not return
anything.
Bjorn, do you have an idea what commit could have caused this collision?
Furthermore it would be interesting if this address space collision can
cause any system freezes or if this is just “cosmetic”(?).
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-38) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Oct 3 05:45:56 UTC 2011
** Kernel log:
[ 1.969117] usb 3-2: New USB device found, idVendor=058f, idProduct=9254
[ 1.969121] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.969124] usb 3-2: Product: Generic USB Hub
[ 1.969126] usb 3-2: Manufacturer: ALCOR
[ 1.969225] usb 3-2: configuration #1 chosen from 1 choice
[ 1.972188] hub 3-2:1.0: USB hub found
[ 1.974114] hub 3-2:1.0: 4 ports detected
[ 20.292396] PM: Starting manual resume from disk
[ 20.292401] PM: Resume from partition 253:2
[ 20.292403] PM: Checking hibernation image.
[ 20.293266] PM: Error -22 checking image file
[ 20.293269] PM: Resume from disk failed.
[ 20.350212] kjournald starting. Commit interval 5 seconds
[ 20.350240] EXT3-fs: mounted filesystem with ordered data mode.
[ 21.974587] <30>udevd[474]: starting version 172
[ 22.657456] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[ 22.657470] ACPI: Sleep Button [SLPB]
[ 22.657544] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3
[ 22.657548] ACPI: Power Button [PWRB]
[ 22.657621] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[ 22.657625] ACPI: Power Button [PWRF]
[ 22.671794] processor LNXCPU:00: registered as cooling_device0
[ 22.672085] processor LNXCPU:01: registered as cooling_device1
[ 22.757024] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 22.796647] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 22.946071] k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
[ 23.075615] parport_pc 00:04: reported by Plug and Play ACPI
[ 23.075663] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[ 23.134115] EDAC MC: Ver: 2.1.0 Oct 3 2011
[ 23.449967] EDAC amd64_edac: Ver: 3.2.0 Oct 3 2011
[ 23.450650] EDAC amd64: ECC is enabled by BIOS.
[ 23.450689] EDAC MC: Rev F or later detected
[ 23.450755] EDAC MC0: Giving out device to 'amd64_edac' 'RevF': DEV 0000:00:18.2
[ 23.450786] EDAC PCI0: Giving out device to module 'amd64_edac' controller 'EDAC PCI controller': DEV '0000:00:18.2' (POLLED)
[ 23.801762] alloc irq_desc for 17 on node 0
[ 23.801766] alloc kstat_irqs on node 0
[ 23.801776] HDA Intel 0000:20:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 23.801859] HDA Intel 0000:20:01.0: setting latency timer to 64
[ 23.801864] HDA Intel 0000:20:01.0: PCI: Disallowing DAC for device
[ 23.882460] input: HDA Digital PCBeep as /devices/pci0000:20/0000:20:01.0/input/input5
[ 24.298713] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input6
[ 24.316775] ioctl32(fsck.ext3:847): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(ffca43d8) on /dev/dm-1
[ 24.316887] ioctl32(fsck.ext3:847): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(ffca43d8) on /dev/dm-1
[ 24.395101] EXT3 FS on dm-1, internal journal
[ 24.874632] loop: module loaded
[ 25.004438] kvm: Nested Virtualization enabled
[ 26.702781] Adding 4194296k swap on /dev/mapper/speicher-swap. Priority:-1 extents:1 across:4194296k
[ 26.715021] ioctl32(fsck.ext3:1090): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff5f5a8) on /dev/md0
[ 26.715476] ioctl32(fsck.ext3:1090): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff5f5a8) on /dev/md0
[ 26.785895] ioctl32(fsck.ext3:1093): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff90f78) on /dev/dm-6
[ 26.821972] ioctl32(fsck.ext3:1093): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff90f78) on /dev/dm-6
[ 27.369764] ioctl32(fsck.ext3:1098): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff5e848) on /dev/dm-3
[ 27.389020] ioctl32(fsck.ext3:1098): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(fff5e848) on /dev/dm-3
[ 27.889114] ioctl32(fsck.ext3:1102): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(ffad6cc8) on /dev/dm-4
[ 27.924852] ioctl32(fsck.ext3:1102): Unknown cmd fd(5) cmd(0000127c){t:12;sz:0} arg(ffad6cc8) on /dev/dm-4
[ 28.600283] fuse init (API version 7.13)
[ 28.812319] kjournald starting. Commit interval 5 seconds
[ 28.844426] EXT3 FS on md0, internal journal
[ 28.844431] EXT3-fs: mounted filesystem with ordered data mode.
[ 29.119131] kjournald starting. Commit interval 5 seconds
[ 29.194923] EXT3 FS on dm-6, internal journal
[ 29.194931] EXT3-fs: mounted filesystem with ordered data mode.
[ 29.313414] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 29.314965] SGI XFS Quota Management subsystem
[ 29.406078] XFS mounting filesystem dm-7
[ 29.732665] Ending clean XFS mount for filesystem: dm-7
[ 29.944405] XFS mounting filesystem dm-8
[ 30.210437] Ending clean XFS mount for filesystem: dm-8
[ 30.300263] REISERFS (device dm-5): found reiserfs format "3.6" with standard journal
[ 30.300304] REISERFS (device dm-5): using ordered data mode
[ 30.307728] REISERFS (device dm-5): journal params: device dm-5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[ 30.309347] REISERFS (device dm-5): checking transaction log (dm-5)
[ 30.341246] REISERFS (device dm-5): Using r5 hash to sort names
[ 30.413826] kjournald starting. Commit interval 5 seconds
[ 30.414410] EXT3 FS on dm-3, internal journal
[ 30.414417] EXT3-fs: mounted filesystem with ordered data mode.
[ 30.446499] kjournald starting. Commit interval 5 seconds
[ 30.446798] EXT3 FS on dm-4, internal journal
[ 30.446804] EXT3-fs: mounted filesystem with ordered data mode.
[ 35.360686] powernow-k8: Found 1 AMD Athlon(tm) X2 Dual Core Processor BE-2350 processors (2 cpu cores) (version 2.20.00)
[ 35.360745] powernow-k8: 0 : fid 0xd (2100 MHz), vid 0xe
[ 35.360748] powernow-k8: 1 : fid 0xc (2000 MHz), vid 0xf
[ 35.360750] powernow-k8: 2 : fid 0xa (1800 MHz), vid 0x11
[ 35.360753] powernow-k8: 3 : fid 0x2 (1000 MHz), vid 0x16
[ 36.004024] Clocksource tsc unstable (delta = -261871484 ns)
[ 69.750801] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 71.392312] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 71.845650] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 78.671648] [drm] Initialized drm 1.1.0 20060810
[ 78.869715] alloc irq_desc for 16 on node 0
[ 78.869723] alloc kstat_irqs on node 0
[ 78.869746] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 78.871097] [drm] Initialized via 2.11.1 20070202 for 0000:01:00.0 on minor 0
[ 78.871744] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0106407){t:'d';sz:16} arg(ff82b200) on /dev/dri/card0
[ 78.871790] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0106407){t:'d';sz:16} arg(ff82b200) on /dev/dri/card0
[ 78.871807] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0086401){t:'d';sz:8} arg(ff82b1f8) on /dev/dri/card0
[ 78.946336] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0246400){t:'d';sz:36} arg(09b5df10) on /dev/dri/card0
[ 78.971230] ioctl32(Xorg:2494): Unknown cmd fd(11) cmd(c0246400){t:'d';sz:36} arg(09b5df10) on /dev/dri/card0
[ 80.344020] eth0: no IPv6 routers present
[ 193.434434] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 0304
board_vendor: ASUSTeK Computer INC.
board_name: M2V-MX SE
board_version: Rev x.xx
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] [1106:3230] (rev 11) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:8297]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (500ns min)
Interrupt: pin A routed to IRQ 16
Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
Region 1: Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at fbef0000 [disabled] [size=64K]
Capabilities: <access denied>
20:01.0 Audio device [0403]: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) [1106:3288] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:8290]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fbffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: HDA Intel
** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c312 Logitech, Inc. DeLuxe 250 Keyboard
Bus 003 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.32-5-amd64 depends on:
ii debconf [debconf-2.0] 1.5.41
ii initramfs-tools [linux-initramfs-tool] 0.99
ii linux-base 3.3
ii module-init-tools 3.16-1
Versions of packages linux-image-2.6.32-5-amd64 recommends:
ii firmware-linux-free 3
ii libc6-i686 2.13-21
Versions of packages linux-image-2.6.32-5-amd64 suggests:
pn grub | lilo <none>
pn linux-doc-2.6.32 <none>
Versions of packages linux-image-2.6.32-5-amd64 is related to:
pn firmware-bnx2 <none>
pn firmware-bnx2x <none>
pn firmware-ipw2x00 <none>
pn firmware-ivtv <none>
pn firmware-iwlwifi <none>
pn firmware-linux <none>
pn firmware-linux-nonfree <none>
pn firmware-qlogic <none>
pn firmware-ralink <none>
pn xen-hypervisor <none>
Bug#637659: Linux kernel: 2.6.32.42: (Debian Bug#637659): pci 0000:00:00.0: BAR 0: address space collision on of device
Hi Paul,
Paul Menzel wrote:
> Commit 29cf7a30 [3] addresses this issue for my board by adding a quirk.
>
> commit 29cf7a30f8a0ce4af2406d93d5a332099be26923
> Author: Paul Menzel <paulepanter@users.sourceforge.net>
> Date: Wed Aug 31 17:07:10 2011 +0200
>
> x86/PCI: use host bridge _CRS info on ASUS M2V-MX SE
[...]
> Unfortunately I do not have outputs from `dmesg` anywhere from older
> Linux versions so I do not know when this problem started. I am pretty
> sure though that they have not been there since the beginning.
Yep, the regression fixed by 29cf7a30 was likely introduced by
v2.6.31-rc1~1 (Revert "PCI: use ACPI _CRS data by default",
2009-06-24).
A partial fix was v2.6.34-rc1~287^2~2 (x86/PCI: use host bridge _CRS
info by default on 2008 and newer machines, 2010-02-23), which does
not seem to be part of v2.6.32.y (and Debian squeeze) but probably
should be.
Hope that helps,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111010094642.GA8878@elie.hsd1.il.comcast.net">ht tp://lists.debian.org/20111010094642.GA8878@elie.hsd1.il.comcast.net
10-10-2011, 09:58 AM
Jonathan Nieder
Bug#637659: Linux kernel: 2.6.32.42: (Debian Bug#637659): pci 0000:00:00.0: BAR 0: address space collision on of device
Jonathan Nieder wrote:
> Paul Menzel wrote:
>> I am pretty
>> sure though that they have not been there since the beginning.
>
> Yep, the regression fixed by 29cf7a30 was likely introduced by
[...]
Quick correction: that was only a regression within the merge window.
Since we are just talking about a log message, it's possible the
address space collision was reported in a different way before or
something; it is hard to say much without knowing which kernel to
compare to.
What I wrote afterwards still has a chance of being true. Namely:
> A partial fix was v2.6.34-rc1~287^2~2 (x86/PCI: use host bridge _CRS
> info by default on 2008 and newer machines, 2010-02-23), which does
> not seem to be part of v2.6.32.y (and Debian squeeze) but probably
> should be.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111010095815.GB8878@elie.hsd1.il.comcast.net">ht tp://lists.debian.org/20111010095815.GB8878@elie.hsd1.il.comcast.net
10-11-2011, 08:41 AM
Paul Menzel
Bug#637659: Linux kernel: 2.6.32.42: (Debian Bug#637659): pci 0000:00:00.0: BAR 0: address space collision on of device
Dear Jonathan,
as always, thank you very much for your prompt help and responses.
Am Montag, den 10.10.2011, 04:46 -0500 schrieb Jonathan Nieder:
> Paul Menzel wrote:
>
> > Commit 29cf7a30 [3] addresses this issue for my board by adding a quirk.
> >
> > commit 29cf7a30f8a0ce4af2406d93d5a332099be26923
> > Author: Paul Menzel <paulepanter@users.sourceforge.net>
> > Date: Wed Aug 31 17:07:10 2011 +0200
> >
> > x86/PCI: use host bridge _CRS info on ASUS M2V-MX SE
> [...]
> > Unfortunately I do not have outputs from `dmesg` anywhere from older
> > Linux versions so I do not know when this problem started. I am pretty
> > sure though that they have not been there since the beginning.
>
> Yep, the regression fixed by 29cf7a30 was likely introduced by
> v2.6.31-rc1~1 (Revert "PCI: use ACPI _CRS data by default",
> 2009-06-24).
The following commit is the reverted one.
$ git show 9e9f46c44
commit 9e9f46c44e487af0a82eb61b624553e2f7118f5b
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date: Thu Jun 11 10:58:28 2009 -0700
PCI: use ACPI _CRS data by default
$ git describe 9e9f46c44
v2.6.30-22-g9e9f46c
> A partial fix was v2.6.34-rc1~287^2~2 (x86/PCI: use host bridge _CRS
> info by default on 2008 and newer machines, 2010-02-23), which does
> not seem to be part of v2.6.32.y (and Debian squeeze) but probably
> should be.
Additionally that would not be enough for my board as this is an “old“
machine from 2006.
Additionally as guessed in Linux 2.6.32.x there seems to be no way to
force the use of _CRS information using the Linux kernel command line.
$ more /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/storage-root ro quiet pci=use_crs
Furthermore searching for »Linux 2.6.32 address space collision on of
device« on the Web there are several hits like Debian bug report #567435
[5] so it would be worth to fix in my opinion.
Ben and Maximilian state in the report thread [5] that the message is
harmless. But since my system occasionally freezes it would be great if
you could confirm that.
> with the longterm Linux kernel 2.6.32 I am getting the following error
>
> pci 0000:00:00.0: BAR 0: address space collision on of device [0xc8000000-0xcfffffff]
>
> It is already reported to the Debian BTS as report #613979.
The patch that fixed this upstream (v3.1-rc10~19, "x86/PCI: use host
bridge _CRS info on ASUS M2V-MX SE", 2011-08-31) has some dependencies
with subtle consequences, so I am not sure how to fix this.
2.6.32.y does have support for the pci=use_crs parameter (see
arch/x86/pci/common.c). Do I understand correctly that, unlike later
kernels, the squeeze kernel does not benefit from it?
Sorry for the trouble,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120328192243.GA9872@burratino">http://lists.debian.org/20120328192243.GA9872@burratino