Messages in this thread | ![/](/images/icornerl.gif) | | Date | Mon, 3 Feb 2003 13:35:06 -0800 | From | Chris Wright <> | Subject | Re: Kernel 2.4.20 panic in scheduler |
| |
* John Goerzen (jgoerzen@complete.org) wrote: > > Today I experienced a kernel panic running kernel 2.4.20 (plus the ctx > vserver patch; otherwise vanilla) with a bcm5700 module added in. It's
Have you tried this without the vserver patch? Last I looked it touched many of the code paths in your trace below. Also, if possible, set up a serial console, it'll be a lot easier to catch the full trace.
> Adhoc c01093ef <system_call+33/38> > Adhoc c011a201 <schedule+501/530>
vserver touches this code
> Adhoc c01208c8 <release_task+e8/110>
vserver touches this code
> Adhoc c01218dc <sys_wait4+39c/410> > Adhoc c01218de <sys_wait4+39e/410> > Adhoc c012b419 <sys_release_ip_info+29/60>
this is vserver code which could be called from either release_task() or inet_sock_destruct() (both are in this trace).
you get the idea... cheers, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |