LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org> To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>, Peter Zijlstra <peterz@infradead.org>, Thomas Gleixner <tglx@linutronix.de> Subject: Re: 2.6.26.6-rt11: BUGs (sleeping function called from invalid context) Date: Fri, 16 Jan 2009 19:37:14 -0500 (EST) [thread overview] Message-ID: <alpine.DEB.1.10.0901161935130.9232@gandalf.stny.rr.com> (raw) In-Reply-To: <1232147180.3081.4.camel@localhost.localdomain> On Fri, 16 Jan 2009, Fernando Lopez-Lezcano wrote: > On Fri, 2009-01-16 at 15:49 -0500, Steven Rostedt wrote: > > On Fri, 16 Jan 2009, Fernando Lopez-Lezcano wrote: > > > > > 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... > > > > Could you try this patch and see if it fixes your issue. > > That particular BUG seems to be gone, so far with no side effects (no > hard disk explosions or anything like that, hopefully). Thanks!!! Great to hear! > > Hmmm, I don't remember seeing this before (but I could be wrong): > > irq 19: nobody cared (try booting with the "irqpoll" option) > Pid: 479, comm: IRQ-19 Not tainted > 2.6.26.8-1.rt13.2.fc9.ccrma.i686.rtPAE #1 > [<c0461b70>] __report_bad_irq+0x2e/0x6f > [<c0461d6c>] note_interrupt+0x1bb/0x20b > [<c0460f6c>] ? handle_IRQ_event+0x49/0xe6 > [<c046128c>] thread_simple_irq+0x68/0x7c > [<c04612a0>] ? do_irqd+0x0/0x229 > [<c046134f>] do_irqd+0xaf/0x229 > [<c04612a0>] ? do_irqd+0x0/0x229 > [<c043b023>] kthread+0x3b/0x61 > [<c043afe8>] ? kthread+0x0/0x61 > [<c040481f>] kernel_thread_helper+0x7/0x10 > ======================= > handlers: > [<c058d680>] (usb_hcd_irq+0x0/0x61) > turning off IO-APIC fast mode. > irq 19: nobody cared (try booting with the "irqpoll" option) > Pid: 479, comm: IRQ-19 Not tainted > 2.6.26.8-1.rt13.2.fc9.ccrma.i686.rtPAE #1 > [<c0461b70>] __report_bad_irq+0x2e/0x6f > [<c0461d6c>] note_interrupt+0x1bb/0x20b > [<c0460f6c>] ? handle_IRQ_event+0x49/0xe6 > [<c046128c>] thread_simple_irq+0x68/0x7c > [<c04612a0>] ? do_irqd+0x0/0x229 > [<c046134f>] do_irqd+0xaf/0x229 > [<c04612a0>] ? do_irqd+0x0/0x229 > [<c043b023>] kthread+0x3b/0x61 > [<c043afe8>] ? kthread+0x0/0x61 > [<c040481f>] kernel_thread_helper+0x7/0x10 > ======================= > handlers: > [<c058d680>] (usb_hcd_irq+0x0/0x61) > > Related? No, but that looks like a boot interrupt issue. See this (huge) thread for details: http://marc.info/?t=123154237900002&r=1&w=2 -- Steve
next prev parent reply other threads:[~2009-01-17 0:37 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-07 18:50 2.6.26.6-rt11: BUGs (sleeping function called from invalid context) 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 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 [this message] 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=alpine.DEB.1.10.0901161935130.9232@gandalf.stny.rr.com \ --to=rostedt@goodmis.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@elte.hu \ --cc=nando@ccrma.Stanford.EDU \ --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: linkBe 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; as well as URLs for NNTP newsgroup(s).