Random kernel panics after 'resume'

  • Sergei Poselenov


    I'm running the the pcmcia-cs-3.2.0 on PPC kernel 2.4.2.

    The cardctl suspend/resume sequence randomly caused
    the kernel crash:

    bash-2.04# cardctl resume 0
    bash-2.04# kernel BUG at slab.c:1073!
    Oops: Kernel Mode Software FPU Emulation, sig: 8
    NIP: C0027AD8 XER: 0000D871 LR: C0027AD8 SP: C0130C70 REGS: c0130bc0 TRAP: 1000
    MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
    TASK = c012f010[0] 'swapper' Last syscall: 120
    last math 00000000 last altivec 00000000
    GPR00: C0027AD8 C0130C70 C012F010 0000001B 00001032 00000001 C0150000 C0150000
    GPR08: C0144490 00000000 0000001F C0130BC0 FFFFFFFF 100AD098 03FF4E00 007FFF64
    GPR16: 00000000 00000001 007FFF00 FFFFFFFF 00001032 00130EF0 00000000 C0002710
    GPR24: C0003E00 007FFEC0 E0000000 E0000000 00001000 00000007 00000007 C01970C0
    Call backtrace:
    C0027AD8 C0027EF8 C0026C10 C000A744 C000A6A0 C5003A04 C5003B7C
    C50043CC C500096C C00180BC C0013DC8 C0013C78 C0013A90 C0002740
    C0003D54 C0003D68 C014170C C00021E4
    Kernel panic: Aiee, killing interrupt handler!
    In interrupt handler - not syncing

    The call backtrace caused the panic is following :

    open_softirq ->bh_action ->unreset_socket ->verify_cis_cache ->read_cis_mem ->set_cis_map ->__ioremap ->get_vm_area ->kmalloc ->kmem_cache_grow

    As I understand, the kmalloc(GFP_KERNEL) is called in context of softirq and kmalloc is going to allocate a new slab.

    Has anyone run into this?


    • David Hinds

      David Hinds - 2002-10-24

      If you are using the standalone pcmcia-cs modules, don't.  If you're using the kernel PCMCIA subsystem, upgrade.  This should not happen with a current kernel; 2.4.2 is out of date.

      -- Dave


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks