"PCI: BIOS BUG #81[49435000] found" error interrupt usplash

[Daann]

This bug is generated by a BIOS bug of Phoenix brand.

This comment down the importance, cause it's just an esthetic bug:

http://www.fedoraforum.org/forum/showpost.php?p=901026&postcount=39

"On the whole bug #81 can be ignored as it has no material affect on a running system. The way to fix this is to either hassle your manufacturer to fix it or delve into the bios code. As I said the linux kernel is trying to setup hardware one way but the bios is saying no, go away. When the processors are setup as x86_64 they function differently to when they are setup for 32bit so this may not be an issue under 64 bit linux's."

This error message cause that usplash can't be seen fine at the beggining, and when you shut down the system the upslash is not there :(

--------------------------------
Original description

When booting Ubuntu 7.04 i get a bios bug,

PCI: BIOS BUG #81[49435000] found

Maybe this has something to do with my wireless/sound?

Specs,

Hp pavilion dv2020ca
Amd turion x2 64bit (32bit feisty fawn)
Ubuntu 7.04 Feisty Fawn

[Daann (daanspanjers)]

If you need more information just let me know.

[Tom Gallacher (tom-hammersmad)]

I Have the same when my system,the sound only wants to work when it wants too, at this moment it isn't working. however my wireless is working fine.

Specs:

Hp Pavilion dv2036ea
Amd turion x2 64bit (32bit feisty fawn)
Ubuntu 7.04 Feisty Fawn

[ahwayakchih (ahwayakchih)]

Here sound works, but it doesn't remember sound volume setting, and defaults to almost highest after each boot :(
I get the same BIOS bug when booting.

Specs:

Benq P52EG (http://benq.pl/products/joybook/?product=717&page=specifications)
AMD Sempron 3400+
Ubuntu 7.04 Feisty Fawn

Volume COntrol panel says it's Realtec ALC262 sound chipset here. Device Manager says vendor and device "unknown", but lists them under "ATI Technologies Inc SB450 HDA Audio" device.

[chainlynx (dannycolligan)]

I have the same error message on boot. No apparent problems with the sound, unlike some posters above. The only thing I notice wrong with my computer, however is on a GNOME logout. The logout sound keeps cycling/glitching and I don't return to the login screen -- the monitor stays blank. I have to do a hard reset on my laptop by holding the power button down to get the thing working again.

Specs:
HP Pavilion dv9000z laptop
Amd turion x2 64bit (32bit feisty fawn)
Ubuntu 7.04 Feisty Fawn (with no upgrades -- fresh install)

[Everett Kotler (ebu)]

I get the same message as well, I have sound too. Not observing any other problems though.

Fiesty Fawn

Fujitsu A6025 laptop
Pentium Dual-Core

[urho (vonturha)]

getting this same message when booting on gutsy. Sound, video etc. seems to work fine. sometimes logout don't work just getting a screen full of garbage, i have to do a hard reset

Toshiba satellite A200-s17

[Walther Seidel (waseidel)]

Well, I have the same error too and everything it's working, but at the moment of the shutdown sometimes it don't do nothing just keep beeping and the screen black but it's randomly, I don't know what could be that but I want this be solved because I don't like see a bug when I'm starting my laptop

Specs:
Compaq F566LA
AMD Turion 64 (MK-38) (32bits Feitsy Fawn)
1 GB RAM

[Kurt (kurtbcox)]

I get the same error message on feisy or gutsy kernels and my sound doesn't work either.

Specs

Gateway MX3417
AMD Turion 64-bit
1 GB Ram

[Jojo (kuzniarpawel)]

I also receive this message but everything works fine on my Compal HEL 80 (except camera, fingerprint reader - for obvious reasons).

Linux adam-laptop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

[Jojo (kuzniarpawel)]

and here is my lspci

[Matthew Meyer (osarusan)]

I have the same bug, running Gutsy on a Fujitsu Stylistic ST5112. Everything works *but* sound.

[Brian Murray (brian-murray)]

Reviewing this bug report and its comments it seems that multiple people are experiencing this problem. Subsequently, I am confirming this bug report. For future reference you can manage the status of bug reports by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status .

[Risto H. Kurppa (risto.kurppa)]

HP Pavilion dv2140eu here w. the same error message as you all. I haven't found anything that wouldn't work on this laptop.

[Anup Jayapal Rao (anup-rao)]

Hi,

I am using Kubuntu 7.10 on my Acer Aspire 5051AWXMi. I notice the BIOS BUG#81 message as well as the following:

PCI: Cannot allocate resource region 7 of bridge 0000:00:04.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:04.0
PCI: Cannot allocate resource region 7 of bridge 0000:00:05.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:05.0
PCI: Cannot allocate resource region 7 of bridge 0000:00:06.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:06.0
PCI: Cannot allocate resource region 7 of bridge 0000:00:07.0
PCI: Cannot allocate resource region 8 of bridge 0000:00:07.0

The following are the observations on my laptop:

1> HD Installed Kubuntu:
Cannot use Xorg when running from battery, works only when powered by AC mains. When using battery, black screen with artifacts and lines are noticed. Text console works fine. This is the case for non accelerated or accelerated drivers.

2> Using Live Kubuntu CD:
Xorg launches when running from battery but switching to terminal or shutdown shows black screen with artifacts and lines are noticed. Works fine if AC mains are connected.

Windows Vista Home Basic was provided on the laptop, it has no issues problems displaying hardware accelerated graphics when running from battery.

Regards,
Anup

[Darrin Tisdale (tizzyd)]

For me on this Fujitsu Lifebook P1610, it's not the sound that's an issue. That works. It's the Wacom tablet. I found that I can load the wacom driver, but there's no recognition in the kernel for the PnP object. It comes up as FUJ02e6. A quick google on that ID, and it appears that the id is in the .24 revision to the kernel. So, it looks like I'm compiling a new kernel. Oh well.

[Matt LaPaglia (mlapaglia)]

I have had this problem since Feisty on my Compal Hel80 notebook. Everything works fine, I'm not sure if this is affecting my system performance or not but everything seems fine.

[Walther Seidel (waseidel)]

this bug still coming in hardy 8.04 alpha tribe 4, kernel 2.6.24-8

I still with that but still unknowing what's the trouble with my laptop because it's works fine

I want to make a question to all of us your processor is 64bits or 32bits (just curiosity)

[Fabián Rodríguez (magicfab)]

Long thread in forums with people having the same problem, someone implies this is a "Trusted computing' issue with Phoenix BIOSes (see comment on November 3rd, 2007, 07:55 AM):
http://ubuntuforums.org/archive/index.php/t-332829.html

[Fabián Rodríguez (magicfab)]

Most logical explanation for this:
http://www.fedoraforum.org/forum/showpost.php?p=901026&postcount=39

Bottom line, hardware problem (bad BIOS implementation from manufacturer), not a software bug in itself.

[Leann Ogasawara (leannogasawara)]

Just curious if anyone has tried updating their BIOS? Regardless, BIOS issues are something we can not resolve.

[Michalxo (michalxo)]

Hi, yes I did. I flashed my BIOS, but no change after all. I used toshiba A200-1gs BIOS ver. 5.20 for XP. If I remember well. bug stayed :(

[Dimitrios Symeonidis (azimout)]

I get the same bios bug error message in dmesg, however all my hardware seems to work fine... i have a fujitsu siemens s7110 with gutsy...

[Dimitrios Symeonidis (azimout)]

Upgrading to the 2.6.24.4 kernel (compile from source) made the bug disappear, and it's also not there with the 2.6.25 kernel...

[ericleary (eric-leary)]

Thanks Dimitrios! since Ubuntu 8.04 has this kernel, I will be installing
it in five days, once it comes out of Beta.

Yeah.

On Fri, Apr 18, 2008 at 10:57 AM, Dimitrios Symeonidis <email address hidden>
wrote:

> Upgrading to the 2.6.24.4 kernel (compile from source) made the bug
> disappear, and it's also not there with the 2.6.25 kernel...
>
> --
> PCI: BIOS BUG #81[49435000] found - [HP pavilion dv2000]
> https://bugs.launchpad.net/bugs/116734
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Walther Seidel (waseidel)]

I still having the trouble with the kernell '2.6.24-16-generic' it still
apearing at boot 'pci bios bug ....' i'm running ubuntu 8.04 beta, at this
kernell I don't get to modify the grub to boot (I was to add at end of line
'noapic noirqdebug pnpbios=off acpi=off' to boot).

anyway this bug still at least to me still in my laptop

2008/4/19 ericleary <email address hidden>:

> Thanks Dimitrios! since Ubuntu 8.04 has this kernel, I will be installing
> it in five days, once it comes out of Beta.
>
> Yeah.
>
> On Fri, Apr 18, 2008 at 10:57 AM, Dimitrios Symeonidis <email address hidden>
> wrote:
>
> > Upgrading to the 2.6.24.4 kernel (compile from source) made the bug
> > disappear, and it's also not there with the 2.6.25 kernel...
> >
> > --
> > PCI: BIOS BUG #81[49435000] found - [HP pavilion dv2000]
> > https://bugs.launchpad.net/bugs/116734
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
>
>
> ** Attachment added: "unnamed"
> http://launchpadlibrarian.net/13582927/unnamed
>
> --
> PCI: BIOS BUG #81[49435000] found - [HP pavilion dv2000]
> https://bugs.launchpad.net/bugs/116734
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
"El software es como el sexo: cuando es gratis es mejor"
- Linus Torvalds
Linux User: 461212
Ubuntu User: 20734
http://www.ubuntu-co.com

[Matthew Meyer (osarusan)]

I just upgraded to Hardy, and the problem mostly disappeared. That is to say, I used to get a bunch of errors (8 or 9) but now I only get a single error. The sound still doesn't work.

[Marciano (paulomarciano)]

From what i hear, hardy's kernel is based upon 2.6.24.3 , which may be why you guys haven't made the problem go away. Try compiling form source.

[Anup Jayapal Rao (anup-rao)]

I have checked with Hardy Heron [and Zenwalk with kernel 2.6.25]. I notice
these messages in addition to the PCI messages

PCI: Bridge: 0000:00:01.0
  IO window: 9000-9fff
  MEM window: b0100000-b01fffff
  PREFETCH window: c0000000-cfffffff
PCI: Bridge: 0000:00:04.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:05.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:06.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:07.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.

Sadly, on an ACER 5051AWXMi [my Laptop :-( ], these correspond to the PCI
Bridges for video.

00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:05.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:07.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge

checking dmesg reveals:

ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 17 (level, low) -> IRQ 21
[fglrx] GART Table is not in FRAME_BUFFER range

glxgears will report a score around 1700fps but enabling compositing will
drag the system. I believe that the root cause of this issue also causes the
laptop to underperform when running 3D applications.

I do not know if this is relevant, but I cannot seem to get my display to
work in 32bit depth , though 24 seems just fine. Could this be the result of
the same issue?

Regards,
Anup

On Tue, Apr 22, 2008 at 6:28 PM, Marciano <email address hidden> wrote:

> >From what i hear, hardy's kernel is based upon 2.6.24.3 , which may be
> why you guys haven't made the problem go away. Try compiling form
> source.
>
> --
> PCI: BIOS BUG #81[49435000] found - [HP pavilion dv2000]
> https://bugs.launchpad.net/bugs/116734
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Matt Scholz (scholzilla)]

I don't know if I believe this is a hardware issue. I never got this bug until I switched from Hardy 64-bit to Hardy 32-bit on my gateway mt6452 laptop (amd64, phoenix bios).

[Fabián Rodríguez (magicfab)]

If anyone commenting this bug would at least care to read my previous comment or just read this[1], it would save all subscribers to this bug some time when going through comments that don't contribute to actually solving this bug.

Sorry to be so blunt, let's focus on the issue here.

[1] http://www.fedoraforum.org/forum/showpost.php?p=901026&postcount=39

Citing:

"On the whole bug #81 can be ignored as it has no material affect on a running system. The way to fix this is to either hassle your manufacturer to fix it or delve into the bios code. As I said the linux kernel is trying to setup hardware one way but the bios is saying no, go away. When the processors are setup as x86_64 they function differently to when they are setup for 32bit so this may not be an issue under 64 bit linux's.

pepe123: you don't see the message when using those parameters because linux just accepts the hardware config as presented by the bios. No code is run to rearrange the hardware in a more functional way by the kernel (bad bios code will run as bad bios code, if it is really bad then at the very least stuff won't work at the wort you will get crashes.).

noapic disables the the kernel APIC Code (Advanced Programmable Interrupt Controller). Switch this off and you don't have programmable Interrupts and other stuff.

nolapic disables the kernel local apic code. The local apic resides on the CPU and mediates access to the processor. It is not required on single processor systems but is required on dual processor ystems including dual core processors.

Routing interrupts inefficiently can decrease the systems performance somewhat and also throw up other isssues.

In some senses it is bad to use these parameters because you lose performance and possibly some functionality (for example the bios configures some hardware to share interrupts with some other hardware. Linux has a problem with this but it knows how to set things up correctly. noapic disables linux' ability to resolve the problem.)

Sometimes you need to disable apic code to run linux but if you don't then don't.

For example installing fedora 8 on my laptop works if I disable apic but it will also work if I add the vga=0x0317. So I choose the second option. If you have a problem machine then use the least intrusive solution. For these cases Google is your friend. Just remember no problem is ever a new problem

The Acpi site is an interesting read but of no practical use to the average joe. To use that info you need to be able to rewrite your bios code and does not deal directly with apic issues anyway (APIC and ACPI are different although related beasties)"

[Fabián Rodríguez (magicfab)]

bug #81 as linked in my last comment (and this one) is a result of automatic linking, not an actual correct or voluntary reference to Bug #81 in Launchpad.

[Sander van der Veeke (sanderveeke-deactivatedaccount)]

I understand that this bug is something to forget, but is it possible to hide the bug message?

it makes my boot process jumpy.

[Dimitrios Symeonidis (azimout)]

Like I said above, the message does not appear since 2.6.24.4

[Walther Seidel (waseidel)]

Dimitrios Symeonidis, let's see my dmesg and will see that bug still appearing

[Matt Scholz (scholzilla)]

Yep, also appears still on my system and I'm fully up-to-date with the kernels.

[Sander van der Veeke (sanderveeke-deactivatedaccount)]

@dimitrios: Bug still shows on my up-to-date system.

No way to hide it? can't i tell Grub to stop showing those messages?

[Dimitrios Symeonidis (azimout)]

Ok, I rebooted with the latest kernel in the ubuntu repositories (2.6.24-19) and the message reappeared. I am otherwise running the latest kernel from kernel.org (2.6.25.9), with a customized .config file...

I am not sure which upstream version the 2.6.24-19 kernel is based upon... I will revert my kernel sources to 2.6.24.x, recompile and reboot, to see if the problem disappeared because of the source upgrades or because of changes to my .config file. I will post my conclusions here...

[Dimitrios Symeonidis (azimout)]

The message doesn't show with my custom 2.6.24 kernel... So it's in the kernel's .config file, not in the sources...
I'll try and find where the message comes from, to locate the kernel option responsible...

PS Sander, the message comes from the kernel, not grub

[Dimitrios Symeonidis (azimout)]

The message is coming from the file arch/x86/pci/pcbios.c, on line 137-9:

  if (status || signature != PCI_SIGNATURE) {
   printk (KERN_ERR "PCI: BIOS BUG #%x[%08x] found\n",
    status, signature);

[Dimitrios Symeonidis (azimout)]

So (correct me if I'm wrong) in this case:

status = 0x81
signature = 0x49435000
PCI_SIGNATURE = 'PCI ' (which translates to 0x00494350)

from the definition
#define PCI_SIGNATURE (('P' << 0) + ('C' << 8) + ('I' << 16) + (' ' << 24))

[Dimitrios Symeonidis (azimout)]

Small test program:
#include <stdio.h>

#define PCI_SIGNATURE (('P' << 0) + ('C' << 8) + ('I' << 16) + (' ' << 24))

int main(void)
{
 short status = 0x81;
 long signature = 0x49435000;

 printf("status = %x\nsignature = %08x\n", status, signature);
 printf("PCI_SIGNATURE = %x\n", PCI_SIGNATURE);
 return 0;
}

the result:
status = 81
signature = 49435000
PCI_SIGNATURE = 20494350

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Julian Alarcon (julian-alarcon)]

This bugs is still there.
Using Ubuntu 8.04 with all updates.
Linux openbox-laptop 2.6.24-24-generic #1 SMP Tue Jul 7 19:46:39 UTC 2009 i686 GNU/Linux

PC: Notebook Compaq Presario F502LA

[Dimitrios Symeonidis (azimout)]

Julian, could you try with the latest ubuntu version? I don't get the message anymore with Jaunty's kernel..

[Dimitrios Symeonidis (azimout)]

Also, do you have any issues with your hardware, or is it just the message that annoys you?

[Julian Alarcon (julian-alarcon)]

Thu bug had been fixed, I'm using right now Ubuntu 9.04 Jaunty Jackalope.

[m45smg (m45smg)]

But the Hardy still have this problem! You are ignore to fix the problem in Hardy!!

[Jonathan Aquilina (eagles051387)]

i have no idea what you said.

On Mon, Oct 12, 2009 at 3:23 PM, m45smg <email address hidden> wrote:

> But the Hardy still have this problem! You are ignore to fix the problem
> in Hardy!!
>
> --
> "PCI: BIOS BUG #81[49435000] found" error interrupt usplash
> https://bugs.launchpad.net/bugs/116734
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Jonathan Aquilina

[Fabián Rodríguez (magicfab)]

Fixing this in Hardy is not about to happen unless someone cares enough to file a Stable Release Update request, using this process:
https://wiki.ubuntu.com/StableReleaseUpdates

Citing:
"Once an Ubuntu release has been completed and published, updates for it are only released under certain circumstances, and must follow a special procedure called a "stable release update" or SRU."

Any further questions about this or similar issues should happen in the Answers tracker or in the Ubuntu forums, as this bug has now been "fix released":
https://answers.launchpad.net/ubuntu/+source/linux/+addquestion

[Jonathan Aquilina (eagles051387)]

then if this bug has had a fix released for it then this bug can im guessing
be marked as fix released and link it to the answers link.

2009/10/13 Fabián Rodríguez <email address hidden>

> Fixing this in Hardy is not about to happen unless someone cares enough to
> file a Stable Release Update request, using this process:
> https://wiki.ubuntu.com/StableReleaseUpdates
>
> Citing:
> "Once an Ubuntu release has been completed and published, updates for it
> are only released under certain circumstances, and must follow a special
> procedure called a "stable release update" or SRU."
>
> Any further questions about this or similar issues should happen in the
> Answers tracker or in the Ubuntu forums, as this bug has now been "fix
> released":
> https://answers.launchpad.net/ubuntu/+source/linux/+addquestion
>
> --
> "PCI: BIOS BUG #81[49435000] found" error interrupt usplash
> https://bugs.launchpad.net/bugs/116734
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Jonathan Aquilina