Re: BUG: soft lockup detected on CPU#0! in 2.6.23.8
From: Erik de Castro Lopo <[EMAIL PROTECTED]> Date: Tue, 20 Nov 2007 16:22:25 +1100 > I've just compiled 2.6.23.8 from kernel.org sources and I getting a > bunch of these soft lockups detected. Yes, this is getting hit by everyone, a fix is in the works. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BUG: soft lockup detected on CPU#0! in 2.6.23.8
HI all, I've just compiled 2.6.23.8 from kernel.org sources and I getting a bunch of these soft lockups detected. This seems to be similar to the problems reported here: http://lkml.org/lkml/2007/11/19/345 but I am not as far as I am aware using the ondemand governor. > cat /proc/acpi/processor/CPU0/info processor id:0 acpi id: 0 bus mastering control: no power management:no throttling control: no limit interface: no What is suspisious is "Clocksource tsc unstable". Dump from dmsg follows. Any light people can shed on this much appreciated. Cheers, Erik [ 80.215847] Marking TSC unstable due to: cpufreq changes. [ 80.217903] Time: acpi_pm clocksource has been installed. [ 80.217908] BUG: soft lockup detected on CPU#0! [ 80.217924] [] softlockup_tick+0xbb/0xf0 [ 80.217934] [] update_process_times+0x32/0x80 [ 80.217941] [] tick_sched_timer+0x75/0x1c0 [ 80.217952] [] hrtimer_interrupt+0x170/0x1c0 [ 80.217960] [] smp_apic_timer_interrupt+0x3d/0x80 [ 80.217966] [] apic_timer_interrupt+0x28/0x30 [ 80.217973] [] pci_pcbios_init+0x18b/0x260 [ 80.217979] [] default_idle+0x2b/0x40 [ 80.217984] [] cpu_idle+0x48/0x80 [ 80.217987] [] start_kernel+0x21f/0x2a0 [ 80.217992] [] unknown_bootoption+0x0/0x1d0 [ 80.217997] === [ 80.757447] Clocksource tsc unstable (delta = -9062 ns) [ 98.773859] BUG: soft lockup detected on CPU#0! [ 98.773881] [] softlockup_tick+0xbb/0xf0 [ 98.773893] [] update_process_times+0x32/0x80 [ 98.773901] [] tick_sched_timer+0x75/0x1c0 [ 98.773913] [] hrtimer_interrupt+0x170/0x1c0 [ 98.773922] [] smp_apic_timer_interrupt+0x3d/0x80 [ 98.773930] [] apic_timer_interrupt+0x28/0x30 [ 98.773938] [] hci_sock_setsockopt+0x0/0x1b0 [ 98.773947] === [ 85.153581] BUG: soft lockup detected on CPU#0! [ 85.153602] [] softlockup_tick+0xbb/0xf0 [ 85.153614] [] update_process_times+0x32/0x80 [ 85.153621] [] tick_sched_timer+0x75/0x1c0 [ 85.153631] [] hrtimer_interrupt+0x170/0x1c0 [ 85.153639] [] smp_apic_timer_interrupt+0x3d/0x80 [ 85.153645] [] apic_timer_interrupt+0x28/0x30 [ 85.153653] [] hci_sock_setsockopt+0x0/0x1b0 [ 85.153660] === [ 72.741364] usb 1-1: reset full speed USB device using uhci_hcd and address 2 [ 99.596976] BUG: soft lockup detected on CPU#0! [ 99.596995] [] softlockup_tick+0xbb/0xf0 [ 99.597006] [] update_process_times+0x32/0x80 [ 99.597013] [] tick_sched_timer+0x75/0x1c0 [ 99.597024] [] hrtimer_interrupt+0x170/0x1c0 [ 99.597032] [] smp_apic_timer_interrupt+0x3d/0x80 [ 99.597038] [] apic_timer_interrupt+0x28/0x30 [ 99.597045] [] pci_pcbios_init+0x18b/0x260 [ 99.597050] [] default_idle+0x2b/0x40 [ 99.597054] [] cpu_idle+0x48/0x80 [ 99.597057] [] start_kernel+0x21f/0x2a0 [ 99.597063] [] unknown_bootoption+0x0/0x1d0 [ 99.597068] === [ 124.441285] BUG: soft lockup detected on CPU#0! [ 124.441305] [] softlockup_tick+0xbb/0xf0 [ 124.441315] [] update_process_times+0x32/0x80 [ 124.441323] [] tick_sched_timer+0x75/0x1c0 [ 124.441336] [] hrtimer_interrupt+0x170/0x1c0 [ 124.441345] [] smp_apic_timer_interrupt+0x3d/0x80 [ 124.441352] [] apic_timer_interrupt+0x28/0x30 [ 124.441360] [] pci_pcbios_init+0x18b/0x260 [ 124.441366] [] default_idle+0x2b/0x40 [ 124.441371] [] cpu_idle+0x48/0x80 [ 124.441375] [] start_kernel+0x21f/0x2a0 [ 124.441381] [] unknown_bootoption+0x0/0x1d0 [ 124.441388] === -- - Erik de Castro Lopo - Linux, the UNIX defragmentation tool. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BUG: soft lockup detected on CPU#0! in 2.6.23.8
HI all, I've just compiled 2.6.23.8 from kernel.org sources and I getting a bunch of these soft lockups detected. This seems to be similar to the problems reported here: http://lkml.org/lkml/2007/11/19/345 but I am not as far as I am aware using the ondemand governor. cat /proc/acpi/processor/CPU0/info processor id:0 acpi id: 0 bus mastering control: no power management:no throttling control: no limit interface: no What is suspisious is Clocksource tsc unstable. Dump from dmsg follows. Any light people can shed on this much appreciated. Cheers, Erik [ 80.215847] Marking TSC unstable due to: cpufreq changes. [ 80.217903] Time: acpi_pm clocksource has been installed. [ 80.217908] BUG: soft lockup detected on CPU#0! [ 80.217924] [c014212b] softlockup_tick+0xbb/0xf0 [ 80.217934] [c0126152] update_process_times+0x32/0x80 [ 80.217941] [c0139395] tick_sched_timer+0x75/0x1c0 [ 80.217952] [c0133e70] hrtimer_interrupt+0x170/0x1c0 [ 80.217960] [c09d] smp_apic_timer_interrupt+0x3d/0x80 [ 80.217966] [c0104bc8] apic_timer_interrupt+0x28/0x30 [ 80.217973] [c043007b] pci_pcbios_init+0x18b/0x260 [ 80.217979] [c0102fab] default_idle+0x2b/0x40 [ 80.217984] [c0103008] cpu_idle+0x48/0x80 [ 80.217987] [c041087f] start_kernel+0x21f/0x2a0 [ 80.217992] [c04102e0] unknown_bootoption+0x0/0x1d0 [ 80.217997] === [ 80.757447] Clocksource tsc unstable (delta = -9062 ns) [ 98.773859] BUG: soft lockup detected on CPU#0! [ 98.773881] [c014212b] softlockup_tick+0xbb/0xf0 [ 98.773893] [c0126152] update_process_times+0x32/0x80 [ 98.773901] [c0139395] tick_sched_timer+0x75/0x1c0 [ 98.773913] [c0133e70] hrtimer_interrupt+0x170/0x1c0 [ 98.773922] [c09d] smp_apic_timer_interrupt+0x3d/0x80 [ 98.773930] [c0104bc8] apic_timer_interrupt+0x28/0x30 [ 98.773938] [c034] hci_sock_setsockopt+0x0/0x1b0 [ 98.773947] === [ 85.153581] BUG: soft lockup detected on CPU#0! [ 85.153602] [c014212b] softlockup_tick+0xbb/0xf0 [ 85.153614] [c0126152] update_process_times+0x32/0x80 [ 85.153621] [c0139395] tick_sched_timer+0x75/0x1c0 [ 85.153631] [c0133e70] hrtimer_interrupt+0x170/0x1c0 [ 85.153639] [c09d] smp_apic_timer_interrupt+0x3d/0x80 [ 85.153645] [c0104bc8] apic_timer_interrupt+0x28/0x30 [ 85.153653] [c034] hci_sock_setsockopt+0x0/0x1b0 [ 85.153660] === [ 72.741364] usb 1-1: reset full speed USB device using uhci_hcd and address 2 [ 99.596976] BUG: soft lockup detected on CPU#0! [ 99.596995] [c014212b] softlockup_tick+0xbb/0xf0 [ 99.597006] [c0126152] update_process_times+0x32/0x80 [ 99.597013] [c0139395] tick_sched_timer+0x75/0x1c0 [ 99.597024] [c0133e70] hrtimer_interrupt+0x170/0x1c0 [ 99.597032] [c09d] smp_apic_timer_interrupt+0x3d/0x80 [ 99.597038] [c0104bc8] apic_timer_interrupt+0x28/0x30 [ 99.597045] [c043007b] pci_pcbios_init+0x18b/0x260 [ 99.597050] [c0102fab] default_idle+0x2b/0x40 [ 99.597054] [c0103008] cpu_idle+0x48/0x80 [ 99.597057] [c041087f] start_kernel+0x21f/0x2a0 [ 99.597063] [c04102e0] unknown_bootoption+0x0/0x1d0 [ 99.597068] === [ 124.441285] BUG: soft lockup detected on CPU#0! [ 124.441305] [c014212b] softlockup_tick+0xbb/0xf0 [ 124.441315] [c0126152] update_process_times+0x32/0x80 [ 124.441323] [c0139395] tick_sched_timer+0x75/0x1c0 [ 124.441336] [c0133e70] hrtimer_interrupt+0x170/0x1c0 [ 124.441345] [c09d] smp_apic_timer_interrupt+0x3d/0x80 [ 124.441352] [c0104bc8] apic_timer_interrupt+0x28/0x30 [ 124.441360] [c043007b] pci_pcbios_init+0x18b/0x260 [ 124.441366] [c0102fab] default_idle+0x2b/0x40 [ 124.441371] [c0103008] cpu_idle+0x48/0x80 [ 124.441375] [c041087f] start_kernel+0x21f/0x2a0 [ 124.441381] [c04102e0] unknown_bootoption+0x0/0x1d0 [ 124.441388] === -- - Erik de Castro Lopo - Linux, the UNIX defragmentation tool. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: soft lockup detected on CPU#0! in 2.6.23.8
From: Erik de Castro Lopo [EMAIL PROTECTED] Date: Tue, 20 Nov 2007 16:22:25 +1100 I've just compiled 2.6.23.8 from kernel.org sources and I getting a bunch of these soft lockups detected. Yes, this is getting hit by everyone, a fix is in the works. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
