LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: 2.6.26.6-rt11: BUGs (sleeping function called from invalid context)
Date: Fri, 16 Jan 2009 12:16:15 -0800 [thread overview]
Message-ID: <1232136975.6326.32.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.10.0811071400570.3711@gandalf.stny.rr.com>
On Fri, 2008-11-07 at 14:01 -0500, Steven Rostedt wrote:
> Peter, I think we've seen this before. It is the highmem code sleeping.
>
> On Fri, 7 Nov 2008, Fernando Lopez-Lezcano wrote:
>
> > Three BUGs while booting 2.6.26.7 + rt11 (same hardware: no problems
> > with 2.6.24.7-rt21):
> >
> > Nov 7 10:31:19 host kernel: BUG: sleeping function called from invalid
> > context IRQ-22(540) at arch/x86/mm/highmem_32.c:8
> > Nov 7 10:31:19 host kernel: in_atomic():0 [00000000], irqs_disabled():1
> > Nov 7 10:31:19 host kernel: Pid: 540, comm: IRQ-22 Not tainted
> > 2.6.26.7-1.rt11.1fc9.ccrma.i686.rt #1
> > Nov 7 10:31:19 host kernel: [<c041ff88>] __might_sleep+0xe8/0xed
> > Nov 7 10:31:19 host kernel: [<c041cd55>] kmap+0x42/0x55
>
> As here.
Still happening in 2.6.26.8-rt13...
-- Fernando
> > Nov 7 10:31:19 host kernel: [<f88e9e1d>] ata_sff_hsm_move+0x3d3/0x66b
> > [libata]
> > Nov 7 10:31:19 host kernel: [<f88ea314>] ata_sff_interrupt+0x153/0x1eb
> > [libata]
> > Nov 7 10:31:19 host kernel: [<c0461730>] handle_IRQ_event+0x49/0xcd
> > Nov 7 10:31:19 host kernel: [<c0461a15>] thread_simple_irq+0x45/0x7c
> > Nov 7 10:31:19 host kernel: [<c0461a4c>] ? do_irqd+0x0/0x229
> > Nov 7 10:31:19 host kernel: [<c0461afb>] do_irqd+0xaf/0x229
> > Nov 7 10:31:19 host kernel: [<c0461a4c>] ? do_irqd+0x0/0x229
> > Nov 7 10:31:19 host kernel: [<c043b15f>] kthread+0x3b/0x61
> > Nov 7 10:31:19 host kernel: [<c043b124>] ? kthread+0x0/0x61
> > Nov 7 10:31:19 host kernel: [<c040581f>] kernel_thread_helper+0x7/0x10
> > Nov 7 10:31:19 host kernel: =======================
> >
> >
> > Nov 7 10:31:01 host kernel: BUG: sleeping function called from invalid
> > context IRQ-22(540) at arch/x86/mm/highmem_32.c:8
> > Nov 7 10:31:01 host kernel: in_atomic():0 [00000000], irqs_disabled():1
> > Nov 7 10:31:01 host kernel: Pid: 540, comm: IRQ-22 Not tainted
> > 2.6.26.7-1.rt11.1fc9.ccrma.i686.rt #1
> > Nov 7 10:31:01 host kernel: [<c041ff88>] __might_sleep+0xe8/0xed
> > Nov 7 10:31:01 host kernel: [<c041cd55>] kmap+0x42/0x55
> > Nov 7 10:31:01 host kernel: [<f88e9e1d>] ata_sff_hsm_move+0x3d3/0x66b
> > [libata]
> > Nov 7 10:31:01 host kernel: [<f88ea314>] ata_sff_interrupt+0x153/0x1eb
> > [libata]
> > Nov 7 10:31:01 host kernel: [<c0461730>] handle_IRQ_event+0x49/0xcd
> > Nov 7 10:31:01 host kernel: [<c0461a15>] thread_simple_irq+0x45/0x7c
> > Nov 7 10:31:01 host kernel: [<c0461a4c>] ? do_irqd+0x0/0x229
> > Nov 7 10:31:01 host kernel: [<c0461afb>] do_irqd+0xaf/0x229
> > Nov 7 10:31:01 host kernel: [<c0461a4c>] ? do_irqd+0x0/0x229
> > Nov 7 10:31:01 host kernel: [<c043b15f>] kthread+0x3b/0x61
> > Nov 7 10:31:01 host kernel: [<c043b124>] ? kthread+0x0/0x61
> > Nov 7 10:31:01 host kernel: [<c040581f>] kernel_thread_helper+0x7/0x10
> > Nov 7 10:31:01 host kernel: =======================
> >
> >
> > Nov 7 10:30:58 host kernel: BUG: sleeping function called from invalid
> > context IRQ-22(540) at arch/x86/mm/highmem_32.c:8
> > Nov 7 10:30:58 host kernel: in_atomic():0 [00000000], irqs_disabled():1
> > Nov 7 10:30:58 host kernel: Pid: 540, comm: IRQ-22 Not tainted
> > 2.6.26.7-1.rt11.1fc9.ccrma.i686.rt #1
> > Nov 7 10:30:58 host kernel: [<c041ff88>] __might_sleep+0xe8/0xed
> > Nov 7 10:30:58 host kernel: [<c041cd55>] kmap+0x42/0x55
> > Nov 7 10:30:58 host kernel: [<f88e9e1d>] ata_sff_hsm_move+0x3d3/0x66b
> > [libata]
> > Nov 7 10:30:58 host kernel: [<f88ea314>] ata_sff_interrupt+0x153/0x1eb
> > [libata]
> > Nov 7 10:30:58 host kernel: [<c0461730>] handle_IRQ_event+0x49/0xcd
> > Nov 7 10:30:58 host kernel: [<c0461a15>] thread_simple_irq+0x45/0x7c
> > Nov 7 10:30:58 host kernel: [<c0461a4c>] ? do_irqd+0x0/0x229
> > Nov 7 10:30:58 host kernel: [<c0461afb>] do_irqd+0xaf/0x229
> > Nov 7 10:30:58 host kernel: [<c0461a4c>] ? do_irqd+0x0/0x229
> > Nov 7 10:30:58 host kernel: [<c043b15f>] kthread+0x3b/0x61
> > Nov 7 10:30:58 host kernel: [<c043b124>] ? kthread+0x0/0x61
> > Nov 7 10:30:58 host kernel: [<c040581f>] kernel_thread_helper+0x7/0x10
> > Nov 7 10:30:58 host kernel: =======================
> >
next prev parent reply other threads:[~2009-01-16 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 18:50 Fernando Lopez-Lezcano
2008-11-07 19:01 ` Steven Rostedt
2008-11-07 19:16 ` Peter Zijlstra
2008-11-07 21:35 ` Fernando Lopez-Lezcano
2008-11-07 21:47 ` Peter Zijlstra
2008-11-07 23:52 ` Fernando Lopez-Lezcano
2008-11-08 8:47 ` Peter Zijlstra
2008-11-08 18:28 ` Fernando Lopez-Lezcano
2009-01-16 20:16 ` Fernando Lopez-Lezcano [this message]
2009-01-16 20:41 ` Steven Rostedt
2009-01-16 20:49 ` Steven Rostedt
2009-01-16 23:06 ` Fernando Lopez-Lezcano
2009-01-17 0:37 ` Steven Rostedt
2009-01-19 20:36 ` Fernando Lopez-Lezcano
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=1232136975.6326.32.camel@localhost.localdomain \
--to=nando@ccrma.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--subject='Re: 2.6.26.6-rt11: BUGs (sleeping function called from invalid context)' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).