Re: 2.5.38 semaphore.c calls sleeping function in illegal context

From: Andrew Morton (
Date: Mon Sep 23 2002 - 20:12:54 EST

William Lee Irwin III wrote:
> ksymoops 2.4.6 on i686 2.5.38-2. Options used
> -v /mnt/b/2.5.38/vmlinux-2.5.38-2 (specified)
> -K (specified)
> -L (specified)
> -O (specified)
> -m /boot/ (specified)
> Reading Oops report from the terminal
> c02c9f6c c02c9f84 c01175f7 c0260f80 c0261500 0000007e c02c9f98 c011a4a1
> c0261500 0000007e 00000000 c02c9fac c011a78a c0312480 c0278213 c0383244
> c02c9fb8 c02d8316 c02ba640 c02c9fc0 c02d8164 c02c9fd0 c02d8a4b 00000000
> Call Trace: [<c01175f7>] [<c011a4a1>] [<c011a78a>] [<c0105000>]
> Warning (Oops_read): Code line not seen, dumping what data is available
> Trace; c01175f7 <__might_sleep+27/2b>
> Trace; c011a4a1 <acquire_console_sem+2d/50>
> Trace; c011a78a <register_console+122/1cc>
> Trace; c0105000 <_stext+0/0>

Don't know. Who called register_console()?

But I suspect in_atomic() is returning incorrect or misleading
answers early in boot.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:41 EST