From: Darren Hart <dvhltc@us.ibm.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>,
"lkml, " <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mi
Subject: 2.6.31-rc4-rt1: BUG: panic in requeue_pi test case
Date: Tue, 04 Aug 2009 07:37:45 -0700 [thread overview]
Message-ID: <4A7847B9.5050907@us.ibm.com> (raw)
Using a slightly modified version of pthread_cond_many from
ltp/testcases/realtime/perf/latency I tripped over the following crash
while using a patched glibc to make use of the new futex requeue_pi
syscalls. The changes to the test boil down to making the "child_mutex"
PI aware. The unmodified test ran for 10 hours using the old futex
behavior (stock glibc). I'll do some more investigation and see if I
can reproduce on mainline, or on a 2.6.29 rt kernel.
Kernel panic - not syncing: softlockup: hung tasks
BUG: soft lockup - CPU#5 stuck for 61s! [pthread_cond_ma:30534]
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Call Trace:
[<ffffffff813fe78a>] ? rt_spin_lock_slowlock+0xdb/0x1b9
[<ffffffff813fe6af>] ? rt_spin_lock_slowlock+0x0/0x1b9
[<ffffffff8108de6d>] ? rt_spin_lock_fastlock+0x77/0x93
[<ffffffff813feddf>] ? rt_spin_lock+0x28/0x3e
[<ffffffff8108a6c8>] ? queue_lock+0x46/0x66
[<ffffffff8108bcc0>] ? futex_lock_pi+0xf9/0x2c1
[<ffffffff8113a59b>] ? __pollwait+0x0/0x107
[<ffffffff813ff581>] ? _atomic_spin_unlock_irqrestore+0x49/0x68
[<ffffffff8108e296>] ? rt_mutex_adjust_prio+0x49/0x68
[<ffffffff8108ddc5>] ? rt_spin_lock_fastunlock+0x54/0x85
[<ffffffff8108cc43>] ? do_futex+0x7e2/0xb41
[<ffffffff810421a0>] ? pick_next_task_idle+0x2b/0x4d
[<ffffffff81060809>] ? timespec_add_safe+0x4b/0x94
[<ffffffff8100cdde>] ? apic_timer_interrupt+0xe/0x20
[<ffffffff8108d0c7>] ? sys_futex+0x125/0x157
[<ffffffff8100c29b>] ? system_call_fastpath+0x16/0x1b
Kernel panic - not syncing: softlockup: hung tasks
BUG: soft lockup - CPU#6 stuck for 61s! [pthread_cond_ma:30536]
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Call Trace:
[<ffffffff813fe78a>] ? rt_spin_lock_slowlock+0xdb/0x1b9
[<ffffffff813fe6af>] ? rt_spin_lock_slowlock+0x0/0x1b9
[<ffffffff8108de6d>] ? rt_spin_lock_fastlock+0x77/0x93
[<ffffffff813feddf>] ? rt_spin_lock+0x28/0x3e
[<ffffffff8108a6c8>] ? queue_lock+0x46/0x66
[<ffffffff8108bcc0>] ? futex_lock_pi+0xf9/0x2c1
[<ffffffff8113a59b>] ? __pollwait+0x0/0x107
[<ffffffff8108e296>] ? rt_mutex_adjust_prio+0x49/0x68
[<ffffffff813fe692>] ? rt_spin_lock_slowunlock+0x6f/0x8c
[<ffffffff813fe623>] ? rt_spin_lock_slowunlock+0x0/0x8c
[<ffffffff8108ddd9>] ? rt_spin_lock_fastunlock+0x68/0x85
[<ffffffff8108cc43>] ? do_futex+0x7e2/0xb41
[<ffffffff810421a0>] ? pick_next_task_idle+0x2b/0x4d
[<ffffffff81060809>] ? timespec_add_safe+0x4b/0x94
[<ffffffff8100cdde>] ? apic_timer_interrupt+0xe/0x20
[<ffffffff8108d0c7>] ? sys_futex+0x125/0x157
[<ffffffff8100c29b>] ? system_call_fastpath+0x16/0x1b
Kernel panic - not syncing: softlockup: hung tasks
BUG: soft lockup - CPU#7 stuck for 61s! [pthread_cond_ma:30537]
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Call Trace:
[<ffffffff813fe78a>] ? rt_spin_lock_slowlock+0xdb/0x1b9
[<ffffffff813fe6af>] ? rt_spin_lock_slowlock+0x0/0x1b9
[<ffffffff8108de6d>] ? rt_spin_lock_fastlock+0x77/0x93
[<ffffffff813feddf>] ? rt_spin_lock+0x28/0x3e
[<ffffffff8108a6c8>] ? queue_lock+0x46/0x66
[<ffffffff8108bcc0>] ? futex_lock_pi+0xf9/0x2c1
[<ffffffff8113a59b>] ? __pollwait+0x0/0x107
[<ffffffff8108e296>] ? rt_mutex_adjust_prio+0x49/0x68
[<ffffffff813fe692>] ? rt_spin_lock_slowunlock+0x6f/0x8c
[<ffffffff813fe623>] ? rt_spin_lock_slowunlock+0x0/0x8c
[<ffffffff8108ddd9>] ? rt_spin_lock_fastunlock+0x68/0x85
[<ffffffff8108cc43>] ? do_futex+0x7e2/0xb41
[<ffffffff810421a0>] ? pick_next_task_idle+0x2b/0x4d
[<ffffffff81060809>] ? timespec_add_safe+0x4b/0x94
[<ffffffff8108d0c7>] ? sys_futex+0x125/0x157
[<ffffffff8100c29b>] ? system_call_fastpath+0x16/0x1b
Kernel panic - not syncing: softlockup: hung tasks
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhltc@us.ibm.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>,
"lkml, " <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Dinakar Guniguntala <dino@in.ibm.com>
Subject: 2.6.31-rc4-rt1: BUG: panic in requeue_pi test case
Date: Tue, 04 Aug 2009 07:37:45 -0700 [thread overview]
Message-ID: <4A7847B9.5050907@us.ibm.com> (raw)
Using a slightly modified version of pthread_cond_many from
ltp/testcases/realtime/perf/latency I tripped over the following crash
while using a patched glibc to make use of the new futex requeue_pi
syscalls. The changes to the test boil down to making the "child_mutex"
PI aware. The unmodified test ran for 10 hours using the old futex
behavior (stock glibc). I'll do some more investigation and see if I
can reproduce on mainline, or on a 2.6.29 rt kernel.
Kernel panic - not syncing: softlockup: hung tasks
BUG: soft lockup - CPU#5 stuck for 61s! [pthread_cond_ma:30534]
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Call Trace:
[<ffffffff813fe78a>] ? rt_spin_lock_slowlock+0xdb/0x1b9
[<ffffffff813fe6af>] ? rt_spin_lock_slowlock+0x0/0x1b9
[<ffffffff8108de6d>] ? rt_spin_lock_fastlock+0x77/0x93
[<ffffffff813feddf>] ? rt_spin_lock+0x28/0x3e
[<ffffffff8108a6c8>] ? queue_lock+0x46/0x66
[<ffffffff8108bcc0>] ? futex_lock_pi+0xf9/0x2c1
[<ffffffff8113a59b>] ? __pollwait+0x0/0x107
[<ffffffff813ff581>] ? _atomic_spin_unlock_irqrestore+0x49/0x68
[<ffffffff8108e296>] ? rt_mutex_adjust_prio+0x49/0x68
[<ffffffff8108ddc5>] ? rt_spin_lock_fastunlock+0x54/0x85
[<ffffffff8108cc43>] ? do_futex+0x7e2/0xb41
[<ffffffff810421a0>] ? pick_next_task_idle+0x2b/0x4d
[<ffffffff81060809>] ? timespec_add_safe+0x4b/0x94
[<ffffffff8100cdde>] ? apic_timer_interrupt+0xe/0x20
[<ffffffff8108d0c7>] ? sys_futex+0x125/0x157
[<ffffffff8100c29b>] ? system_call_fastpath+0x16/0x1b
Kernel panic - not syncing: softlockup: hung tasks
BUG: soft lockup - CPU#6 stuck for 61s! [pthread_cond_ma:30536]
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Call Trace:
[<ffffffff813fe78a>] ? rt_spin_lock_slowlock+0xdb/0x1b9
[<ffffffff813fe6af>] ? rt_spin_lock_slowlock+0x0/0x1b9
[<ffffffff8108de6d>] ? rt_spin_lock_fastlock+0x77/0x93
[<ffffffff813feddf>] ? rt_spin_lock+0x28/0x3e
[<ffffffff8108a6c8>] ? queue_lock+0x46/0x66
[<ffffffff8108bcc0>] ? futex_lock_pi+0xf9/0x2c1
[<ffffffff8113a59b>] ? __pollwait+0x0/0x107
[<ffffffff8108e296>] ? rt_mutex_adjust_prio+0x49/0x68
[<ffffffff813fe692>] ? rt_spin_lock_slowunlock+0x6f/0x8c
[<ffffffff813fe623>] ? rt_spin_lock_slowunlock+0x0/0x8c
[<ffffffff8108ddd9>] ? rt_spin_lock_fastunlock+0x68/0x85
[<ffffffff8108cc43>] ? do_futex+0x7e2/0xb41
[<ffffffff810421a0>] ? pick_next_task_idle+0x2b/0x4d
[<ffffffff81060809>] ? timespec_add_safe+0x4b/0x94
[<ffffffff8100cdde>] ? apic_timer_interrupt+0xe/0x20
[<ffffffff8108d0c7>] ? sys_futex+0x125/0x157
[<ffffffff8100c29b>] ? system_call_fastpath+0x16/0x1b
Kernel panic - not syncing: softlockup: hung tasks
BUG: soft lockup - CPU#7 stuck for 61s! [pthread_cond_ma:30537]
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Modules linked in: ipv6 autofs4 i2c_dev i2c_core hidp rfcomm l2cap
bluetooth rfkill sunrpc dm_mirror dm_multipath scsi_dh video output sbs
sbshc battery ac parport_pc lp parport sg snd_seq_dummy snd_seq_oss
button serio_raw bnx2 bnx2x snd_seq_midi_event snd_seq i5k_amb hwmon
crc32c snd_seq_device i5000_edac pata_acpi snd_pcm_oss iTCO_wdt
ata_generic snd_mixer_oss edac_core iTCO_vendor_support libcrc32c
snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr dm_region_hash
dm_log dm_mod ata_piix libata shpchp mptsas mptscsih mptbase
scsi_transport_sas sd_mod scsi_mod crc_t10dif ext3 jbd mbcache uhci_hcd
ohci_hcd ehci_hcd
Call Trace:
[<ffffffff813fe78a>] ? rt_spin_lock_slowlock+0xdb/0x1b9
[<ffffffff813fe6af>] ? rt_spin_lock_slowlock+0x0/0x1b9
[<ffffffff8108de6d>] ? rt_spin_lock_fastlock+0x77/0x93
[<ffffffff813feddf>] ? rt_spin_lock+0x28/0x3e
[<ffffffff8108a6c8>] ? queue_lock+0x46/0x66
[<ffffffff8108bcc0>] ? futex_lock_pi+0xf9/0x2c1
[<ffffffff8113a59b>] ? __pollwait+0x0/0x107
[<ffffffff8108e296>] ? rt_mutex_adjust_prio+0x49/0x68
[<ffffffff813fe692>] ? rt_spin_lock_slowunlock+0x6f/0x8c
[<ffffffff813fe623>] ? rt_spin_lock_slowunlock+0x0/0x8c
[<ffffffff8108ddd9>] ? rt_spin_lock_fastunlock+0x68/0x85
[<ffffffff8108cc43>] ? do_futex+0x7e2/0xb41
[<ffffffff810421a0>] ? pick_next_task_idle+0x2b/0x4d
[<ffffffff81060809>] ? timespec_add_safe+0x4b/0x94
[<ffffffff8108d0c7>] ? sys_futex+0x125/0x157
[<ffffffff8100c29b>] ? system_call_fastpath+0x16/0x1b
Kernel panic - not syncing: softlockup: hung tasks
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
next reply other threads:[~2009-08-04 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 14:37 Darren Hart [this message]
2009-08-04 14:37 ` 2.6.31-rc4-rt1: BUG: panic in requeue_pi test case Darren Hart
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=4A7847B9.5050907@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.