Re: iwlwifi can't connect to router after resuming from suspend.
Thanks Dan, Kevin, [...] [suspend/resume] > [ 58.835223] wlan0: authenticate with 30:46:9a:68:a9:52 > [ 58.864519] wlan0: send auth to 30:46:9a:68:a9:52 (try 1/3) > [ 59.067596] wlan0: send auth to 30:46:9a:68:a9:52 (try 2/3) > [ 59.271484] wlan0: send auth to 30:46:9a:68:a9:52 (try 3/3) > [ 59.475356] wlan0: authentication with 30:46:9a:68:a9:52 timed out Yeah ... we saw this in the lab at some point, but somehow we couldn't reproduce it again later. The issue is that we stop the queues, and never restart them, and if it's the same issue then it's definitely the driver's fault. To confirm, when you get this, can you please do sudo cat /sys/kernel/debug/ieee80211/phy*/queues (assuming you have mac80211 debugfs compiled) If it's really the same bug, the first four queues (0-3) will show something like 00: 0x0001/7 01: 0x0001/0 02: 0x0001/0 03: 0x0001/0 [...] If this is the case, then I'd appreciate if you could do tracing. To do that, make sure CONFIG_IWLWIFI_DEVICE_TRACING is set in your kernel config (which requires CONFIG_EVENT_TRACING, you can use the / key in menuconfig to search for items). When you have that, grab the trace-cmd tool (ubuntu ships it now I believe) and start tracing *before* you suspend: sudo bash -c "echo global > /sys/kernel/debug/tracing/trace_clock" sudo trace-cmd record -e mac80211 -e iwlwifi -e iwlwifi_msg then suspend and resume while it's running, and ctrl-c later after it failed to connect after resuming. Then you get a file "trace.dat", compress it and send it to me privately (it's large, and may contain information you might consider private, like your AP name/BSSID/etc.) Thanks! If that's too much effort, let me know and I'll try to reproduce, but I'll probably need to have more info on your setup etc. as I haven't been able to reproduce this in mine yet, but I also have issues with suspend/resume anyway quite frequently :-( johannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: iwlwifi can't connect to router after resuming from suspend.
Thanks Dan, Kevin, [...] [suspend/resume] [ 58.835223] wlan0: authenticate with 30:46:9a:68:a9:52 [ 58.864519] wlan0: send auth to 30:46:9a:68:a9:52 (try 1/3) [ 59.067596] wlan0: send auth to 30:46:9a:68:a9:52 (try 2/3) [ 59.271484] wlan0: send auth to 30:46:9a:68:a9:52 (try 3/3) [ 59.475356] wlan0: authentication with 30:46:9a:68:a9:52 timed out Yeah ... we saw this in the lab at some point, but somehow we couldn't reproduce it again later. The issue is that we stop the queues, and never restart them, and if it's the same issue then it's definitely the driver's fault. To confirm, when you get this, can you please do sudo cat /sys/kernel/debug/ieee80211/phy*/queues (assuming you have mac80211 debugfs compiled) If it's really the same bug, the first four queues (0-3) will show something like 00: 0x0001/7 01: 0x0001/0 02: 0x0001/0 03: 0x0001/0 [...] If this is the case, then I'd appreciate if you could do tracing. To do that, make sure CONFIG_IWLWIFI_DEVICE_TRACING is set in your kernel config (which requires CONFIG_EVENT_TRACING, you can use the / key in menuconfig to search for items). When you have that, grab the trace-cmd tool (ubuntu ships it now I believe) and start tracing *before* you suspend: sudo bash -c echo global /sys/kernel/debug/tracing/trace_clock sudo trace-cmd record -e mac80211 -e iwlwifi -e iwlwifi_msg then suspend and resume while it's running, and ctrl-c later after it failed to connect after resuming. Then you get a file trace.dat, compress it and send it to me privately (it's large, and may contain information you might consider private, like your AP name/BSSID/etc.) Thanks! If that's too much effort, let me know and I'll try to reproduce, but I'll probably need to have more info on your setup etc. as I haven't been able to reproduce this in mine yet, but I also have issues with suspend/resume anyway quite frequently :-( johannes -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: iwlwifi can't connect to router after resuming from suspend.
On Fri, Sep 28, 2012 at 03:15:15PM -0700, Kevin Cruz wrote: > Hey Dan, > > > Thanks for the response. > > >> Linux cyber-ubuntu 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC > >> 2012 x86_64 x86_64 x86_64 GNU/Linux > > > That kernel is too old. Can you test with a 3.5.x kernel (or even > > better would be a 3.6-rc kernel). Those are the only ones we look > > at on lkml. > > I did try out Sabayon 10 live disk because it said it uses the kernel 3.5.4 > but it did not fix the problem. I will definitely try to figure a way to > test the 3.6-rc kernel. Do you know any (experimental?) distros that are > using it? Is there anything else that I could do that could help, like > rerunning any commands/script on a newer kernel? You can compile it under ubuntu. I looked on google to find directions but everyone had bad advice. This might work: apt-get build-dep linux-image-$(uname -r) download and unpack the kernel from kernel.org make localmodconfig make make modules_install install reboot If it doesn't then having the dmesg from Sabayon live disk will have to be enough. We can open a bug for that on bugzilla and CC the wireless people. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: iwlwifi can't connect to router after resuming from suspend.
On Fri, Sep 28, 2012 at 03:15:15PM -0700, Kevin Cruz wrote: Hey Dan, Thanks for the response. Linux cyber-ubuntu 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux That kernel is too old. Can you test with a 3.5.x kernel (or even better would be a 3.6-rc kernel). Those are the only ones we look at on lkml. I did try out Sabayon 10 live disk because it said it uses the kernel 3.5.4 but it did not fix the problem. I will definitely try to figure a way to test the 3.6-rc kernel. Do you know any (experimental?) distros that are using it? Is there anything else that I could do that could help, like rerunning any commands/script on a newer kernel? You can compile it under ubuntu. I looked on google to find directions but everyone had bad advice. This might work: apt-get build-dep linux-image-$(uname -r) download and unpack the kernel from kernel.org make localmodconfig make make modules_install install reboot If it doesn't then having the dmesg from Sabayon live disk will have to be enough. We can open a bug for that on bugzilla and CC the wireless people. regards, dan carpenter -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: iwlwifi can't connect to router after resuming from suspend.
Hey Dan, Thanks for the response. >> Linux cyber-ubuntu 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC >> 2012 x86_64 x86_64 x86_64 GNU/Linux > That kernel is too old. Can you test with a 3.5.x kernel (or even > better would be a 3.6-rc kernel). Those are the only ones we look > at on lkml. I did try out Sabayon 10 live disk because it said it uses the kernel 3.5.4 but it did not fix the problem. I will definitely try to figure a way to test the 3.6-rc kernel. Do you know any (experimental?) distros that are using it? Is there anything else that I could do that could help, like rerunning any commands/script on a newer kernel? I eventually plan to purchase a [different wireless card][1] and if it does not work, we will know that the problem is not in the wireless driver/card. I'm betting it will fix it for me but I can't be certain. The bug I'm having may be an ACPI or some power management issue as far as I can tell. I'll still be interested in fixing the issue on my current wireless card if the new card fixes the problem. I'm not sure when this will happen though. [1]: https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-half-height-mini-pcie-card Thanks, Kevin. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: iwlwifi can't connect to router after resuming from suspend.
Hi Kevin, > Linux cyber-ubuntu 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC > 2012 x86_64 x86_64 x86_64 GNU/Linux That kernel is too old. Can you test with a 3.5.x kernel (or even better would be a 3.6-rc kernel). Those are the only ones we look at on lkml. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: iwlwifi can't connect to router after resuming from suspend.
Hi Kevin, Linux cyber-ubuntu 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux That kernel is too old. Can you test with a 3.5.x kernel (or even better would be a 3.6-rc kernel). Those are the only ones we look at on lkml. regards, dan carpenter -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: iwlwifi can't connect to router after resuming from suspend.
Hey Dan, Thanks for the response. Linux cyber-ubuntu 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux That kernel is too old. Can you test with a 3.5.x kernel (or even better would be a 3.6-rc kernel). Those are the only ones we look at on lkml. I did try out Sabayon 10 live disk because it said it uses the kernel 3.5.4 but it did not fix the problem. I will definitely try to figure a way to test the 3.6-rc kernel. Do you know any (experimental?) distros that are using it? Is there anything else that I could do that could help, like rerunning any commands/script on a newer kernel? I eventually plan to purchase a [different wireless card][1] and if it does not work, we will know that the problem is not in the wireless driver/card. I'm betting it will fix it for me but I can't be certain. The bug I'm having may be an ACPI or some power management issue as far as I can tell. I'll still be interested in fixing the issue on my current wireless card if the new card fixes the problem. I'm not sure when this will happen though. [1]: https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-half-height-mini-pcie-card Thanks, Kevin. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
