2.5.38 semaphore.c calls sleeping function in illegal context

2.5.38 semaphore.c calls sleeping function in illegal context

Post by William Lee Irwin II » Wed, 25 Sep 2002 09:30:08



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/System.map-2.5.38-2 (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>

1 warning issued.  Results may not be reliable.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.38 semaphore.c calls sleeping function in illegal context

Post by Andrew Morto » Wed, 25 Sep 2002 10:20:04



Quote:

> 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/System.map-2.5.38-2 (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

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.5.38 semaphore.c calls sleeping function in illegal context

Post by William Lee Irwin II » Wed, 25 Sep 2002 10:30:05



>> 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.

I would suspect console_init(). I believe some kind of change was
done here for preempt bootstrap ordering issues (vm86_info: BAD) as
it's a bit too early to schedule here. Things have gotten interesting
down here in other contexts where sleeping and/or waitqueue fiddling
is illegal so early on. Getting a better stack dump might be helpful.
I'll see if I can do that soon.

Cheers,
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. sleeping function called from illegal context (asm/semaphore.h)

Hi folks,

Booting into 2.5.40 (upto changeset 1.754) I found this in my logs:

Debug: sleeping function called from illegal context at
include/asm/semaphore.h:119
Call Trace:
 [<c01149e2>] E __might_sleep_Rd533bec7+0x52/0x2d3ad8
 [<c02b9765>] E usb_hub_tt_clear_buffer_Rbe74a884+0xf45/0xffffe690
 [<c02b9a00>] E usb_hub_tt_clear_buffer_Rbe74a884+0x11e0/0xffffe690
 [<c02b9a35>] E usb_hub_tt_clear_buffer_Rbe74a884+0x1215/0xffffe690
 [<c02b9a00>] E usb_hub_tt_clear_buffer_Rbe74a884+0x11e0/0xffffe690
 [<c01137b0>] E default_wake_function_Rfe478e92+0x0/0xa0
 [<c01054d9>] E enable_hlt_R9c7077bd+0x1c9/0x16960

I hope this is usefull info...

please CC me if you have questions as I'm not subscribed.

Kind regards,
Harm Verhagen

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. ufs in raw mode: reading inodes

3. 2.5.38 vs. 2.5.38-mm1 dbench 512 oprofiles

4. mounting image via loop device

5. Sleeping function called from illegal context at page_alloc.c:325

6. If this is too simple I ask for forgiveness...

7. sleeping function called from illegal context

8. Is there a TCP/IP for INTEL cards yet?

9. sleeping function called from illegal context at mm/slab.c:1723

10. sleeping function called from illegal context (set_shrinker)

11. Sleeping function called from illegal context at slab.c:1378

12. Sleeping function called from illegal context...

13. 2.5.47 -- OOPS -- sleeping function called from illegal context at mm/page_alloc.c:417