Bug 427676 - soft lockup in ACPI?
Summary: soft lockup in ACPI?
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-01-06 16:27 UTC by David Dillow
Modified: 2009-01-09 05:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-01-09 05:42:54 UTC

Attachments (Terms of Use)

Description David Dillow 2008-01-06 16:27:34 UTC
Description of problem:
Machine goes away for almost 5 minutes, then dumps this in the log:

BUG: soft lockup - CPU#0 stuck for 277s! [fnfxd:1832]

Pid: 1832, comm:                fnfxd
EIP: 0060:[<c0526e2e>] CPU: 0
EIP is at acpi_ns_lookup+0x1ee/0x309
 EFLAGS: 00200202    Not tainted  ( #1)
EAX: 00000000 EBX: dec4b618 ECX: dec52030 EDX: d3337c44
ESI: 00000000 EDI: df8035c7 EBP: 00000000 DS: 007b ES: 007b FS: 00d8
CR0: 8005003b CR2: 005e3054 CR3: 196d8000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
 [<c0529242>] acpi_ps_get_next_namepath+0x88/0x1ac
 [<c051c46a>] acpi_ds_is_result_used+0x3f/0xfb
 [<c0529525>] acpi_ps_get_next_arg+0x1bf/0x222
 [<c051900f>] acpi_os_release_object+0x5/0x8
 [<c0529bf5>] acpi_ps_complete_op+0x1c5/0x1d9
 [<c052a058>] acpi_ps_parse_loop+0x44f/0x737
 [<c051bae8>] acpi_ds_call_control_method+0x104/0x15b
 [<c052960e>] acpi_ps_parse_aml+0x60/0x237
 [<c051d328>] acpi_ds_init_aml_walk+0xb4/0xfe
 [<c052a83c>] acpi_ps_execute_method+0x111/0x1b1
 [<c0527bdd>] acpi_ns_evaluate+0x99/0xf0
 [<c0527837>] acpi_evaluate_object+0x142/0x1e7
 [<dfb7a185>] hci_raw+0x74/0xac [toshiba_acpi]
 [<c048fffc>] dput+0x30/0xd7
 [<c0489521>] __link_path_walk+0xa74/0xbaf
 [<c04ccc9a>] inode_has_perm+0x66/0x6e
 [<dfb7a1fd>] hci_read1+0x40/0x5e [toshiba_acpi]
 [<dfb7a405>] read_keys+0x24/0xb9 [toshiba_acpi]
 [<dfb7a019>] dispatch_read+0x19/0x4a [toshiba_acpi]
 [<dfb7a000>] dispatch_read+0x0/0x4a [toshiba_acpi]
 [<c04b272c>] proc_file_read+0x10f/0x246
 [<c04b261d>] proc_file_read+0x0/0x246
 [<c04af0be>] proc_reg_read+0x5e/0x71
 [<c04af060>] proc_reg_read+0x0/0x71
 [<c04817a2>] vfs_read+0xa6/0x158
 [<c0481c00>] sys_read+0x41/0x67
 [<c040518a>] syscall_call+0x7/0xb

Version-Release number of selected component (if applicable):

How reproducible:
Unsure -- I've seen a long pause before, but thought the computer had hung and
rebooted. That was with the kernel from the install CD, without fnfx installed.

Steps to Reproduce:
1. Unknown at present

Comment 1 Bug Zapper 2008-11-26 09:18:43 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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: 

Comment 2 Bug Zapper 2009-01-09 05:42:54 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.

Note You need to log in before you can comment on or make changes to this bug.