N wifi broke after kernel update

[Genes MailLists]

  Wireless stopped working after latest kernel update.

  It connects and works fine using wired/

  It connects and works fine with wireless until I use it for more than
a host check and a ping check.

  Shortly after trying to use the connection (heavy load from chrome
restoring a lot of saved tabs) - it stops = NM thinks its ok - ifconfig
wlan0 shows it has an ip - iwconfig looks normal.

   However I cannot ping the default route any longer.

   /var/log/messages shows nothing iwlagn related - no oops etc
   wpa_supplicant remains quiet.


   rebooting produces same result with  kernel is 2.6.32.10-90 (x86_64).

   rmmod iwlagn; modprobe iwlagn ===> does not revive it.

   Booting back to older  kernel-2.6.9-70 works fine - so problem is
only in the newer kernel.

   I did not see this using same computer earlier on a 802.11g network -
so it seesm its only with N.


Filed bug:  https://bugzilla.redhat.com/show_bug.cgi?id=578663

  gene

[Sam Varshavchik]

Mail Lists writes:

>  
>    Wireless stopped working after latest kernel update.
>  
>    It connects and works fine using wired/
>  
>    It connects and works fine with wireless until I use it for more than
>  a host check and a ping check.
>  
>    Shortly after trying to use the connection (heavy load from chrome
>  restoring a lot of saved tabs) - it stops = NM thinks its ok - ifconfig
>  wlan0 shows it has an ip - iwconfig looks normal.
>  
>     However I cannot ping the default route any longer.
>  
>     /var/log/messages shows nothing iwlagn related - no oops etc
>     wpa_supplicant remains quiet.
>  
>  
>     rebooting produces same result with  kernel is 2.6.32.10-90 (x86_64).
>  
>     rmmod iwlagn; modprobe iwlagn ===> does not revive it.
>  
>     Booting back to older  kernel-2.6.9-70 works fine - so problem is
>  only in the newer kernel.
>  
>     I did not see this using same computer earlier on a 802.11g network -
>  so it seesm its only with N.
>  
>  
>  Filed bug:  https://bugzilla.redhat.com/show_bug.cgi?id=578663 
For your bug report to be useful to the kernel developers, you need to 
include, after booting the kernel in question:

1) The output of 'lspci -v'

2) The output of 'lsmod'

3) The output of 'dmesg'

In the meantime you can go back to the older kernel. This kind of stuff 
happens occasionally, and that's why you can easily roll back to an earlier 
kernel. I've lost count how many times, out of the blue, one of my machines 
couldn't run with a new kernel, so I got stuck with an older one, for a 
while, until it got fixed. Right now one of my laptops is occasionally 
crashing the 2.6.32.9 kernel series, so it's running the previous one. I'll 
try the new 2.6.32.10 kernel this weekend to see if it fixes it.

[Genes MailLists]

On 03/31/2010 09:15 PM, Mail Lists wrote:
>  
>    Wireless stopped working after latest kernel update. 
  ...

>  
>  Filed bug:  https://bugzilla.redhat.com/show_bug.cgi?id=578663
>   
  Happy to report this has already been fixed (thank you john
linville!!) in the 2.6.32.10-94.fc12 kernel build available in koji.

  gene

[Genes MailLists]

On 03/31/2010 09:39 PM, Mail Lists wrote:
>  On 03/31/2010 09:27 PM, Antonio Olivares wrote:
>  
> >
> > Gene,
> >
> > Out of curiosity, did you check ipv6 settings?  You might have only ipv4 network, and
> ipv6 settings are enabled by default?
> >
> > I had such a case and I was cursing the new kernels, I wanted to write bug reports
> and do a bunch of things, I went to the Administrator of the network and blamed it on him,
> because wired connections would work and this one would not , I checked the settings again
> and again, several times over, saw the ipv6 check and removed it and solved the problem by
> myself :) I hope a solution like this is possible for you, if not, I still tried and
> shared my story.
> >
> > Regards,
> >
> > Antonio 
> >
> >      
>  
>  
>    I thought about that too but IPV6 is set to 'ignore' in nm-applet -
>  unless there is somewhere else that needs it ? 

   I do see AAAA dns requests but only after A request fails - which of
course happens when network is down. I dont know who is doing IP6
requests tho' ..

[Genes MailLists]

On 03/31/2010 09:27 PM, Antonio Olivares wrote:

>  
>  Gene,
>  
>  Out of curiosity, did you check ipv6 settings?  You might have only ipv4 network, and
> ipv6 settings are enabled by default?
>  
>  I had such a case and I was cursing the new kernels, I wanted to write bug reports and do
> a bunch of things, I went to the Administrator of the network and blamed it on him,
> because wired connections would work and this one would not , I checked the settings again
> and again, several times over, saw the ipv6 check and removed it and solved the problem by
> myself :) I hope a solution like this is possible for you, if not, I still tried and
> shared my story.
>  
>  Regards,
>  
>  Antonio 
>  
>        

  I thought about that too but IPV6 is set to 'ignore' in nm-applet -
unless there is somewhere else that needs it ?

[Antonio Olivares]

--- On Wed, 3/31/10, Mail Lists <lists(a)sapience.com&gt; wrote:

>  From: Mail Lists <lists(a)sapience.com&gt;
>  Subject: N  wifi broke after kernel update
>  To: "Fedora." <users(a)lists.fedoraproject.org&gt;
>  Date: Wednesday, March 31, 2010, 6:15 PM
>  
>    Wireless stopped working after latest kernel
>  update.
>  
>    It connects and works fine using wired/
>  
>    It connects and works fine with wireless until I use
>  it for more than
>  a host check and a ping check.
>  
>    Shortly after trying to use the connection (heavy
>  load from chrome
>  restoring a lot of saved tabs) - it stops = NM thinks its
>  ok - ifconfig
>  wlan0 shows it has an ip - iwconfig looks normal.
>  
>     However I cannot ping the default route
>  any longer.
>  
>     /var/log/messages shows nothing iwlagn
>  related - no oops etc
>     wpa_supplicant remains quiet.
>  
>  
>     rebooting produces same result with 
>  kernel is 2.6.32.10-90 (x86_64).
>  
>     rmmod iwlagn; modprobe iwlagn ===>
>  does not revive it.
>  
>     Booting back to older 
>  kernel-2.6.9-70 works fine - so problem is
>  only in the newer kernel.
>  
>     I did not see this using same computer
>  earlier on a 802.11g network -
>  so it seesm its only with N.
>  
>  
>  Filed bug:  https://bugzilla.redhat.com/show_bug.cgi?id=578663
>  
>    gene
>  
>  
>  
>  --  
Gene,

Out of curiosity, did you check ipv6 settings?  You might have only ipv4 network, and ipv6
settings are enabled by default?

I had such a case and I was cursing the new kernels, I wanted to write bug reports and do
a bunch of things, I went to the Administrator of the network and blamed it on him,
because wired connections would work and this one would not , I checked the settings again
and again, several times over, saw the ipv6 check and removed it and solved the problem by
myself :) I hope a solution like this is possible for you, if not, I still tried and
shared my story.

Regards,

Antonio