Ubuntu

pciehp and shpchp modules produce too much error output

Reported by Alexis Bunel on 2004-09-28
46
Affects Status Importance Assigned to Milestone
hotplug (Ubuntu)
Low
Thom May

Bug Description

Hotplug service always fails for the PCI part when trying to load what seems to
be unneeded modules. This is not a stopping bug, as booting follows correctly.

Relevant log :
Sep 28 22:36:53 lezard kernel: cpci_hotplug: CompactPCI Hot Plug Core version: 0.2
Sep 28 22:36:53 lezard kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 28 22:36:53 lezard kernel: pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN
fail=0x5
Sep 28 22:36:53 lezard kernel: pciehp: acpi_pciehprm:get_device PCI ROOT HID
fail=0x5
Sep 28 22:36:53 lezard kernel: shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN
fail=0x5
Sep 28 22:36:53 lezard kernel: shpchp: acpi_shpchprm:get_device PCI ROOT HID
fail=0x5

Hardware details :
lezard:/home/ubuntu# lspci -v
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
        Flags: bus master, medium devsel, latency 0
        Memory at d8000000 (32-bit, prefetchable)
        Capabilities: [a0] AGP version 2.0
        Capabilities: [c0] Power Management version 2

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
(prog-if 00 [Normal decode])
        Flags: bus master, 66MHz, medium devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000c000-0000cfff
        Memory behind bridge: dc000000-ddffffff
        Prefetchable memory behind bridge: d0000000-d7ffffff
        Expansion ROM at 0000c000 [disabled] [size=4K]
        Capabilities: [80] Power Management version 2

0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
        Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
        Flags: bus master, stepping, medium devsel, latency 0
        Capabilities: [c0] Power Management version 2

0000:00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a
[Master SecP PriP])
        Flags: bus master, medium devsel, latency 32
        I/O ports at d000 [size=16]
        Capabilities: [c0] Power Management version 2

0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 16) (prog-if 00 [UHCI])
        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
        Flags: bus master, medium devsel, latency 32, IRQ 11
        I/O ports at d400 [size=32]
        Capabilities: [80] Power Management version 2

0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 16) (prog-if 00 [UHCI])
        Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
        Flags: bus master, medium devsel, latency 32, IRQ 11
        I/O ports at d800 [size=32]
        Capabilities: [80] Power Management version 2

0000:00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
(rev 40)
        Flags: medium devsel, IRQ 9
        Capabilities: [68] Power Management version 2

0000:00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97
Audio Controller (rev 50)
        Subsystem: Micro-Star International Co., Ltd.: Unknown device 3300
        Flags: medium devsel, IRQ 10
        I/O ports at dc00
        I/O ports at e000 [size=4]
        I/O ports at e400 [size=4]
        Capabilities: [c0] Power Management version 2

0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY
[Radeon 7000/VE] (prog-if 00 [VGA])
        Subsystem: Palit Microsystems Inc.: Unknown device 5159
        Flags: bus master, stepping, 66MHz, medium devsel, latency 32, IRQ 11
        Memory at d0000000 (32-bit, prefetchable)
        I/O ports at c000 [size=256]
        Memory at dd000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [58] AGP version 2.0
        Capabilities: [50] Power Management version 2

Report from debconf : *** The following debconf settings were detected:
* hotplug/ignore_pci_class_display: true
* hotplug/net_agent_policy: hotplug
* hotplug/usb_keyboard:
* hotplug/static_module_list:
  hotplug/x11_usbmice_hack: false

Matt Zimmerman (mdz) wrote :

As noted on the mailing list, these drivers are always loaded, and that's OK,
but they shouldn't produce so much unnecessary output when they aren't needed.
This output should be suppressed unless the user boots in recovery mode.

Thanks Mark, I've seen too late your mail. Could it be possible to produce less
output ?

Robert Brimhall (rbrimhall) wrote :

Less output would be better... As it stands I thought something might be wrong
until I read about this on the mailing list

Sean O'Donnell (sean-odonnell) wrote :

Same problem observed on my IBM Thinkpad T21 (<email address hidden>)

Matt Zimmerman (mdz) wrote :

I think this was fixed in 0.0.20040329-11ubuntu8:

hotplug (0.0.20040329-11ubuntu8) warty; urgency=low

  * debian/hotplug.init: Fixed #1082
  * debian/hotplug.init: Fixed several exitstatus bugs
  * debian/hotplug.init: Lower kernel printk level if non VERBOSE

 -- Nathaniel McCallum <email address hidden> Tue, 7 Sep 2004 18:17:36 -0400

that should have stopped the messages from being printed to the console. The
messages logged to syslog are harmless, and not distracting like the console
messages.

Can you confirm whether you are seeing the messages on the console?

Matt Zimmerman (mdz) wrote :

Since this bug was just described as "vague" on the mailing list, I'll be explicit:

These messages are entirely harmless, and this is purely a cosmetic issue.

Sean O'Donnell (sean-odonnell) wrote :

Am running 0.0.20040329-11ubuntu10 and still seeing the errors on the thinkpad

Nathaniel McCallum (nmccallum) wrote :

At what point in the boot process are the messages occuring? Do they occur
before "Mounting tmpfs over /dev... [ ok ]"? Or at another point?

Matt Zimmerman (mdz) wrote :

*** Bug 8906 has been marked as a duplicate of this bug. ***

Matt Zimmerman (mdz) wrote :

This is becoming a serious FAQ on the mailing lists and needs to be fixed for
release, despite its cosmeticness.

Sean O'Donnell (sean-odonnell) wrote :

re At what point in the boot process are the messages occuring? Do they occur
before "Mounting tmpfs over /dev... [ ok ]"? Or at another point?

Nope,It says clean ifupdown , then starting hotplug subsystem , and then the
error messages.

Joël Haudiquer (jhaudiq) wrote :

Hi all,
These errors messages are generated when the hotplug service is started.
If we are sure they are entirely harmless and the hotplug service is well
running, we can add these modules in the hotplug blacklist to prevent not
loading it.
What about my suggestion ?

Thanks for help.

Joël Haudiquer.

Nathaniel McCallum (nmccallum) wrote :

Can someone who is getting these messages try the attached patch for
/etc/init.d/hotplug to see if it makes the situation better (I'm still not sure
where all this is coming from)? Thanks!

Nathaniel McCallum (nmccallum) wrote :

Created an attachment (id=490)
debuging patch for hotplug initscript

Joël Haudiquer (jhaudiq) wrote :

Hi Nathaniel,

My hotplug file was already patched.
I've tested without blacklisted these two modules and it's the same with errors
twice about pciehp & shpchp.
The only workaround I've found, it's to add these two modules in the hotplug
blacklist file.

Thanks for your help.

joël haudiquer.

Daniel Robitaille (robitaille) wrote :

(In reply to comment #13)
> Can someone who is getting these messages try the attached patch for
> /etc/init.d/hotplug to see if it makes the situation better (I'm still not sure
> where all this is coming from)? Thanks!

tried the patch. It seems it got rid of a couple of lines of output, but the
errors are still displayed on the console

bluegeek (bluegeek) wrote :

I also get these errors:

modprobe: FATAL: Error inserting pciehp
modprobe: FATAL: Error inserting shpchp

I think the word "FATAL" is somewhat scaring for a regular user.

Matt Zimmerman (mdz) wrote :

*** Bug 9356 has been marked as a duplicate of this bug. ***

Donald Noble (dnoble) wrote :
Download full text (14.9 KiB)

I know that bug 9356 was labeled a duplicate but that bug was exactly right. It
really does cause the computer to hang/lock-up. I found, (after several
reinstalls,) that you have to hard-reboot 2 or 3 times to get Ubuntu to load. I
know that if my mouse (USB) blinks 2 times I'm usually okay. I went ahead and
added this dmesg to let you guys know.

he: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 2600+ stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23 not
connected.
..TIMER: vector=0x31 pin1=2 pin2=-1
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2082.0780 MHz.
..... host bus clock speed is 333.0244 MHz.
checking if image is initramfs...it isn't (ungzip failed); looks like an initrd
Freeing initrd memory: 4360k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfb4d0, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040816
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *0, disabled.
ACPI: PCI Interrupt Link [ALKB] (IRQs 21) *0, disabled.
ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0, disabled.
ACPI: PCI Interrupt Link [ALKD] (IRQs 23) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00fbfa0
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xbfd0, dseg 0xf0000
PnPBIOS: 14 nodes reported by PnP BIOS; 14 recorded by driver
PCI: Using ACPI for IRQ routing
ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI 19 (level, low) -> IRQ 169
ACPI: PCI Interrupt Link [ALKB] BIOS reported IRQ 0, using IRQ 21
ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21
ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 177
ACPI: PCI interrupt 0000:00:10.1[B] -> GSI 21 (level, low) -> IRQ 177
ACPI: PCI interrupt 0000:00:10.2[C] -> GSI 21 (level, low) -> IRQ 177
ACPI: PCI interrupt 0000:00:10.3[D] -> GSI 21 (level, low) -> IRQ 177
ACPI: PCI Interrupt Link [ALKA] BIOS reported IRQ 0, using IRQ 20
ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
ACPI: PCI interrupt 0000:00:11.1[A] -> GSI 20 (level, low) -> IRQ 185
ACPI: PCI Interrupt Link [ALKD] BIOS reported IRQ 0...

Thom May (thombot) wrote :

(In reply to comment #19)
> I know that bug 9356 was labeled a duplicate but that bug was exactly right. It
> really does cause the computer to hang/lock-up. I found, (after several
> reinstalls,) that you have to hard-reboot 2 or 3 times to get Ubuntu to load. I
> know that if my mouse (USB) blinks 2 times I'm usually okay. I went ahead and
> added this dmesg to let you guys know.

Um, I think this is added to the wrong bug.

Matt Zimmerman (mdz) wrote :

Please make sure that these messages are suppressed for Hoary; this is one FAQ
that we should definitely eliminate

Matt Zimmerman (mdz) wrote :

CCing Fabio since I'm not sure whether this ought to be fixed in the kernel or
in userland

Thom May (thombot) wrote :

I think it needs to be a two pronged approach - modprobe needs to be much
quieter when the kernel printk level is turned to quiet, and the two modules
need to be put on a printk diet.

Thom May (thombot) wrote :

Should now be fixed:
 hotplug (0.0.20040329-16ubuntu5) hoary; urgency=low
 .
   * Run modprobe silently (Ubuntu: #1869, #1552)

Daniel Robitaille (robitaille) wrote :

*** Bug 13306 has been marked as a duplicate of this bug. ***

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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