I am seeing two problems with kdb on a 2.6.9 kernel. This is on a x86 PC.
Running v4.4. If anyone has seen them before and has a solution I would
greatly appreciate
it.
thanks
- ac
1. I keep getting Debug linux kernel messages when I enter KDB. I am
doing it over
a serial driver:
"Debug: sleeping function called from invalid context at ..."
Most of the time I get to a kdb console but sometimes I hang on an
endless loop:
The stack always seems to indicate the problem comes from
kdb_getarea_size():
Debug: sleeping function called from invalid context at kernel/sched.c:3535
in_atomic():1[expected: 0], irqs_disabled():0
[<c010692c>] dump_stack+0x15/0x17
[<c011c7ab>] __might_sleep+0x7d/0x87
[<c030d176>] __cond_resched+0x14/0x3a
[<c01d6417>] kdb_getarea_size+0x72/0x150
[<c01d66c8>] kdb_getword+0x31/0x8b
[<c02a6d26>] kdba_find_return_1+0xf6/0x377
[<c02a700a>] kdba_find_return+0x63/0x94
[<c02a74eb>] kdba_prologue+0x4b0/0x59e
[<c01d606f>] kdb_get_next_ar+0x92/0x25d
[<c02a5791>] kdba_bt_stack+0x1c1/0x484
[<c02a5a6c>] kdba_bt_process+0xc/0x10
[<c01d4bed>] kdb_bt1+0x6d/0xaa
[<c01d4f15>] kdb_bt+0x2eb/0x2fe
[<c01d7749>] kdb_parse+0x31d/0x40c
[<c01d7c9c>] kdb_local+0x3d6/0x41c
[<c01d7dae>] kdb_main_loop+0x8e/0x16e
[<c02a7d5e>] kdba_main_loop+0x28/0x3b
[<c01d84a9>] kdb+0x61b/0x862
[<c02415ea>] receive_chars+0x91/0x249
[<c0241a4b>] serial8250_interrupt+0x120/0x200
[<c0108183>] handle_IRQ_event+0x22/0x4b
[<c0108aef>] do_IRQ+0x11d/0x246
[<c01064a4>] common_interrupt+0x18/0x20
[<c01040a5>] cpu_idle+0x22/0x37
[<c0100418>] rest_init+0xa8/0xaa
[<c03f97d2>] start_kernel+0x231/0x233
[<c010019f>] 0xc010019f
Debug: sleeping function called from invalid context at
include/asm/uaccess.h:428
in_atomic():1[expected: 0], irqs_disabled():0
[<c010692c>] dump_stack+0x15/0x17
[<c011c7ab>] __might_sleep+0x7d/0x87
[<c01d6451>] kdb_getarea_size+0xac/0x150
[<c01d66fa>] kdb_getword+0x63/0x8b
[<c02a6c79>] kdba_find_return_1+0x49/0x377
[<c02a700a>] kdba_find_return+0x63/0x94
[<c02a74eb>] kdba_prologue+0x4b0/0x59e
[<c01d606f>] kdb_get_next_ar+0x92/0x25d
[<c02a5791>] kdba_bt_stack+0x1c1/0x484
[<c02a5a6c>] kdba_bt_process+0xc/0x10
[<c01d4bed>] kdb_bt1+0x6d/0xaa
[<c01d4f15>] kdb_bt+0x2eb/0x2fe
[<c01d7749>] kdb_parse+0x31d/0x40c
[<c01d7c9c>] kdb_local+0x3d6/0x41c
[<c01d7dae>] kdb_main_loop+0x8e/0x16e
[<c02a7d5e>] kdba_main_loop+0x28/0x3b
[<c01d84a9>] kdb+0x61b/0x862
[<c02415ea>] receive_chars+0x91/0x249
[<c0241a4b>] serial8250_interrupt+0x120/0x200
[<c0108183>] handle_IRQ_event+0x22/0x4b
[<c0108aef>] do_IRQ+0x11d/0x246
[<c01064a4>] common_interrupt+0x18/0x20
[<c01040a5>] cpu_idle+0x22/0x37
[<c0100418>] rest_init+0xa8/0xaa
[<c03f97d2>] start_kernel+0x231/0x233
[<c010019f>] 0xc010019f
Debug: sleeping function called from invalid context at kernel/sched.c:3535
in_atomic():1[expected: 0], irqs_disabled():
2. I have my kernel and modules configured to use fp but I don't always
get a stack
trace and when I do it is a real toss up whether the arguments are valid
or not. The stack is fine. It just seems kdb doesn't always know how to
figure it out. Is there some config
I am missing?
thanks
---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
|