public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Folkert van Heusden <folkert@vanheusden.com>
To: linux-kernel@vger.kernel.org
Subject: [2.6.20.1] BUG: soft lockup detected on CPU#1!
Date: Thu, 3 May 2007 21:11:20 +0200	[thread overview]
Message-ID: <20070503191120.GW7874@vanheusden.com> (raw)

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

-- 
MultiTail cok yonlu kullanimli bir program, loglari okumak, verilen
kommandolari yerine getirebilen. Filter, renk verme, merge, 'diff-
view', vs.  http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

             reply	other threads:[~2007-05-03 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 19:11 Folkert van Heusden [this message]
2007-05-03 20:31 ` [2.6.20.1] BUG: soft lockup detected on CPU#1! Michal Piotrowski
2007-05-04 14:32   ` Folkert van Heusden

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=20070503191120.GW7874@vanheusden.com \
    --to=folkert@vanheusden.com \
    --cc=linux-kernel@vger.kernel.org \
    /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