From: "Gary Funck" <gary@intrepid.com>
To: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: 2.6.17-1.2145_FC5 mmap-related soft lockup
Date: Sat, 15 Jul 2006 10:07:26 -0700 [thread overview]
Message-ID: <JCEPIPKHCJGDMPOHDOIGGEKJDFAA.gary@intrepid.com> (raw)
A test program which allocates about 256M of MAP_ANONYMOUS mmap memory,
and then spawns 4 processess, where each process i writes to 1/4 of the
mapped memory, and then reads the memory written by
the process (i + 1)%4, triggers a soft lockup, when exiting.
Hardware:
dual core dual Opteron 275 (Tyan motherboard, 4G physical memory)
has been rock solid reliable.
BUG: soft lockup detected on CPU#3!
Call Trace: <IRQ> <ffffffff802b2fb5>{softlockup_tick+219}
<ffffffff8029708e>{update_process_times+66}
<ffffffff8027a3ed>{smp_local_timer_interrupt+35}
<ffffffff8027aa95>{smp_apic_timer_interrupt+65}
<ffffffff80263acb>{apic_timer_interrupt+135} <EOI>
<ffffffff8020e578>{__set_page_dirty_nobuffers+0}
<ffffffff8026a128>{_write_unlock_irq+11}
<ffffffff8020e62d>{__set_page_dirty_nobuffers+181}
<ffffffff80207af6>{unmap_vmas+1037}
<ffffffff8023c7d9>{exit_mmap+120} <ffffffff8023eda8>{mmput+44}
<ffffffff80215ece>{do_exit+599}
<ffffffff8024cacd>{debug_mutex_init+0}
<ffffffff80262f01>{tracesys+209}
BUG: soft lockup detected on CPU#0!
Call Trace: <IRQ> <ffffffff802b2fb5>{softlockup_tick+219}
<ffffffff8029708e>{update_process_times+66}
<ffffffff8027a3ed>{smp_local_timer_interrupt+35}
<ffffffff8027aa95>{smp_apic_timer_interrupt+65}
<ffffffff80263acb>{apic_timer_interrupt+135} <EOI>
<ffffffff8020e578>{__set_page_dirty_nobuffers+0}
<ffffffff8026a128>{_write_unlock_irq+11}
<ffffffff8020e62d>{__set_page_dirty_nobuffers+181}
<ffffffff80207af6>{unmap_vmas+1037}
<ffffffff8023c7d9>{exit_mmap+120} <ffffffff8023eda8>{mmput+44}
<ffffffff80215ece>{do_exit+599}
<ffffffff8024cacd>{debug_mutex_init+0}
<ffffffff80262f01>{tracesys+209}
BUG: soft lockup detected on CPU#2!
Call Trace: <IRQ> <ffffffff802b2fb5>{softlockup_tick+219}
<ffffffff8029708e>{update_process_times+66}
<ffffffff8027a3ed>{smp_local_timer_interrupt+35}
<ffffffff8027aa95>{smp_apic_timer_interrupt+65}
<ffffffff80263acb>{apic_timer_interrupt+135} <EOI>
<ffffffff8020e578>{__set_page_dirty_nobuffers+0}
<ffffffff8026a128>{_write_unlock_irq+11}
<ffffffff8020e62d>{__set_page_dirty_nobuffers+181}
<ffffffff80207af6>{unmap_vmas+1037}
<ffffffff8023c7d9>{exit_mmap+120} <ffffffff8023eda8>{mmput+44}
<ffffffff80215ece>{do_exit+599}
<ffffffff8024cacd>{debug_mutex_init+0}
<ffffffff80262f01>{tracesys+209}
BUG: soft lockup detected on CPU#1!
Call Trace: <IRQ> <ffffffff802b2fb5>{softlockup_tick+219}
<ffffffff8029708e>{update_process_times+66}
<ffffffff8027a3ed>{smp_local_timer_interrupt+35}
<ffffffff8027aa95>{smp_apic_timer_interrupt+65}
<ffffffff80263acb>{apic_timer_interrupt+135} <EOI>
<ffffffff8020e578>{__set_page_dirty_nobuffers+0}
<ffffffff8026a128>{_write_unlock_irq+11}
<ffffffff8020e62d>{__set_page_dirty_nobuffers+181}
<ffffffff80207af6>{unmap_vmas+1037}
<ffffffff8023c7d9>{exit_mmap+120} <ffffffff8023eda8>{mmput+44}
<ffffffff80215ece>{do_exit+599}
<ffffffff8024cacd>{debug_mutex_init+0}
<ffffffff80262f01>{tracesys+209}
The test program runs successfully, but hangs several seconds upon exit.
The hardware and software configuration has been solid for several months,
but
we have seen timer-related synchronization issues with recent kernels (where
ntp has to force a re-sync for example, and an occasional lost ticks
message).
The test program mentioned above is more complicated than described, and
can't easily be reproduced in source form, but the binary could be
made available.
next reply other threads:[~2006-07-15 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 17:07 Gary Funck [this message]
2006-07-16 5:19 ` 2.6.17-1.2145_FC5 mmap-related soft lockup Andrew Morton
2006-07-19 2:25 ` Gary Funck
2006-07-19 4:04 ` Andrew Morton
2006-07-16 6:50 ` Gary Funck
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=JCEPIPKHCJGDMPOHDOIGGEKJDFAA.gary@intrepid.com \
--to=gary@intrepid.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