From: Andrew Morton <akpm@osdl.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: dhowells@redhat.com, torvalds@osdl.org, arjan@infradead.org,
suparna@in.ibm.com, linux-aio@kvack.org,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] rwsem: Make rwsems use interrupt disabling spinlocks
Date: Wed, 9 Mar 2005 11:42:34 -0800 [thread overview]
Message-ID: <20050309114234.6598f486.akpm@osdl.org> (raw)
In-Reply-To: <1110395783.24286.207.camel@dyn318077bld.beaverton.ibm.com>
Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
> I am not sure if this is related to your patch. But I ran into
> BUG() with sysrq-t with your patch.
>
> Thanks,
> Badari
>
> BUG: soft lockup detected on CPU#1!
>
> Modules linked in: joydev sg st floppy usbserial parport_pc lp parport
> ipv6 ohci_hcd i2c_amd756 i2c_core evdev usbcore raid0 dm_mod nls_utf8
> Pid: 15433, comm: bash Not tainted 2.6.11-mm1n
> RIP: 0010:[<ffffffff8013d094>] <ffffffff8013d094>{__do_softirq+84}
> RSP: 0018:ffff8101dff83f68 EFLAGS: 00000206
> RAX: ffffffff80651880 RBX: 0000000000000002 RCX: 0000000000000004
> RDX: 0000000000000002 RSI: 0000000000000103 RDI: ffff8101d7c77680
> RBP: ffff810177ffbe48 R08: 0000000000000002 R09: 0000000000000100
> R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001
> R13: 00002aaaaaafb000 R14: 000000000000000a R15: 0000000000000001
> FS: 00002aaaab2890a0(0000) GS:ffffffff80651880(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 00002aaaaaafb000 CR3: 00000001bb2a0000 CR4: 00000000000006e0
>
> Call Trace:<IRQ> <ffffffff8013d165>{do_softirq+53}
> <ffffffff8010ef59>{apic_timer_interrupt+133}
> <EOI> <ffffffff80403055>{_spin_unlock_irqrestore+5}
> <ffffffff801bd357>{write_sysrq_trigger+55}
> <ffffffff80183579>{vfs_write+233}
> <ffffffff80183713>{sys_write+83}
> <ffffffff8010e5ce>{system_call+126}
That's probably just a false positive in Ingo's soft-lockup detector. Long
streams of irq-context serial console output will do that.
Ingo, we already have a touch_nmi_watchdog() in the sysrq code. It might be
worth adding a touch_softlockup_watchdog() wherever we have a
touch_nmi_watchdog().
next prev parent reply other threads:[~2005-03-09 19:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050308170107.231a145c.akpm@osdl.org>
[not found] ` <1110327267.24286.139.camel@dyn318077bld.beaverton.ibm.com>
[not found] ` <18744.1110364438@redhat.com>
2005-03-09 11:04 ` aio stress panic on 2.6.11-mm1 Suparna Bhattacharya
2005-03-09 11:05 ` Andrew Morton
2005-03-09 11:07 ` Arjan van de Ven
2005-03-09 11:17 ` Andi Kleen
2005-03-09 11:28 ` Andrew Morton
2005-03-09 11:59 ` David Howells
2005-03-09 12:12 ` [PATCH] rwsem: Make rwsems use interrupt disabling spinlocks David Howells
2005-03-09 17:35 ` Badari Pulavarty
2005-03-09 19:18 ` Badari Pulavarty
2005-03-09 19:16 ` Badari Pulavarty
2005-03-09 19:42 ` Andrew Morton [this message]
2005-03-09 20:10 ` Arjan van de Ven
2005-03-11 9:40 ` Ingo Molnar
2005-03-11 10:07 ` Andrew Morton
2005-03-11 10:25 ` Ingo Molnar
2005-03-09 11:10 ` aio stress panic on 2.6.11-mm1 Arjan van de Ven
2005-03-09 11:21 ` Andi Kleen
2005-03-09 14:48 ` Suparna Bhattacharya
2005-03-09 11:11 ` Andi Kleen
2005-03-09 21:58 ` David Howells
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=20050309114234.6598f486.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pbadari@us.ibm.com \
--cc=suparna@in.ibm.com \
--cc=torvalds@osdl.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
Powered by JetHome