linux-kernel - Re: 2.6.26.6-rt11: BUGs (sleeping function called from invalid context)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0901161935130.9232@gandalf.stny.rr.com>
Date:	Fri, 16 Jan 2009 19:37:14 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>
cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: 2.6.26.6-rt11: BUGs (sleeping function called from invalid
 context)


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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/