Quoting Andrew Morton <[email protected]>:
This looks like some sort of slab scribble, possibly caused by faulty
error-path handling in the ipw2200 code.
Please enable CONFIG_DEBUG_SLAB and see if that picks anything up.
Also enable CONFIG_DEBUG_PAGEALLOC.
You may also get more info by setting CONFIG_IPW_DEBUG and loading the
module with `debug=65535' (guess).
Whatever you do, don't fix the firmware loading failure (sorry). Doing
that will cause you to not be able to reproduce this bug ;)
Hi,
I enabled all these options yesterday and ran it all night without
encountering
this oops again (the firmware loading error yes, but I've had it since I began
to use ipw2200). Perhaps isn't it the same issue than Zilvinas ?
I'll continue trying, though...
Regards,
Alexandre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
