mm snapshot broken-out-2006-08-24-00-22.tar.gz uploaded
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi,
Quoted 5 lines · On 24/08/06, [email protected] <[email protected]> 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.gzIt 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/0x300xc0103cb8 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
Signature · 3 lines
Michal K. K. Piotrowski LTG - Linux Testers Group (http://www.stardust.webpages.pl/ltg/wiki/)
Quoted 23 lines · On Thu, 24 Aug 2006 13:52:28 +0200 "Michal Piotrowski"…
Hi,
Quoted 5 lines · On 24/08/06, [email protected] <[email protected]> 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.gzIt 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
Quoted 1 line
Leftover inexact backtrace:
Sigh, useless.
Quoted 6 lines
[<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
Quoted 8 lines
[<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
There are a couple of recent futex changes, but they're fairly innocent-looking. What is the workload?
Quoted 46 lines · Andrew Morton
Quoted 23 lines · On Thu, 24 Aug 2006 13:52:28 +0200 "Michal Piotrowski"…
Hi,
Quoted 5 lines · On 24/08/06, [email protected] <[email protected]> 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.gzIt 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/0x30Quoted 1 line
Leftover inexact backtrace:
Sigh, useless.
Quoted 6 lines
[<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/0x65Quoted 8 lines
[<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
Quoted 4 lines
There are a couple of recent futex changes, but they're fairly innocent-looking. What is the workload?
This script -> http://www.stardust.webpages.pl/files/mm/2.6.18-rc4-mm3/test_mount_fs.sh
+ Amarok.
ls -sh /home/fs-farm/
razem 3,6G
513M ext2.img 513M ext3.img 513M ext4.img 513M jfs.img 513M reiser3.img 513M reiser4.img 513M xfs.img
Regards,
Michal
Signature · 3 lines
Michal K. K. Piotrowski LTG - Linux Testers Group (http://www.stardust.webpages.pl/ltg/wiki/)
Quoted 5 lines · On 24/08/06, [email protected] <[email protected]> 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.gzIt contains the following patches against 2.6.18-rc4:
Filesystem "loop4": Disabling barriers, not supported by the underlying device XFS mounting filesystem loop4
Slab corruption: start=ef135b6c, len=304
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<fdd1c363>](xfs_buf_free+0xb8/0xbd [xfs])
0d0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6c 6b 6b 6b
Prev obj: start=ef135a30, len=304
Redzone: 0x170fc2a5/0x170fc2a5.
Last user: [<fdd19dad>](kmem_zone_alloc+0x51/0x97 [xfs])
000: 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
010: ad 4e ad de ff ff ff ff ff ff ff ff 00 00 00 00
Next obj: start=ef135ca8, len=304
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<fdd1c363>](xfs_buf_free+0xb8/0xbd [xfs])
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
http://www.stardust.webpages.pl/files/mm/2.6.18-rc4-mm3/mm-config
Regards,
Michal
Signature · 3 lines
Michal K. K. Piotrowski LTG - Linux Testers Group (http://www.stardust.webpages.pl/ltg/wiki/)