[Intrepid] Random system freeze (possibly linked to wireless card driver - Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61))

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 276990, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

I'm not sure if this is a duplicate.They mention it happens with 802.11n... I wasn't aware that the network I was connecting to was 802.11n, in facrt it was also happening when I was associating/deassociating.

How can I tell which standard is in use (it happens on university WiFi, and I don't know who's responsible for managing it, so I don't know who to ask.)

Also unlike other people in that bug, I'm unable to switch to the console. Once system freezes, it's completly frozen, I can't switch to other consoles.

Though once it will be resolved, I'll see if that will fix my bug too.

Derek, one of the people on the other bug reported kernel panics on 802.11g networks as well. When you are at University use this command in terminal

iwconfig wlan0 | grep 802

it will give you and output similar to this

wlan0 IEEE 802.11abgn ESSID:**********

The letters after 802.11 determine what kind of wifi you are using. If either g or n is in there then you most likely are experiencing the same issue as the people in my other bug report.

On Fri, 2008-10-17 at 15:41 +0000, Derek Kulinski wrote:
> Also unlike other people in that bug, I'm unable to switch to the
> console. Once system freezes, it's completly frozen, I can't switch to
> other consoles.

syko21 replied to the other bits, but to this part, they can't switch to
console after the kernel panic. That wouldn't be possible. What
they're doing is connecting, going to console, and working from there
while they wait for the kernel panic so that they can see it happen.

I have IEEE 802.11abgn, but doesn't this show the capabilities of my card, and not the AP mode?
Didn't the bug happen when specific protocol is used?

I'll try the recommended driver and see if it works.

The driver seems to be the problem since it isn't happening just with
802.11n on that bug. N is only mentioned, I think, because this is the
only Intel card capable of doing N (if not the only built-in wireless
card in general).