NETDEV WATCHDOG: wifi0: transmit timed out

NETDEV WATCHDOG: wifi0: transmit timed out

[Justin Mattock]

I should'nt be posting this, due to
having  tainted modules(madwifi), but
I figured I might as well:(below)

[ 5000.986044] NETDEV WATCHDOG: wifi0: transmit timed out
[ 5000.991959] ------------[ cut here ]------------
[ 5000.991964] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x95/0xe7()
[ 5000.991968] Modules linked in: hci_usb cpufreq_ondemand
cpufreq_performance cpufreq_powersave rfcomm hidp l2cap bluetooth
container battery fan ipmi_watchdog ipmi_msghandler isight_firmware
uinput wlan_tkip ieee80211_crypt_tkip ieee80211 ieee80211_crypt
arpt_mangle arptable_filter arp_tables nf_conntrack_ipv4 nf_conntrack
iptable_mangle iptable_filter ip_tables x_tables coretemp eeprom
acpi_cpufreq applesmc joydev appletouch uvcvideo wlan_scan_sta
ath_rate_sample ath_pci firewire_ohci wlan firewire_core fglrx(P)
snd_hda_intel ath_hal(P) snd_pcm snd_timer agpgart snd_page_alloc
snd_hwdep ohci1394 evdev thermal ath5k ieee1394 ehci_hcd uhci_hcd
pata_acpi video processor ac button sbshc
[ 5000.992067] Pid: 0, comm: swapper Tainted: P          2.6.26 #5
[ 5000.992075]  [<c0123487>] warn_on_slowpath+0x41/0x6b
[ 5000.992113]  [<f8de1cfc>] ? ath_reset+0x31c/0x372 [ath_pci]
[ 5000.992139]  [<f8de2298>] ? ath_tx_timeout+0xbc/0xd5 [ath_pci]
[ 5000.992156]  [<c0123e0e>] ? printk+0x15/0x17
[ 5000.992168]  [<c031d40a>] dev_watchdog+0x95/0xe7
[ 5000.992177]  [<c012ab73>] run_timer_softirq+0x11e/0x180
[ 5000.992185]  [<c031d375>] ? dev_watchdog+0x0/0xe7
[ 5000.992193]  [<c031d375>] ? dev_watchdog+0x0/0xe7
[ 5000.992204]  [<c01275c4>] __do_softirq+0x6d/0xdf
[ 5000.992215]  [<c012767e>] do_softirq+0x48/0x57
[ 5000.992223]  [<c012791e>] irq_exit+0x38/0x6b
[ 5000.992230]  [<c0110627>] smp_apic_timer_interrupt+0x6e/0x7f
[ 5000.992240]  [<c0103a38>] apic_timer_interrupt+0x28/0x30
[ 5000.992252]  [<c013007b>] ? sys_getpriority+0x153/0x190
[ 5000.992263]  [<c03983fe>] ? _spin_unlock_irqrestore+0xf/0x1a
[ 5000.992274]  [<c013b3a2>] tick_broadcast_oneshot_control+0xdd/0xe3
[ 5000.992286]  [<c013add8>] tick_notify+0x1cd/0x2e5
[ 5000.992295]  [<c024f822>] ? acpi_hw_low_level_write+0x8e/0xc1
[ 5000.992308]  [<c039a089>] notifier_call_chain+0x2b/0x4a
[ 5000.992320]  [<c0136d71>] __raw_notifier_call_chain+0xe/0x10
[ 5000.992329]  [<c0136d7f>] raw_notifier_call_chain+0xc/0xe
[ 5000.992337]  [<c013a826>] clockevents_do_notify+0x11/0x13
[ 5000.992345]  [<c013a844>] clockevents_notify+0x1c/0x5c
[ 5000.992354]  [<f8838b56>] acpi_state_timer_broadcast+0x31/0x34 [processor]
[ 5000.992371]  [<f88397b3>] acpi_idle_enter_bm+0x2cf/0x322 [processor]
[ 5000.992389]  [<c02e896b>] cpuidle_idle_call+0x5e/0x8b
[ 5000.992399]  [<c0101c04>] cpu_idle+0xc4/0xe4
[ 5000.992406]  [<c03946ae>] start_secondary+0x168/0x16d
[ 5000.992426]  =======================
[ 5000.992430] ---[ end trace 83ab3ac068df9439 ]---


-- 
Justin P. Mattock

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Arjan van de Ven]

On Mon, 28 Jul 2008 00:10:46 -0700
"Justin Mattock" <justinmattock@gmail.com> wrote:

> I should'nt be posting this, due to
> having  tainted modules(madwifi), but

and fglrx

> I figured I might as well:(below)
> 
> [ 5000.986044] NETDEV WATCHDOG: wifi0: transmit timed out

and what's more... it's the the wifi that's b0rked.

sounds like you want to switch to ath5k or ath9k.


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Justin Mattock]

On Mon, Jul 28, 2008 at 6:12 AM, Arjan van de Ven <arjan@infradead.org> wrote:
> On Mon, 28 Jul 2008 00:10:46 -0700
> "Justin Mattock" <justinmattock@gmail.com> wrote:
>
>> I should'nt be posting this, due to
>> having  tainted modules(madwifi), but
>
> and fglrx
>
>> I figured I might as well:(below)
>>
>> [ 5000.986044] NETDEV WATCHDOG: wifi0: transmit timed out
>
> and what's more... it's the the wifi that's b0rked.
>
> sounds like you want to switch to ath5k or ath9k.
>
>
> --
> If you want to reach me at my work email, use arjan@linux.intel.com
> For development, discussion and tips for power savings,
> visit http://www.lesswatts.org
>

If there's support for the 5418 card that the macbook pro has.
interesting when lspci I'm not seeing the card number(below is lspci)
As for the fglrx "f*&k it" too much of a pain.:


00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and
945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and
945GT Express PCI Express Root Port (rev 03)
00:07.0 Performance counters: Intel Corporation Unknown device 27a3 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
Port 3 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB
UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB
UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB
UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB
UHCI #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2
EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface
Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE
Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family)
Serial ATA Storage Controller IDE (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 71c5
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053
PCI-E Gigabit Ethernet Controller (rev 22)
03:00.0 Network controller: Atheros Communications, Inc. Unknown
device 0024 (rev 01)
0c:03.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b
Link Layer Controller (rev 01)

unkown device 0024!
I hope my wireless card isn't broken.
regards;
-- 
Justin P. Mattock

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Alistair John Strachan]

On Monday 28 July 2008 14:53:41 Justin Mattock wrote:
> On Mon, Jul 28, 2008 at 6:12 AM, Arjan van de Ven <arjan@infradead.org> 
wrote:
> > On Mon, 28 Jul 2008 00:10:46 -0700
> >
> > "Justin Mattock" <justinmattock@gmail.com> wrote:
> >> I should'nt be posting this, due to
> >> having  tainted modules(madwifi), but
> >
> > and fglrx
> >
> >> I figured I might as well:(below)
> >>
> >> [ 5000.986044] NETDEV WATCHDOG: wifi0: transmit timed out
> >
> > and what's more... it's the the wifi that's b0rked.
> >
> > sounds like you want to switch to ath5k or ath9k.
> >
> >
> > --
> > If you want to reach me at my work email, use arjan@linux.intel.com
> > For development, discussion and tips for power savings,
> > visit http://www.lesswatts.org
>
> If there's support for the 5418 card that the macbook pro has.
> interesting when lspci I'm not seeing the card number(below is lspci)
> As for the fglrx "f*&k it" too much of a pain.:

Yep check out the linux-wireless archives for more info, but ath9k is ready 
and working on your hardware. I've got a Macbook with the same chipset and 
it's totally fine (2.6.26+wireless-testing+ath9k).

-- 
Cheers,
Alistair.

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Justin Mattock]

On Mon, Jul 28, 2008 at 8:22 AM, Alistair John Strachan
<alistair@devzero.co.uk> wrote:
> On Monday 28 July 2008 14:53:41 Justin Mattock wrote:
>> On Mon, Jul 28, 2008 at 6:12 AM, Arjan van de Ven <arjan@infradead.org>
> wrote:
>> > On Mon, 28 Jul 2008 00:10:46 -0700
>> >
>> > "Justin Mattock" <justinmattock@gmail.com> wrote:
>> >> I should'nt be posting this, due to
>> >> having  tainted modules(madwifi), but
>> >
>> > and fglrx
>> >
>> >> I figured I might as well:(below)
>> >>
>> >> [ 5000.986044] NETDEV WATCHDOG: wifi0: transmit timed out
>> >
>> > and what's more... it's the the wifi that's b0rked.
>> >
>> > sounds like you want to switch to ath5k or ath9k.
>> >
>> >
>> > --
>> > If you want to reach me at my work email, use arjan@linux.intel.com
>> > For development, discussion and tips for power savings,
>> > visit http://www.lesswatts.org
>>
>> If there's support for the 5418 card that the macbook pro has.
>> interesting when lspci I'm not seeing the card number(below is lspci)
>> As for the fglrx "f*&k it" too much of a pain.:
>
> Yep check out the linux-wireless archives for more info, but ath9k is ready
> and working on your hardware. I've got a Macbook with the same chipset and
> it's totally fine (2.6.26+wireless-testing+ath9k).
>
> --
> Cheers,
> Alistair.
>

Alright!!
I'm glad to hear this.
"natural and fresh".

-- 
Justin P. Mattock

[PLEASE REVERT] "Add a WARN_ON_ONCE" at net/sched/sch_generic.c:

[Komuro]

Hi,

Please revert the patch "Add a WARN_ON_ONCE() to
 the transmit timeout function".

The transmit timeout sometimes happens on normal operation.
This message annoys me.


>net: Add a WARN_ON_ONCE() to the transmit timeout function
>
>WARN_ON_ONCE() gives a stack trace including the full module list.
>Having this in the kernel dump for the timeout case in the
>generic netdev watchdog will help us see quicker which driver
>is involved. It also allows us to collect statistics
>and patterns in terms of which drivers have this event occuring.
>
>Suggested by Andrew Morton
>
>Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
>Signed-off-by: David S. Miller <davem@davemloft.net>

Best Regards
Komuro

RE: NETDEV WATCHDOG: wifi0: transmit timed out

[Komuro]

Hi,

Please try to comment out the "WARN_ON_ONCE"
at net/sched/sched_generic.c.


--- linux-2.6.27-rc1/net/sched/sch_generic.c.orig	2008-07-29 21:45:36.000000000 +0900
+++ linux-2.6.27-rc1/net/sched/sch_generic.c	2008-07-29 21:45:54.000000000 +0900
@@ -216,7 +216,6 @@ static void dev_watchdog(unsigned long a
 				printk(KERN_INFO "NETDEV WATCHDOG: %s (%s): transmit timed out\n",
 				       dev->name, netdev_drivername(dev, drivername, 64));
 				dev->tx_timeout(dev);
-				WARN_ON_ONCE(1);
 			}
 			if (!mod_timer(&dev->watchdog_timer,
 				       round_jiffies(jiffies +



>I should'nt be posting this, due to
>having  tainted modules(madwifi), but
>I figured I might as well:(below)
>
>[ 5000.986044] NETDEV WATCHDOG: wifi0: transmit timed out
>[ 5000.991959] ------------[ cut here ]------------
>[ 5000.991964] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x95/0xe7()

Best Regards
Komuro

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Justin Mattock]

On Tue, Jul 29, 2008 at 5:53 AM, Komuro <komurojun-mbn@nifty.com> wrote:
> Hi,
>
> Please try to comment out the "WARN_ON_ONCE"
> at net/sched/sched_generic.c.
>
>
> --- linux-2.6.27-rc1/net/sched/sch_generic.c.orig       2008-07-29 21:45:36.000000000 +0900
> +++ linux-2.6.27-rc1/net/sched/sch_generic.c    2008-07-29 21:45:54.000000000 +0900
> @@ -216,7 +216,6 @@ static void dev_watchdog(unsigned long a
>                                printk(KERN_INFO "NETDEV WATCHDOG: %s (%s): transmit timed out\n",
>                                       dev->name, netdev_drivername(dev, drivername, 64));
>                                dev->tx_timeout(dev);
> -                               WARN_ON_ONCE(1);
>                        }
>                        if (!mod_timer(&dev->watchdog_timer,
>                                       round_jiffies(jiffies +
>
>
>
>>I should'nt be posting this, due to
>>having  tainted modules(madwifi), but
>>I figured I might as well:(below)
>>
>>[ 5000.986044] NETDEV WATCHDOG: wifi0: transmit timed out
>>[ 5000.991959] ------------[ cut here ]------------
>>[ 5000.991964] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x95/0xe7()
>
> Best Regards
> Komuro
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Cool thanks for the patch.
I'll plug it in and see if I get this message again.

-- 
Justin P. Mattock

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Arjan van de Ven]

On Tue, 29 Jul 2008 21:53:15 +0900
Komuro <komurojun-mbn@nifty.com> wrote:

> Hi,
> 
> Please try to comment out the "WARN_ON_ONCE"
> at net/sched/sched_generic.c.
> 

"I have a hardware failure so I'll comment out the message that says
so, and then I won't have a failure". Yeah that'll work well.

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[David Miller]

From: Arjan van de Ven <arjan@infradead.org>
Date: Tue, 29 Jul 2008 06:58:59 -0700

> On Tue, 29 Jul 2008 21:53:15 +0900
> Komuro <komurojun-mbn@nifty.com> wrote:
> 
> > Hi,
> > 
> > Please try to comment out the "WARN_ON_ONCE"
> > at net/sched/sched_generic.c.
> > 
> 
> "I have a hardware failure so I'll comment out the message that says
> so, and then I won't have a failure". Yeah that'll work well.

Yes, this is indeed a recidulious suggestion, to hide the problem
instead of trying to figure out what it might actually be.

Komuro has a serious problem accepting the fact that this condition is
in fact an abnormal error should should be logged, and he keeps
pushing to get this WARN_ON() removed over and over again.

I'm just ignoring him at this point.

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Justin Mattock]

On Tue, Jul 29, 2008 at 1:47 PM, David Miller <davem@davemloft.net> wrote:
> From: Arjan van de Ven <arjan@infradead.org>
> Date: Tue, 29 Jul 2008 06:58:59 -0700
>
>> On Tue, 29 Jul 2008 21:53:15 +0900
>> Komuro <komurojun-mbn@nifty.com> wrote:
>>
>> > Hi,
>> >
>> > Please try to comment out the "WARN_ON_ONCE"
>> > at net/sched/sched_generic.c.
>> >
>>
>> "I have a hardware failure so I'll comment out the message that says
>> so, and then I won't have a failure". Yeah that'll work well.
>
> Yes, this is indeed a recidulious suggestion, to hide the problem
> instead of trying to figure out what it might actually be.
>
> Komuro has a serious problem accepting the fact that this condition is
> in fact an abnormal error should should be logged, and he keeps
> pushing to get this WARN_ON() removed over and over again.
>
> I'm just ignoring him at this point.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

I should of mentioned the madwifi module I've been
using is from february, so maybe madwifi took care of this already.
As for experimanting with ath9k I pulled yesterday and compiled,
but from what I saw ath9k seems to not handle wpa keys that well.
so back to madwifi until later on.

-- 
Justin P. Mattock

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Dan Williams]

On Tue, 2008-07-29 at 15:48 -0700, Justin Mattock wrote:
> On Tue, Jul 29, 2008 at 1:47 PM, David Miller <davem@davemloft.net> wrote:
> > From: Arjan van de Ven <arjan@infradead.org>
> > Date: Tue, 29 Jul 2008 06:58:59 -0700
> >
> >> On Tue, 29 Jul 2008 21:53:15 +0900
> >> Komuro <komurojun-mbn@nifty.com> wrote:
> >>
> >> > Hi,
> >> >
> >> > Please try to comment out the "WARN_ON_ONCE"
> >> > at net/sched/sched_generic.c.
> >> >
> >>
> >> "I have a hardware failure so I'll comment out the message that says
> >> so, and then I won't have a failure". Yeah that'll work well.
> >
> > Yes, this is indeed a recidulious suggestion, to hide the problem
> > instead of trying to figure out what it might actually be.
> >
> > Komuro has a serious problem accepting the fact that this condition is
> > in fact an abnormal error should should be logged, and he keeps
> > pushing to get this WARN_ON() removed over and over again.
> >
> > I'm just ignoring him at this point.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >
> 
> I should of mentioned the madwifi module I've been
> using is from february, so maybe madwifi took care of this already.
> As for experimanting with ath9k I pulled yesterday and compiled,
> but from what I saw ath9k seems to not handle wpa keys that well.
> so back to madwifi until later on.

ath9k certainly should handle WPA keys; the hardware and driver really
don't care what the key type is because all that is taken care of by
mac80211.  What specific issues were you having with ath9k?  There's
some generic mac80211 breakage going on right now while people figure
out how to fix the skb->cb situation that Dave's multiqueue stuff
exposed, which might be screwing up ath9k for you.

Dan

Re: Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Komuro]

>
>"I have a hardware failure so I'll comment out the message that says
>so, and then I won't have a failure". Yeah that'll work well.


O.K. The madwifi should be fixed.
Thanks,


Best Regards
Komuro

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Arjan van de Ven]

On Wed, 30 Jul 2008 20:48:55 +0900 (JST)
Komuro <komurojun-mbn@nifty.com> wrote:

> 
> >
> >"I have a hardware failure so I'll comment out the message that says
> >so, and then I won't have a failure". Yeah that'll work well.
> 
> 
> O.K. The madwifi should be fixed.
> Thanks,

madwifi has many bigger issues; it's been number 1 in the kerneloops
top 10 for months and months now.

Feel free to fix it.. I can't.. it's a proprietary/binary driver.

-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

Re: NETDEV WATCHDOG: wifi0: transmit timed out

[Justin Mattock]

On Wed, Jul 30, 2008 at 6:22 AM, Arjan van de Ven <arjan@infradead.org> wrote:
> On Wed, 30 Jul 2008 20:48:55 +0900 (JST)
> Komuro <komurojun-mbn@nifty.com> wrote:
>
>>
>> >
>> >"I have a hardware failure so I'll comment out the message that says
>> >so, and then I won't have a failure". Yeah that'll work well.
>>
>>
>> O.K. The madwifi should be fixed.
>> Thanks,
>
> madwifi has many bigger issues; it's been number 1 in the kerneloops
> top 10 for months and months now.
>
> Feel free to fix it.. I can't.. it's a proprietary/binary driver.
>
> --
> If you want to reach me at my work email, use arjan@linux.intel.com
> For development, discussion and tips for power savings,
> visit http://www.lesswatts.org
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

I should of written down the error that it was
giving(I can pull again to get the exact error)
from what I remember it was able to do the handshake
but wpa_supplicant would say CTRL-EVENT-CONNECTED then
CTRL-EVENT-DISCONNECTED
if its possible I would like to pull the wireless testing directory
and add that to 2.6.27-rc1. this way I can run ath9k, and the fresh
git "hot out of the oven",
I do have another computer now so reporting problems
makes it a whole lot easier than having one computer.

-- 
Justin P. Mattock