Mark C. Allman wrote:
From what I've seen googling around to several pages, this bug has been
seen before but I didn't see anyone post a solution:
orion kernel: BUG: soft lockup - CPU#0 stuck for 279s! [swapper:0]
orion kernel:
orion kernel: Pid: 0, comm: swapper
orion kernel: EIP: 0060:[<c05382e6>] CPU: 0
orion kernel: EIP is at acpi_idle_enter_simple+0x17b/0x1f1
orion kernel: EFLAGS: 00000202 Not tainted (2.6.23.9-85.fc8 #1)
orion kernel: EAX: 00000000 EBX: 0018bf91 ECX: 00000000 EDX: 00000000
orion kernel: ESI: 00000000 EDI: 00fffe6e EBP: 00e73edd DS: 007b ES:
007b FS: 00d8
orion kernel: CR0: 8005003b CR2: 090eae64 CR3: 12700000 CR4: 000006d0
orion kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
orion kernel: DR6: ffff0ff0 DR7: 00000400
orion kernel: [<c05a2399>] cpuidle_idle_call+0x5c/0x7f
orion kernel: [<c05a233d>] cpuidle_idle_call+0x0/0x7f
orion kernel: [<c040340b>] cpu_idle+0xab/0xcc
orion kernel: [<c073fa6c>] start_kernel+0x32c/0x334
orion kernel: [<c073f177>] unknown_bootoption+0x0/0x195
orion kernel: =======================
Is there a solution, or is this still a kernel bug???
This can happen for countless different reasons. This one appears to be
acpi-related, which generally means that the kernel is having difficulty with
how the BIOS is describing the hardware. A BIOS update might help, but if not,
we need to know a lot more about the hardware. Booting with acpi=off might also
fix it, but with a modern system that cripples an awful lot of functionality.
-- Chris
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
