mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Mike Galbraith <efault@gmx.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [2.6.23-rt3] NMI watchdog trace of deadlock
Date: Sat, 27 Oct 2007 19:15:42 +1000	[thread overview]
Message-ID: <200710271915.42363.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <1193462494.25330.7.camel@Homer.simpson.net>

On Saturday 27 October 2007 15:21, Mike Galbraith wrote:
> Greetings,
>
> For quite a while now, RT kernels have been locking up on me
> occasionally while my back is turned.  Yesterday, the little bugger
> finally pounced while my serial console box was up and waiting.
>
> [10138.162953] WARNING: at arch/i386/kernel/smp.c:581
> native_smp_call_function_mask() [10138.170583]  [<c01051da>]
> show_trace_log_lvl+0x1a/0x30
> [10138.175796]  [<c0105de3>] show_trace+0x12/0x14
> [10138.180291]  [<c0105dfb>] dump_stack+0x16/0x18
> [10138.184769]  [<c011609f>] native_smp_call_function_mask+0x138/0x13d
> [10138.191117]  [<c0117606>] smp_call_function+0x1e/0x24
> [10138.196210]  [<c012f85c>] on_each_cpu+0x25/0x50
> [10138.200807]  [<c0115c74>] flush_tlb_all+0x1e/0x20
> [10138.205553]  [<c016caaf>] kmap_high+0x1b6/0x417
> [10138.210118]  [<c011ec88>] kmap+0x4d/0x4f
> [10138.214102]  [<c026a9d8>] ntfs_end_buffer_async_read+0x228/0x2f9
> [10138.220163]  [<c01a0e9e>] end_bio_bh_io_sync+0x26/0x3f
> [10138.225352]  [<c01a2b09>] bio_endio+0x42/0x6d
> [10138.229769]  [<c02c2a08>] __end_that_request_first+0x115/0x4ac
> [10138.235682]  [<c02c2da7>] end_that_request_chunk+0x8/0xa
> [10138.241052]  [<c0365943>] ide_end_request+0x55/0x10a
> [10138.246058]  [<c036dae3>] ide_dma_intr+0x6f/0xac
> [10138.250727]  [<c0366d83>] ide_intr+0x93/0x1e0
> [10138.255125]  [<c015afb4>] handle_IRQ_event+0x5c/0xc9

Looks like ntfs is kmap()ing from interrupt context. Should
be using kmap_atomic instead, I think.

But the ntfs code I have seems to do just that...

  reply	other threads:[~2007-10-27  9:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 17:07 2.6.23-rt2 Steven Rostedt
2007-10-27  5:21 ` [2.6.23-rt3] NMI watchdog trace of deadlock Mike Galbraith
2007-10-27  9:15   ` Nick Piggin [this message]
2007-10-27  9:43     ` Mike Galbraith
2007-10-27  9:44     ` Ingo Molnar
2007-10-27 10:12       ` Jaswinder Singh
2007-10-27 13:22         ` Steven Rostedt
2007-10-27 10:17       ` Mike Galbraith
2007-10-27 13:16         ` Ingo Molnar
2007-10-27 14:29         ` Steven Rostedt
2007-10-27  9:40   ` Mike Galbraith

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=200710271915.42363.nickpiggin@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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 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®