BUG:schedulingwhileatomic:events/0/4/总结

对于Linux内核来说&＃xff0c;Oops就意外着内核出了异常&＃xff0c;此时会将产生异常时CPU的状态&＃xff0c;出错的指令地址、数据地址及其他寄存器&＃xff0c;函数调用的顺序甚至是栈里面的内容都打印出来&＃xff0c;然后根据异常的严重程度来决定下一步的操作&＃xff1a;杀死导致异常的进程或者挂起系统。

最典型的异常是在内核态引用了一个非法地址&＃xff0c;通常是未初始化的野指针Null&＃xff0c;这将导致页表异常&＃xff0c;最终引发Oops。

Linux系统足够健壮&＃xff0c;能够正常的反应各种异常。异常通常导致当前进程的死亡&＃xff0c;而系统依然能够继续运转&＃xff0c;但是这种运转都处在一种不稳定的状态&＃xff0c;随时可能出问题。对于中断上下文的异常及系统关键资源的破坏&＃xff0c;通常会导致内核挂起&＃xff0c;不再响应任何事件。

2 内核的异常级别
2.1 Bug
Bug是指那些不符合内核的正常设计&＃xff0c;但内核能够检测出来并且对系统运行不会产生影响的问题&＃xff0c;比如在原子上下文中休眠。如&＃xff1a;
BUG: scheduling while atomic: insmod/826/0x00000002
Call Trace:
[ef12f700] [c00081e0] show_stack&＃43;0x3c/0x194 (unreliable)
[ef12f730] [c0019b2c] __schedule_bug&＃43;0x64/0x78
[ef12f750] [c0350f50] schedule&＃43;0x324/0x34c
[ef12f7a0] [c03515c0] schedule_timeout&＃43;0x68/0xe4
[ef12f7e0] [c027938c] fsl_elbc_run_command&＃43;0x138/0x1c0
[ef12f820] [c0275820] nand_do_read_ops&＃43;0x130/0x3dc
[ef12f880] [c0275ebc] nand_read&＃43;0xac/0xe0
[ef12f8b0] [c0262d98] part_read&＃43;0x5c/0xe4
[ef12f8c0] [c017bcac] jffs2_flash_read&＃43;0x68/0x254
[ef12f8f0] [c0170550] jffs2_read_dnode&＃43;0x60/0x304
[ef12f940] [c017088c] jffs2_read_inode_range&＃43;0x98/0x180
[ef12f970] [c016e610] jffs2_do_readpage_nolock&＃43;0x94/0x1ac
[ef12f990] [c016ee04] jffs2_write_begin&＃43;0x2b0/0x330
[ef12fa10] [c005144c] generic_file_buffered_write&＃43;0x11c/0x8d0
[ef12fab0] [c0051e48] __generic_file_aio_write_nolock&＃43;0x248/0x500
[ef12fb20] [c0052168] generic_file_aio_write&＃43;0x68/0x10c
[ef12fb50] [c007ca80] do_sync_write&＃43;0xc4/0x138
[ef12fc10] [f107c0dc] oops_log&＃43;0xdc/0x1e8 [oopslog]
[ef12fe70] [f3087058] oops_log_init&＃43;0x58/0xa0 [oopslog]
[ef12fe80] [c00477bc] sys_init_module&＃43;0x130/0x17dc
[ef12ff40] [c00104b0] ret_from_syscall&＃43;0x0/0x38
--- Exception: c01 at 0xff29658
    LR &＃61; 0x10031300

2.2 Oops
程序在内核态时&＃xff0c;进入一种异常情况&＃xff0c;比如引用非法指针导致的数据异常&＃xff0c;数组越界导致的取指异常&＃xff0c;此时异常处理机制能够捕获此异常&＃xff0c;并将系统关键信息打印到串口上&＃xff0c;正常情况下Oops消息会被记录到系统日志中去。

Oops发生时&＃xff0c;进程处在内核态&＃xff0c;很可能正在访问系统关键资源&＃xff0c;并且获取了一些锁&＃xff0c;当进程由于Oops异常退出时&＃xff0c;无法释放已经获取的资源&＃xff0c;导致其他需要获取此资源的进程挂起&＃xff0c;对系统的正常运行造成影响。通常这种情况&＃xff0c;系统处在不稳定的状态&＃xff0c;很可能崩溃。

2.3 Panic
当Oops发生在中断上下文中或者在进程0和1中&＃xff0c;系统将彻底挂起&＃xff0c;因为中断服务程序异常后&＃xff0c;将无法恢复&＃xff0c;这种情况即称为内核panic。另外当系统设置了panic标志时&＃xff0c;无论Oops发生在中断上下文还是进程上下文&＃xff0c;都将导致内核Panic。由于在中断复位程序中panic后&＃xff0c;系统将不再进行调度&＃xff0c;Syslogd将不会再运行&＃xff0c;因此这种情况下&＃xff0c;Oops的消息仅仅打印到串口上&＃xff0c;不会被记录在系统日志中。

在调试IC卡驱动过程中频繁拔插卡则出现BUG: scheduling while atomic: events/0/4/0x00010004异常导致系统崩溃,具体信息如下:

[ 1947.900000] BUG: scheduling while atomic: events/0/4/0x00010004
<4>[ 1947.900000] &＃64;&＃64;&＃64;&＃64;cardslot_iso7816_uart_interrupt,line:1384
<3>[ 1947.900000] BUG: scheduling while atomic: events/0/4/0x00010004
<4>[ 1947.900000] Modules linked in: iccard iso7816_uart bcm589x_pm(P) bar_scanner bcm589x_ped idtechencmag magstripe

cx930xx modem slnsp ftp101 printer bcm589x_spi touch_screen bcm5892_adc_driver matrix_keys beeper leds fusion

bcm589x_otg bcm589x_dwccom [last unloaded: iso7816_uart]
<4>[ 1947.900000]
<4>[ 1947.900000] Pid: 4, comm:             events/0
<4>[ 1947.900000] CPU: 0    Tainted: P            (2.6.32.9-bcm5892 #8)
<4>[ 1947.900000] PC is at memcpy&＃43;0x16c/0x330
<4>[ 1947.900000] LR is at 0xffffff
<4>[ 1947.900000] pc : []    lr : [<00ffffff>]    psr: 20000013
<4>[ 1947.900000] sp : c3823ecc  ip : 00ffffff  fp : c3823f60
<4>[ 1947.900000] r10: 00000000  r9 : 00ffffff  r8 : 00ffffff
<4>[ 1947.900000] r7 : 00ffffff  r6 : 00ffffff  r5 : ff000000  r4 : 0000ffff
<4>[ 1947.900000] r3 : ff00ffff  r2 : 0000003f  r1 : c483ad44  r0 : c4854d40
<4>[ 1947.900000] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
<4>[ 1947.900000] Control: 00c5387d  Table: 43b14008  DAC: 00000017
<4>[ 1947.900000] [] (show_regs&＃43;0x0/0x4c) from [] (__schedule_bug&＃43;0x48/0x5c)
<4>[ 1947.900000]  r4:c3823e84
<4>[ 1947.900000] [] (__schedule_bug&＃43;0x0/0x5c) from [] (schedule&＃43;0x78/0x45c)
<4>[ 1947.900000]  r4:c3823ce8
<4>[ 1947.900000] [] (schedule&＃43;0x0/0x45c) from [] (schedule_timeout&＃43;0x20/0x1dc)
<4>[ 1947.900000] [] (schedule_timeout&＃43;0x0/0x1dc) from [] (wait_for_common&＃43;0xf8/0x1b4)
<4>[ 1947.900000]  r6:c3822000 r5:c3815340 r4:c3823ce8
<4>[ 1947.900000] [] (wait_for_common&＃43;0x0/0x1b4) from [] (wait_for_completion&＃43;0x18/0x1c)
<4>[ 1947.900000] [] (wait_for_completion&＃43;0x0/0x1c) from [] (__cancel_work_timer&＃43;0x140/0x194)
<4>[ 1947.900000] [] (__cancel_work_timer&＃43;0x0/0x194) from [] (cancel_delayed_work_sync&＃43;0x14/0x18)
<4>[ 1947.900000] [] (cancel_delayed_work_sync&＃43;0x0/0x18) from []

(fb_deferred_io_fsync_delay&＃43;0x1c/0x2c)
<4>[ 1947.900000] [] (fb_deferred_io_fsync_delay&＃43;0x0/0x2c) from []

(new8110_lcd_icon_control&＃43;0xb0/0xbc)
<4>[ 1947.900000]  r5:c38daa80 r4:00008040
<4>[ 1947.900000] [] (new8110_lcd_icon_control&＃43;0x0/0xbc) from [] (lcd_icon_set&＃43;0x20/0x28)
<4>[ 1947.900000]  r7:bf08e6b0 r6:000000ff r5:c3bee70c r4:c3b0aa1c
<4>[ 1947.900000] [] (lcd_icon_set&＃43;0x0/0x28) from [] (led_trigger_event&＃43;0x64/0xa0)
<4>[ 1947.900000] [] (led_trigger_event&＃43;0x0/0xa0) from [] (card_insert_interrupt&＃43;0x70/0x98

[iccard])
<4>[ 1947.900000]  r6:bf08cacc r5:c041cf4c r4:00000040
<4>[ 1947.900000] [] (card_insert_interrupt&＃43;0x0/0x98 [iccard]) from []

(cardslot_iso7816_uart_interrupt&＃43;0xd4/0xb68 [iccard])
<4>[ 1947.900000]  r7:0000002e r6:c041cf4c r5:0000002e r4:bf08cacc
<4>[ 1947.900000] [] (cardslot_iso7816_uart_interrupt&＃43;0x0/0xb68 [iccard]) from []

(handle_IRQ_event&＃43;0x3c/0xfc)
<4>[ 1947.900000]  r6:00000000 r5:00000000 r4:c3932da0
<4>[ 1947.900000] [] (handle_IRQ_event&＃43;0x0/0xfc) from [] (handle_level_irq&＃43;0xcc/0x168)
<4>[ 1947.900000]  r7:00000002 r6:0000002e r5:c3932da0 r4:c0420810
<4>[ 1947.900000] [] (handle_level_irq&＃43;0x0/0x168) from [] (asm_do_IRQ&＃43;0x70/0x8c)
<4>[ 1947.900000]  r6:00004000 r5:00000000 r4:0000002e
<4>[ 1947.900000] [] (asm_do_IRQ&＃43;0x0/0x8c) from [] (__irq_svc&＃43;0x38/0xd4)
<4>[ 1947.900000] Exception stack(0xc3823e84 to 0xc3823ecc)
<4>[ 1947.900000] 3e80:          c4854d40 c483ad44 0000003f ff00ffff 0000ffff ff000000 00ffffff
<4>[ 1947.900000] 3ea0: 00ffffff 00ffffff 00ffffff 00000000 c3823f60 00ffffff c3823ecc 00ffffff
<4>[ 1947.900000] 3ec0: c017c5cc 20000013 ffffffff
<4>[ 1947.900000]  r5:d102a000 r4:ffffffff
<4>[ 1947.900000] [] (new8110fb_deferred_io&＃43;0x0/0x5ac) from [] (fb_deferred_io_work&＃43;0x90/0xe0)
<4>[ 1947.900000] [] (fb_deferred_io_work&＃43;0x0/0xe0) from [] (worker_thread&＃43;0x178/0x22c)
<4>[ 1947.900000]  r8:c0197eb0 r7:c3801900 r6:c38daa1c r5:c3822000 r4:c38daa20
<4>[ 1947.900000] [] (worker_thread&＃43;0x0/0x22c) from [] (kthread&＃43;0x84/0x8c)
<4>[ 1947.900000] [] (kthread&＃43;0x0/0x8c) from [] (do_exit&＃43;0x0/0x62c)
<4>[ 1947.900000]  r7:00000000 r6:00000000 r5:00000000 r4:00000000

经过反复调试确定问题出在拔插卡中断里面,在拔插卡中断中调用了led_trigger_event(card_insert_led_trigger, LED_OFF)函数,此函数将会加锁而概率性引起死锁或者阻塞,而在中断上下文中绝对不允许调用阻塞函数,故系统将会报bug.

去掉后问题解决.