From: Folkert van Heusden <folkert@vanheusden.com>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: [2.6.20.1] BUG: soft lockup detected on CPU#1!
Date: Fri, 4 May 2007 16:32:58 +0200 [thread overview]
Message-ID: <20070504143258.GN7874@vanheusden.com> (raw)
In-Reply-To: <6bffcb0e0705031331y4cbfafebof9522e326a989748@mail.gmail.com>
The one of moments ago looks a little different. Still in show_trace_log but starting at a different source.
[361648.127868] usb 7-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 10 ret -110
[362269.228906] BUG: soft lockup detected on CPU#1!
[362269.228987] [<c1004d53>] show_trace_log_lvl+0x1a/0x30
[362269.229116] [<c1004d7b>] show_trace+0x12/0x14
[362269.229240] [<c1004e75>] dump_stack+0x16/0x18
[362269.229358] [<c104d52b>] softlockup_tick+0xa6/0xc2
[362269.229477] [<c10267ae>] run_local_timers+0x12/0x14
[362269.229585] [<c10265dc>] update_process_times+0x72/0xa1
[362269.229702] [<c1038390>] tick_sched_timer+0x53/0xb6
[362269.229817] [<c1033ba8>] hrtimer_interrupt+0x16b/0x1c2
[362269.229939] [<c100e9e2>] local_apic_timer_interrupt+0x55/0x5b
[362269.230065] [<c100ea12>] smp_apic_timer_interrupt+0x2a/0x39
[362269.230189] [<c1004a3f>] apic_timer_interrupt+0x33/0x38
[362269.230312] [<c120fdfc>] error_code+0x7c/0x84
[362269.230431] [<c1099fbf>] padzero+0x1f/0x2d
[362269.230547] [<c109a6c6>] load_elf_interp+0x200/0x2a3
[362269.230663] [<c109b17d>] load_elf_binary+0x838/0xc38
[362269.230780] [<c1073b20>] search_binary_handler+0x94/0x20a
[362269.230886] [<c1073df6>] do_execve+0x160/0x1ee
[362269.230977] [<c1002ce9>] sys_execve+0x32/0x8b
[362269.231065] [<c1003f74>] syscall_call+0x7/0xb
[362269.231155] =======================
On Thu, May 03, 2007 at 10:31:23PM +0200, Michal Piotrowski wrote:
> On 03/05/07, Folkert van Heusden <folkert@vanheusden.com> wrote:
> >My P4 with HT and 2GB of ram on an IDE disk succeeded in triggering
> >another bug:
> >
> >[273187.872796] usb 7-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt
> >161 rq 1 len 10 ret -110
> >[273902.586320] BUG: soft lockup detected on CPU#1!
> >[273902.586385] [<c1004d53>] show_trace_log_lvl+0x1a/0x30
> >[273902.586472] [<c1004d7b>] show_trace+0x12/0x14
> >[273902.586557] [<c1004e75>] dump_stack+0x16/0x18
> >[273902.586636] [<c104d52b>] softlockup_tick+0xa6/0xc2
> >[273902.586724] [<c10267ae>] run_local_timers+0x12/0x14
> >[273902.586810] [<c10265dc>] update_process_times+0x72/0xa1
> >[273902.586893] [<c1038390>] tick_sched_timer+0x53/0xb6
> >[273902.586977] [<c1033ba8>] hrtimer_interrupt+0x16b/0x1c2
> >[273902.587062] [<c100e9e2>] local_apic_timer_interrupt+0x55/0x5b
> >[273902.587147] [<c100ea12>] smp_apic_timer_interrupt+0x2a/0x39
> >[273902.587230] [<c1004a3f>] apic_timer_interrupt+0x33/0x38
> >[273902.587312] [<c10020f2>] cpu_idle+0x6b/0x85
> >[273902.587393] [<c130b218>] start_secondary+0xe8/0x30a
> >[273902.587476] [<00000000>] 0x0
> >[273902.587568] =======================
> >[277740.475464] usb 7-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt
> >161 rq 1 len 10 ret -110
> >...
> >[285799.322391] usb 7-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt
> >161 rq 1 len 10 ret -110
> >[286630.885843] BUG: soft lockup detected on CPU#1!
> >[286630.885901] [<c1004d53>] show_trace_log_lvl+0x1a/0x30
> >[286630.885988] [<c1004d7b>] show_trace+0x12/0x14
> >[286630.886071] [<c1004e75>] dump_stack+0x16/0x18
> >[286630.886152] [<c104d52b>] softlockup_tick+0xa6/0xc2
> >[286630.886235] [<c10267ae>] run_local_timers+0x12/0x14
> >[286630.886323] [<c10265dc>] update_process_times+0x72/0xa1
> >[286630.886406] [<c1038390>] tick_sched_timer+0x53/0xb6
> >[286630.886488] [<c1033ba8>] hrtimer_interrupt+0x16b/0x1c2
> >[286630.886571] [<c100e9e2>] local_apic_timer_interrupt+0x55/0x5b
> >[286630.886657] [<c100ea12>] smp_apic_timer_interrupt+0x2a/0x39
> >[286630.886741] [<c1004a3f>] apic_timer_interrupt+0x33/0x38
> >[286630.886824] [<c10020f2>] cpu_idle+0x6b/0x85
> >[286630.886907] [<c130b218>] start_secondary+0xe8/0x30a
> >[286630.886991] [<00000000>] 0x0
> >[286630.887088] =======================
> >[290177.972351] usb 7-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt
> >161 rq 1 len 10 ret -110
> >
> >My .config can be found here:
> >http://keetweej.vanheusden.com/~folkert/config-2.6.21.1
> >
> >
> >Folkert van Heusden
> >
>
> Thomas, this looks very similar to
> http://lkml.org/lkml/2007/5/2/511
>
> Already on list of known regressions.
>
> Regards,
> Michal
>
> --
> Michal K. K. Piotrowski
> Kernel Monkeys
> (http://kernel.wikidot.com/start)
Folkert van Heusden
--
www.vanheusden.com/multitail - win een vlaai van multivlaai! zorg
ervoor dat multitail opgenomen wordt in Fedora Core, AIX, Solaris of
HP/UX en win een vlaai naar keuze
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
prev parent reply other threads:[~2007-05-04 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 19:11 [2.6.20.1] BUG: soft lockup detected on CPU#1! Folkert van Heusden
2007-05-03 20:31 ` Michal Piotrowski
2007-05-04 14:32 ` Folkert van Heusden [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070504143258.GN7874@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox