Seeing lots of these WARN_ONS with current -git. Known issue?
b43 hardware.
[41850.615621] WARNING: at net/mac80211/rc80211_minstrel.c:69 minstrel_rate_init+0x92/0x3c0()
[41850.615624] Hardware name: TravelMate 2480
[41850.615626] Modules linked in: uhci_hcd ehci_hcd usbcore ipv6 binfmt_misc rfcomm bnep sco l2cap bluetooth ppdev lp joydev psmouse serio_raw tifm_7xx1 tifm_core video output evdev ext3 jbd mbcache sg sr_mod cdrom sd_mod crc_t10dif fuse [last unloaded: usbcore]
[41850.615652] Pid: 1024, comm: phy0 Tainted: G W 2.6.29-rc1 #11
[41850.615654] Call Trace:
[41850.615660] [<c0487935>] ? printk+0x18/0x1b
[41850.615665] [<c012ee43>] warn_slowpath+0x73/0xd0
[41850.615671] [<c0148cc5>] ? sched_clock_cpu+0x135/0x190
[41850.615674] [<c0147b5b>] ? up+0x2b/0x40
[41850.615677] [<c012f631>] ? release_console_sem+0x191/0x1d0
[41850.615681] [<c046f522>] minstrel_rate_init+0x92/0x3c0
[41850.615686] [<c0454708>] ? ieee80211_rx_bss_get+0x98/0xb0
[41850.615689] [<c0458ddb>] ? set_sta_flags+0x2b/0x40
[41850.615693] [<c0459955>] ieee80211_rx_mgmt_assoc_resp+0x565/0xd60
[41850.615699] [<c03b2ba4>] ? dev_queue_xmit+0xe4/0x5a0
[41850.615705] [<c03a85e8>] ? __kfree_skb+0x38/0x90
[41850.615708] [<c045ab50>] ? ieee80211_sta_work+0x0/0x760
[41850.615712] [<c045a7c3>] ieee80211_sta_rx_queued_mgmt+0x673/0xa00
[41850.615715] [<c03b1cfb>] ? dev_hard_start_xmit+0x25b/0x2f0
[41850.615719] [<c0148cc5>] ? sched_clock_cpu+0x135/0x190
[41850.615723] [<c011d0a9>] ? update_curr+0x99/0x200
[41850.615726] [<c0120426>] ? dequeue_entity+0x16/0x2a0
[41850.615730] [<c0121088>] ? dequeue_task_fair+0x68/0x70
[41850.615733] [<c011ddef>] ? dequeue_task+0xcf/0x130
[41850.615736] [<c03a81cd>] ? skb_dequeue+0x4d/0x70
[41850.615739] [<c045ab50>] ? ieee80211_sta_work+0x0/0x760
[41850.615743] [<c045abc1>] ieee80211_sta_work+0x71/0x760
[41850.615746] [<c0487e47>] ? schedule+0x3b7/0x9f0
[41850.615749] [<c045ab50>] ? ieee80211_sta_work+0x0/0x760
[41850.615754] [<c013fa4d>] run_workqueue+0x5d/0x110
[41850.615757] [<c013fb88>] worker_thread+0x88/0xf0
[41850.615760] [<c0143660>] ? autoremove_wake_function+0x0/0x50
[41850.615764] [<c013fb00>] ? worker_thread+0x0/0xf0
[41850.615767] [<c01432ec>] kthread+0x3c/0x70
[41850.615769] [<c01432b0>] ? kthread+0x0/0x70
[41850.615773] [<c0103e87>] kernel_thread_helper+0x7/0x10
[41850.615776] ---[ end trace 8289e1ba6ce8ea7b ]---
On Thu, 2009-01-15 at 18:13 +0100, Christian Lamparter wrote:
> On Thursday 15 January 2009 17:50:51 Harvey Harrison wrote:
> > On Thu, 2009-01-15 at 17:31 +0100, Christian Lamparter wrote:
> > > On Thursday 15 January 2009 16:33:11 Michael Buesch wrote:
> > > > On Wednesday 14 January 2009 23:51:20 Harvey Harrison wrote:
> > > > > Seeing lots of these WARN_ONS with current -git. Known issue?
> > > > >
> > > > > b43 hardware.
> > > > >
> > > > > [41850.615621] WARNING: at net/mac80211/rc80211_minstrel.c:69 minstrel_rate_init+0x92/0x3c0()
> > > >
> > > > I think that happens, if you have a b-only AP.
> > >
> > > erm, see : "minstrel: fix warning if lowest supported rate index is not 0"
> > > ( http://www.spinics.net/lists/linux-wireless/msg25799.html )
> > >
> > > The fix is in wireless-testing & wireless-next since a few days now...
> > > Or is this a new bug?
> >
> > I'll try that out shortly, report was against linus mainline.
> >
> Oh? with 2.6.28 or the current 2.6.29-rcX line?
> If you get this WARNING with 2.6.29-rcX, you don't have to worry...
> http://patchwork.kernel.org/patch/2184/
>
Yeah, somewhere a little past 2.6.29-rc1, thanks again.
Harvey
On Thursday 15 January 2009 16:33:11 Michael Buesch wrote:
> On Wednesday 14 January 2009 23:51:20 Harvey Harrison wrote:
> > Seeing lots of these WARN_ONS with current -git. Known issue?
> >
> > b43 hardware.
> >
> > [41850.615621] WARNING: at net/mac80211/rc80211_minstrel.c:69 minstrel_rate_init+0x92/0x3c0()
>
> I think that happens, if you have a b-only AP.
erm, see : "minstrel: fix warning if lowest supported rate index is not 0"
( http://www.spinics.net/lists/linux-wireless/msg25799.html )
The fix is in wireless-testing & wireless-next since a few days now...
Or is this a new bug?
Regards,
Chr
On Thu, 2009-01-15 at 17:31 +0100, Christian Lamparter wrote:
> On Thursday 15 January 2009 16:33:11 Michael Buesch wrote:
> > On Wednesday 14 January 2009 23:51:20 Harvey Harrison wrote:
> > > Seeing lots of these WARN_ONS with current -git. Known issue?
> > >
> > > b43 hardware.
> > >
> > > [41850.615621] WARNING: at net/mac80211/rc80211_minstrel.c:69 minstrel_rate_init+0x92/0x3c0()
> >
> > I think that happens, if you have a b-only AP.
>
> erm, see : "minstrel: fix warning if lowest supported rate index is not 0"
> ( http://www.spinics.net/lists/linux-wireless/msg25799.html )
>
> The fix is in wireless-testing & wireless-next since a few days now...
> Or is this a new bug?
I'll try that out shortly, report was against linus mainline.
Harvey
On Wednesday 14 January 2009 23:51:20 Harvey Harrison wrote:
> Seeing lots of these WARN_ONS with current -git. Known issue?
>
> b43 hardware.
>
> [41850.615621] WARNING: at net/mac80211/rc80211_minstrel.c:69 minstrel_rate_init+0x92/0x3c0()
I think that happens, if you have a b-only AP.
--
Greetings, Michael.
On Thursday 15 January 2009 17:50:51 Harvey Harrison wrote:
> On Thu, 2009-01-15 at 17:31 +0100, Christian Lamparter wrote:
> > On Thursday 15 January 2009 16:33:11 Michael Buesch wrote:
> > > On Wednesday 14 January 2009 23:51:20 Harvey Harrison wrote:
> > > > Seeing lots of these WARN_ONS with current -git. Known issue?
> > > >
> > > > b43 hardware.
> > > >
> > > > [41850.615621] WARNING: at net/mac80211/rc80211_minstrel.c:69 minstrel_rate_init+0x92/0x3c0()
> > >
> > > I think that happens, if you have a b-only AP.
> >
> > erm, see : "minstrel: fix warning if lowest supported rate index is not 0"
> > ( http://www.spinics.net/lists/linux-wireless/msg25799.html )
> >
> > The fix is in wireless-testing & wireless-next since a few days now...
> > Or is this a new bug?
>
> I'll try that out shortly, report was against linus mainline.
>
Oh? with 2.6.28 or the current 2.6.29-rcX line?
If you get this WARNING with 2.6.29-rcX, you don't have to worry...
http://patchwork.kernel.org/patch/2184/
Regards,
Chr