"pci BAR 3: " messages on boot

Bug #445062 reported by Joel Wagler
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

The package in question is linux-source-2.6.31

The following lines appear at startup instead of the xsplash screen. I expected to see the xsplash with the Ubuntu logo however I saw the following messages instead.

[ 0.050700] pci 0000:00:0b.0: BAR 3: address space collision on of device [0x08-0x0f]
[ 0.050759] pci 0000:00:0b.0: BAR 3: can't allocate resource

[ 0.090712] pci 0000:00:0b.0: BAR 1: error updating (0x001001 != 0x000001)
[ 0.090772] pci 0000:00:0b.0: BAR 4: error updating (0x40000004 != 0x36850264)
[ 0.090824] pci 0000:00:0b.0: BAR 4: error updating (high 0x000000 != 0x000020)
[ 0.090877] pci 0000:00:0b.0: BAR 3: error updating (0x001401 != 0x000009)
[ 8.098124] sis630_smbus 0000:00:02.0: SIS630 comp. bus not detected, module not inserted.
[ 8.098577] sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x0c00
[ 8.098585] ACPI: I/O resource 0000:00:02.1 [0xc00-0xc1f] conflicts with ACPI region SMRG [0xc00-0xc1f]
...

The release I'm using is
 Description: Ubuntu karmic (development branch)
Release: 9.10

Here is the kernel image
linux-image-2.6.31-12-386:
  Installed: 2.6.31-12.39
  Candidate: 2.6.31-12.39
  Version table:
 *** 2.6.31-12.39 0
        500 http://ca.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

I submitted information with ubuntu-bug linux however I can submit more information if you need it. The issue is repeatable.

ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jwagler 1928 F.... pulseaudio
 /dev/snd/controlC0: jwagler 1928 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'CA0106'/'Live! 7.1 24bit [SB0410] at 0xa000 irq 5'
   Mixer name : 'CA0106'
   Components : ''
   Controls : 30
   Simple ctrls : 18
Card1.Amixer.info:
 Card hw:1 'U0x46d0x8d7'/'USB Device 0x46d:0x8d7 at usb-0000:00:02.2-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:08d7'
   Controls : 3
   Simple ctrls : 2
Date: Tue Oct 6 18:49:07 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 046d:08d7 Logitech, Inc. QuickCam Communicate STX
MachineType: ECS K7S5A
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-12-386 2.6.31-12.39
ProcCmdLine: root=UUID=27df542d-fe0d-4b94-9e12-410983c589fc ro quiet splash
ProcEnviron:
 LANGUAGE=en_CA.UTF-8
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.39-386
RelatedPackageVersions: linux-firmware 1.21
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-12-386 i686
UserAsoundrc:
 # ALSA library configuration file

 # Include settings that are under the control of asoundconf(1).
 # (To disable these settings, comment out this line.)
 </home/jwagler/.asoundrc.asoundconf>
WpaSupplicantLog:

XsessionErrors:
 (gnome-settings-daemon:1944): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1944): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1995): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1976): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:1966): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -17 and height 24
dmi.bios.date: 04/02/01
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 07.00T
dmi.board.name: K7S5A
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: Version 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr07.00T:bd04/02/01:svnECS:pnK7S5A:pvr1.0:rvnECS:rnK7S5A:rvr1.0:cvnECS:ct3:cvrVersion1.00:
dmi.product.name: K7S5A
dmi.product.version: 1.0
dmi.sys.vendor: ECS

Revision history for this message
Joel Wagler (joel-wagler) wrote :
Revision history for this message
Joel Wagler (joel-wagler) wrote :

I think the duplicate is wrong. No were in the duplicate do I see the following messages. I think these messages are why the boot screen doesn't work.

[ 0.050700] pci 0000:00:0b.0: BAR 3: address space collision on of device [0x08-0x0f]
[ 0.050759] pci 0000:00:0b.0: BAR 3: can't allocate resource

[ 0.090712] pci 0000:00:0b.0: BAR 1: error updating (0x001001 != 0x000001)
[ 0.090772] pci 0000:00:0b.0: BAR 4: error updating (0x40000004 != 0x36850264)
[ 0.090824] pci 0000:00:0b.0: BAR 4: error updating (high 0x000000 != 0x000020)
[ 0.090877] pci 0000:00:0b.0: BAR 3: error updating (0x001401 != 0x000009)
[ 8.098124] sis630_smbus 0000:00:02.0: SIS630 comp. bus not detected, module not inserted.
[ 8.098577] sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x0c00
[ 8.098585] ACPI: I/O resource 0000:00:02.1 [0xc00-0xc1f] conflicts with ACPI region SMRG [0xc00-0xc1f]

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
summary: - When booting there are messages from the kernel instead of the splash
- screen
+ "pci BAR 3: " messages on boot
Revision history for this message
Bjorn Helgaas (bjorn-helgaas) wrote :

This is not a duplicate of bug 438335.

This bug is caused by something wrong with the BARs of 00:0b.0:

  pci 0000:00:0b.0: BAR 1: error updating (0x001001 != 0x000001)
  pci 0000:00:0b.0: BAR 4: error updating (0x40000004 != 0x36850264)
  pci 0000:00:0b.0: BAR 4: error updating (high 0x000000 != 0x000020)
  pci 0000:00:0b.0: BAR 3: error updating (0x001401 != 0x000009)

This report is from a very old kernel, and the dmesg log doesn't contain quite enough information to tell exactly what's wrong. If this is still a problem, and somebody can collect a dmesg log from a current kernel, I'll take a look at it.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.