Re: BUG kmalloc-2048: Invalid object pointer 0xf656ad80

From: Justin Mattock
Date: Wed Apr 08 2009 - 23:07:05 EST


On Wed, Apr 8, 2009 at 8:00 PM, Bryan Donlan <bdonlan@xxxxxxxxx> wrote:
> On Wed, Apr 8, 2009 at 10:50 PM, Justin Mattock <justinmattock@xxxxxxxxx> wrote:
>> On Wed, Apr 8, 2009 at 7:38 PM, Bryan Donlan <bdonlan@xxxxxxxxx> wrote:
>>> On Wed, Apr 8, 2009 at 10:19 PM, Justin Mattock <justinmattock@xxxxxxxxx> wrote:
>>>> doing a:
>>>> sudo /sbin/rmmod wl
>>>> (generated a bug message)
>>> [snip]
>>>> The kernel is tainted with nvidia, and a broadcom wl.
>>>
>>> Would this broadcom wl be the very module you're trying to remove?
>>> What makes you think this isn't a bug in this wl binary module? From
>>> the looks of the backtrace it's dying due to a free of a wild pointer
>>> right in the middle of the wl module - it certainly doesn't look like
>>> it came from some other subsystem...
>>>
>>
>> yup,
>> remove wl, in exchange
>> for ndiswrapper. and poof
>> this showed up..
>
> The bug came up in the wl module's removal code - I'd suggest just not
> loading it in the first place.
>

The module sounded like a good idea,
the problem I have(not sure if this is kernel related)
is after the network is up, loading anything takes
a good 30's, then after about 15min later my router will
do a reset(disconnecting any machine connected). could be something missing
with wpasupplicant, kernel, some lib, who knows...
(at this point my main goal is to get the rest of
the system built before dealing with quirks).

regards,

--
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/