ubuntu-boot-experience ACPI Invalid PBLK Length 5

[Moneta Funzionata]

Binary package hint: usplash

On boot after selecting Ubuntu 9.10 (beta) from boot menu the message "ACPI Invalid PBLK Length [5]" is displayed at the top of the screen.

ProblemType: Bug
Architecture: i386
Date: Sat Oct 3 08:42:23 2009
DistroRelease: Ubuntu 9.10
Lsusb:
 Bus 002 Device 002: ID 0b33:08a0 Contour Design, Inc.
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System Manufacturer System Name
NonfreeKernelModules: nvidia
Package: usplash 0.5.39
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=334e67f7-3b9b-4d8c-89ff-3932ffc53f3d ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: usplash
Uname: Linux 2.6.31-11-generic i686
UsplashConf:
 # Usplash configuration file
 # These parameters will only apply after running update-initramfs.

 xres=1280
 yres=1024
dmi.bios.date: 08/30/2005
dmi.bios.vendor: Award Software, Inc.
dmi.bios.version: ASUS P4S800 ACPI BIOS Revision 1011 Beta 001
dmi.board.name: P4S800
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 7
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4S800ACPIBIOSRevision1011Beta001:bd08/30/2005:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4S800:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion:
dmi.product.name: System Name
dmi.product.version: System Version
dmi.sys.vendor: System Manufacturer

[Andreas Schildbach (schildbach)]

I don't see how this can be fixed in a generic way with the other boot message "bugs", as this is a specific error message. Unmarking duplicate.

[Moneta Funzionata (djmonkey1)]

According to the information posted in Bug #197267, this is a problem related to incorrect BIOS in certain ASUS motherboards. A PBLK length of [5] is indeed invalid as the only acceptable lengths are [0] and [6].

Bug #442633 should be unmarked as a duplicate of this bug. That bug deals with a message reading "Invalid PBLK length [0]". [0] is an acceptable setting for PBLK length and should not cause an error.

This bug should be marked as "Won't fix" in accordance with the findings in Bug #197267.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Moneta Funzionata (djmonkey1)]

I have marked this as "New" for the following reasons:

According to the information posted in Bug #197267, this is a problem related to incorrect BIOS in certain ASUS motherboards. A PBLK length of [5] is indeed invalid as the only acceptable lengths are [0] and [6].

As such, Bug #442633 should not be considered a duplicate of this bug. That bug deals with a message reading "Invalid PBLK length [0]". [0] is an acceptable setting for PBLK length and should not cause an error.

This bug, ACPI Invalid PBLK Length 5, should be marked as "Won't fix" in accordance with the findings in Bug #197267.

[Jeremy Foshee (jeremyfoshee)]

Moneta,
    Have you tested if this is still true for Maverick?

Thanks!

~JFo

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]