Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I have installed Fedora 10 on HP Compaq DC7900. The first installation from Live CD makes a lot of problems. There are many kernel messages eating up the system log. I have installed this Fedora with acpi=off, and the run 'yum update'. I have the last kernel running : Fedora (2.6.27.19-170.2.35.fc10.i686). After upgrading and removing acpi=off from grug, the message [B]ACPI: Invalid PBLK length [7][/B] still appears right after boot. There is still one kernel oop left. The computer seems to work OK. What should I do ? Is it safe to use this computer with this error ? How can I get rid of it ? I am attaching my system log: How reproducible: Allways Steps to Reproduce: 1. start the computer 2. 3.
Created attachment 335886 [details] startup log
How reproducible: Allways Steps to Reproduce: 1. install Fedora Live CD with acpi=off 2. reboot 3. yum update to latest kernel 4. remove acpi=off from grub.conf 5. start the computer The first lines that appear after normal booting: ACPI: Invalid PBLK length [7] ACPI: Invalid PBLK length [7] and there is a oops in log .
Oops: Mar 19 17:04:15 localhost kernel: ------------[ cut here ]------------ Mar 19 17:04:15 localhost kernel: WARNING: at arch/x86/kernel/hpet.c:286 hpet_legacy_next_event+0x49/0x6c() (Not tainted) Mar 19 17:04:15 localhost kernel: Hardware name: HP Compaq dc7900 Convertible Minitower Mar 19 17:04:15 localhost kernel: Modules linked in: Mar 19 17:04:15 localhost kernel: Pid: 1, comm: swapper Not tainted 2.6.27.19-170.2.35.fc10.i686 #1 Mar 19 17:04:15 localhost kernel: [<c042dd93>] warn_on_slowpath+0x65/0x8b Mar 19 17:04:15 localhost kernel: [<c051a8b5>] ? __next_cpu+0x15/0x25 Mar 19 17:04:15 localhost kernel: [<c0424c7f>] ? find_busiest_group+0x2a8/0x716 Mar 19 17:04:15 localhost kernel: [<c041994d>] hpet_legacy_next_event+0x49/0x6c Mar 19 17:04:15 localhost kernel: [<c0446486>] clockevents_program_event+0xd4/0xe3 Mar 19 17:04:15 localhost kernel: [<c0447331>] tick_dev_program_event+0x28/0x95 Mar 19 17:04:15 localhost kernel: [<c0446c0a>] tick_broadcast_setup_oneshot+0xba/0xd3 Mar 19 17:04:15 localhost kernel: [<c0446c4b>] tick_broadcast_switch_to_oneshot+0x28/0x37 Mar 19 17:04:15 localhost kernel: [<c04472f3>] tick_switch_to_oneshot+0x87/0x8e Mar 19 17:04:15 localhost kernel: [<c0447307>] tick_init_highres+0xd/0xf Mar 19 17:04:15 localhost kernel: [<c04419d1>] hrtimer_run_pending+0x77/0x131 Mar 19 17:04:15 localhost kernel: [<c04362cf>] run_timer_softirq+0x1d/0x1bb Mar 19 17:04:15 localhost kernel: [<c0432757>] __do_softirq+0x84/0x109 Mar 19 17:04:15 localhost kernel: [<c04326d3>] ? __do_softirq+0x0/0x109 Mar 19 17:04:15 localhost kernel: [<c0406f1c>] do_softirq+0x77/0xdb Mar 19 17:04:15 localhost kernel: [<c046617b>] ? handle_edge_irq+0x0/0xf4 Mar 19 17:04:15 localhost kernel: [<c04323be>] irq_exit+0x44/0x83 Mar 19 17:04:15 localhost kernel: [<c0406e8e>] do_IRQ+0xe7/0xfe Mar 19 17:04:15 localhost kernel: [<c0405668>] common_interrupt+0x28/0x30 Mar 19 17:04:15 localhost kernel: [<c051fc22>] ? delay_tsc+0x2c/0x59 Mar 19 17:04:15 localhost kernel: [<c051fc98>] ? __const_udelay+0x2f/0x31 Mar 19 17:04:15 localhost kernel: [<c051fc98>] __const_udelay+0x2f/0x31 Mar 19 17:04:15 localhost kernel: [<c0839b14>] isapnp_init+0x15d/0xca1 Mar 19 17:04:15 localhost kernel: [<c051c2b3>] ? kobject_uevent_env+0x2ef/0x310 Mar 19 17:04:15 localhost kernel: [<c051c2b3>] ? kobject_uevent_env+0x2ef/0x310 Mar 19 17:04:15 localhost kernel: [<c051c2de>] ? kobject_uevent+0xa/0xc Mar 19 17:04:15 localhost kernel: [<c0595f59>] ? bus_add_driver+0x198/0x1ba Mar 19 17:04:15 localhost kernel: [<c0596c1b>] ? driver_register+0x81/0xe1 Mar 19 17:04:15 localhost kernel: [<c0401125>] _stext+0x3d/0x115 Mar 19 17:04:15 localhost kernel: [<c08399b7>] ? isapnp_init+0x0/0xca1 Mar 19 17:04:15 localhost kernel: [<c0466b98>] ? register_irq_proc+0x92/0xae Mar 19 17:04:15 localhost kernel: [<c0466bf1>] ? init_irq_proc+0x3d/0x4a Mar 19 17:04:15 localhost kernel: [<c0818362>] kernel_init+0x177/0x1c5 Mar 19 17:04:15 localhost kernel: [<c08181eb>] ? kernel_init+0x0/0x1c5 Mar 19 17:04:15 localhost kernel: [<c040590b>] kernel_thread_helper+0x7/0x10 Mar 19 17:04:15 localhost kernel: =======================
Created attachment 337152 [details] Fedora 11 alpha log I have tried to use Fedora 11 alpha with the latest kernel: Linux version 2.6.29-0.66.rc3.fc11.i686 I still get the same message: ACPI: Invalid PBLK length [7] , in log and on the start-up screen, when Fedora starts ;( Is it safe to use computer with this error ?
Created attachment 337154 [details] 2.6.28-11.37 kernel I have tried to install Ubuntu 2.6.28-11.37-generic (Ubuntu 9.04 beta) to see what happens ... still the same ACPI error ... I am attaching the startup log ... Should I attach anything else ?
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.