From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm snapshot broken-out-2006-08-24-00-22.tar.gz uploaded
Date: Thu, 24 Aug 2006 13:52:28 +0200 [thread overview]
Message-ID: <6bffcb0e0608240452w6c17586djaab20855d9356139@mail.gmail.com> (raw)
In-Reply-To: <200608240723.k7O7NsBB025642@shell0.pdx.osdl.net>
Hi,
On 24/08/06, akpm@osdl.org <akpm@osdl.org> wrote:
> The mm snapshot broken-out-2006-08-24-00-22.tar.gz has been uploaded to
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2006-08-24-00-22.tar.gz
>
> It contains the following patches against 2.6.18-rc4:
I haven't seen this on 2.6.18-rc4-mm2. Any idea which patch is causing
this soft lockup?
BUG: soft lockup detected on CPU#0!
[<c01041b5>] dump_trace+0x64/0x1b2
[<c0104315>] show_trace_log_lvl+0x12/0x25
[<c0104985>] show_trace+0xd/0x10
[<c0104a4d>] dump_stack+0x19/0x1b
[<c014f40d>] softlockup_tick+0xc5/0xd9
[<c012a0c7>] run_local_timers+0x12/0x14
[<c012a329>] update_process_times+0x40/0x65
[<c0113cc7>] smp_apic_timer_interrupt+0x6e/0x77
[<c0103ce2>] apic_timer_interrupt+0x2a/0x30
DWARF2 unwinder stuck at apic_timer_interrupt+0x2a/0x30
Leftover inexact backtrace:
[<c0104315>] show_trace_log_lvl+0x12/0x25
[<c0104985>] show_trace+0xd/0x10
[<c0104a4d>] dump_stack+0x19/0x1b
[<c014f40d>] softlockup_tick+0xc5/0xd9
[<c012a0c7>] run_local_timers+0x12/0x14
[<c012a329>] update_process_times+0x40/0x65
[<c0113cc7>] smp_apic_timer_interrupt+0x6e/0x77
[<c0103ce2>] apic_timer_interrupt+0x2a/0x30
[<c01f3010>] __delay+0x9/0xb
[<c01ffc47>] _raw_spin_lock+0xca/0x11d
[<c02f86a8>] _spin_lock+0x2a/0x32
[<c013cc4e>] do_futex+0xee/0xd9a
[<c013d9d4>] sys_futex+0xda/0xf0
[<c01031b5>] sysenter_past_esp+0x56/0x8d
=======================
(gdb) list *apic_timer_interrupt+0x2a/0x30
0xc0103cb8 is at include2/asm/bitops.h:246.
241 static int test_bit(int nr, const volatile void * addr);
242 #endif
243
244 static __always_inline int constant_test_bit(int nr, const
volatile unsigned long *addr)
245 {
246 return ((1UL << (nr & 31)) & (addr[nr >> 5])) != 0;
247 }
248
249 static inline int variable_test_bit(int nr, const volatile
unsigned long * addr)
250 {
http://www.stardust.webpages.pl/files/mm/2.6.18-rc4-mm3/mm-config
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
next parent reply other threads:[~2006-08-24 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200608240723.k7O7NsBB025642@shell0.pdx.osdl.net>
2006-08-24 11:52 ` Michal Piotrowski [this message]
2006-08-24 14:38 ` Andrew Morton
2006-08-24 15:21 ` Michal Piotrowski
2006-08-24 12:30 ` Michal Piotrowski
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=6bffcb0e0608240452w6c17586djaab20855d9356139@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®