Re: ath9k: BUG kmalloc-8192: Poison overwritten

[Justin P. Mattock]

Justin P. Mattock



On May 14, 2010, at 1:13 PM, "Luis R. Rodriguez"  
<lrodriguez@xxxxxxxxxxx> wrote:

> On Fri, May 14, 2010 at 12:04:15PM -0700, Justin P. Mattock wrote:
> > On May 14, 2010, at 10:29 AM, "Luis R. Rodriguez" <lrodriguez@xxxxxxxxxxx
> > > wrote:
> >
> > > On Fri, May 14, 2010 at 10:24 AM, Justin P. Mattock
> > > <justinmattock@xxxxxxxxx> wrote:
> > >
> > > > here you go:
> > > > (I was grabbing the info
> > > > after rmmod and modprobe)
> > > >
> > > > [    7.034242] ATH9K: cachelsz: 256
> > > > [   69.175348] ATH9K: cachelsz: 256
> > >
> > > Close, so I without any patches applied, and by just running
> > > modprobe as below:
> > >
> > >
> > > modprobe ath9k debug=0x00000200
> > >
> > >              ath_print(common, ATH_DBG_CONFIG, "cachelsz %u
> > > rxbufsize %u\n",
> > >                              common->cachelsz, common->rx_bufsize);
> > >
> > >
> > > This is already in the code so just please do this:
> > >
> > > rmmod ath9k
> > > modprobe ath9k debug=0x00000200
> > > dmesg | grep cachelsz
> >
> > O.k. I did a git reset to the origin
> > Then the above, unfortunantly nothing
> > Shows up when grepping
> > Any CONFIG options I might be missing?
>
> CONFIG_ATH_DEBUG
>
>  Luis

Eveything is on except ath5k
For debugging.
--
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/