Most recent kernel where this bug did *NOT* occur: Distribution: Ubuntu Feisty/Gutsy Hardware Environment: Pentium M, e1000, ipw2200 Software Environment: network-manager Problem Description: Oops removing proc entry during ifdown Steps to reproduce: Suspend/resume with interfaces alive
Created attachment 11525 [details] Dmesg showing oops
Original bug report: https://launchpad.net/bugs/115184
Andrew Morton <akpm@linux-foundation.org> wrote: > > [43092.388000] Stack: e30f433c cab60000 c028608e 00000000 e2e8ae40 00000000 e2e8a5c0 dfe0aa58 > [43092.388000] c826ca00 c826ca00 f10a72ff f1088989 00a33d71 000080fe 00000000 00000001 > [43092.388000] cab60000 e2e8a5c0 dfe0aa58 00000000 c826ca00 f1089594 c826ca54 00000040 > [43092.388000] Call Trace: > [43092.388000] [<c028608e>] pneigh_queue_purge+0x1e/0x30 > [43092.388000] [<f10a72ff>] snmp6_unregister_dev+0x2f/0x40 [ipv6] Looks like a problem with your resume. The second argument to remove_proc_entry, parent, has the value 00a33d71 which is clearly bogus. That value in turn comes from proc_net_devsnmp6. So somehow during the suspend/resume that pointer has been corrupted. Cheers,
This appears to be fixed, at least in 2.6.22-rc2.