Bug#476523: CPU Soft lock with SMP on 4.0r3
reassign 476523 linux-2.6
thanks
On Thu, Apr 17, 2008 at 12:01:41PM +0200, Stephan A. Rickauer wrote:
> Package: kernel
> Version: 2.6.18-6-amd64
> Severity: important
>
> A newly purchased dual-core amd64 machine regularely locks up. This can
> be reproduced by doing massive kernel builds.
>
> I've already played with all the ACPI and APIC knobs in the BIOS,
> deactivated also USB, sound and such, with no luck. Also booting with
> noapic wouldn't remedy the lock-ups. A BIOS upgrade didn't help either.
>
> Here's the error message output. Find a full dmesg further below. The
> detailed hardware is listed at the end of this long email:
>
> BUG: soft lockup detected on CPU#1!
>
> Call Trace:
> <IRQ> [<ffffffff802a3673>] softlockup_tick+0xdb/0xed
> [<ffffffff802878d5>] update_process_times+0x42/0x68
> [<ffffffff8026c2b5>] smp_local_timer_interrupt+0x23/0x47
> [<ffffffff8026c9a9>] smp_apic_timer_interrupt+0x41/0x47
> [<ffffffff8025874a>] apic_timer_interrupt+0x66/0x6c
> <EOI> [<ffffffff8025df39>] _spin_unlock_irqrestore+0x8/0x9
> [<ffffffff8020b2c3>] __down_read_trylock+0x3e/0x44
> [<ffffffff8020a5ed>] do_page_fault+0x2ee/0x706
> [<ffffffff80214ba8>] prio_tree_insert+0x148/0x231
> [<ffffffff802588a5>] error_exit+0x0/0x84
> [<ffffffff8022ceb7>] __clear_user+0x16/0x34
> [<ffffffff8027546d>] padzero+0x1b/0x2b
> [<ffffffff8021698e>] load_elf_binary+0xa56/0x19b7
> [<ffffffff8020de4a>] __alloc_pages+0x5c/0x2a9
> [<ffffffff8020de4a>] __alloc_pages+0x5c/0x2a9
> [<ffffffff80215aca>] copy_strings+0x167/0x1bc
> [<ffffffff8023d3ad>] search_binary_handler+0xa8/0x254
> [<ffffffff8023ca12>] do_execve+0x18c/0x242
> [<ffffffff80250394>] sys_execve+0x36/0x90
> [<ffffffff80257f8f>] stub_execve+0x67/0xb0
>
> BUG: soft lockup detected on CPU#0!
>
> Call Trace:
> <IRQ> [<ffffffff802a3673>] softlockup_tick+0xdb/0xed
> [<ffffffff802878d5>] update_process_times+0x42/0x68
> [<ffffffff8026c2b5>] smp_local_timer_interrupt+0x23/0x47
> [<ffffffff8026c9a9>] smp_apic_timer_interrupt+0x41/0x47
> [<ffffffff8025874a>] apic_timer_interrupt+0x66/0x6c
> <EOI> [<ffffffff80229602>] flush_tlb_page+0x4a/0xbc
> [<ffffffff80208c8d>] __handle_mm_fault+0x8ea/0x91a
> [<ffffffff8020a69c>] do_page_fault+0x39d/0x706
> [<ffffffff802588a5>] error_exit+0x0/0x84
> [<ffffffff8025b507>] copy_user_generic_c+0xd/0x26
> [<ffffffff802171a7>] load_elf_binary+0x126f/0x19b7
> [<ffffffff8023d3ad>] search_binary_handler+0xa8/0x254
> [<ffffffff8023ca12>] do_execve+0x18c/0x242
> [<ffffffff80250394>] sys_execve+0x36/0x90
> [<ffffffff80257f8f>] stub_execve+0x67/0xb0
>
> BUG: soft lockup detected on CPU#0!
>
> Call Trace:
> <IRQ> [<ffffffff802a3673>] softlockup_tick+0xdb/0xed
> [<ffffffff802878d5>] update_process_times+0x42/0x68
> [<ffffffff8026c2b5>] smp_local_timer_interrupt+0x23/0x47
> [<ffffffff8026c9a9>] smp_apic_timer_interrupt+0x41/0x47
> [<ffffffff8025874a>] apic_timer_interrupt+0x66/0x6c
> <EOI> [<ffffffff80257bd6>] system_call+0x7e/0x83
> [<ffffffff802084ef>] __handle_mm_fault+0x14c/0x91a
> [<ffffffff80208c8d>] __handle_mm_fault+0x8ea/0x91a
> [<ffffffff80257bd6>] system_call+0x7e/0x83
> [<ffffffff8020a69c>] do_page_fault+0x39d/0x706
> [<ffffffff80257bd6>] system_call+0x7e/0x83
> [<ffffffff80257bd6>] system_call+0x7e/0x83
> [<ffffffff8020aa02>] do_page_fault+0x703/0x706
> [<ffffffff802588a5>] error_exit+0x0/0x84
> [<ffffffff80257bd6>] system_call+0x7e/0x83
> [<ffffffff8025b7c0>] __put_user_4+0x20/0x30
> [<ffffffff802255c1>] schedule_tail+0x99/0x9e
> [<ffffffff80257acc>] ret_from_fork+0xc/0x25
>
> dmesg:
>
[..]
>
>
> Hardware used:
>
> CPU AMD Athlon X2 BE-2400/2300MHz
> ASUS M2N-MX SE+,mATX,nVidia GeForce 6100 (bios level 0503)
> Kingston Memory DDR2 4GB Kit, PC2-6400800MHz, CL5, Non-ECC
> 2x Hitachi Deskstar P7K500, 250GB, SATA-II, 8.5ms,7200 RPM, 8MB, 8.5ms
>
> Thanks for your help!
Does this error still occur with more recent kernel versions?
If you're running Etch, could you try to reproduce this bug
with the 2.6.24 based kernel added in 4.0r4?
http://packages.qa.debian.org/l/linux-2.6.24.html
Cheers,
Moritz
Reply to: