GNOME freezes when wifi associates

Bug #800798 reported by Greg Gorman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Using any kernel later than the one that I wrote this report with, whenever wifi associates with a station GNOME freezes and you have to power cycle.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-30-generic-pae 2.6.32-30.59
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-30.59-generic-pae 2.6.32.29+drm33.13
Uname: Linux 2.6.32-30-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ggo 975 F.... pulseaudio
 /dev/snd/pcmC0D0p: ggo 975 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2520000 irq 17'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:14f15069,17aa2155,00100302 HDA:80862804,80860101,00100000'
   Controls : 11
   Simple ctrls : 6
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6QHT31WW-1.12'
   Mixer name : 'ThinkPad EC 6QHT31WW-1.12'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Wed Jun 22 10:07:37 2011
HibernationDevice: RESUME=UUID=a926ba21-8c7f-4bf2-8c87-cdb546b80ab3
MachineType: LENOVO 3626A57
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-30-generic-pae root=UUID=e7a3f7ad-4648-4080-9908-197967ed8d4e ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
 LC_PAPER=en_US.UTF-8
RelatedPackageVersions: linux-firmware 1.34.7
SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 10/26/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET61WW (1.31 )
dmi.board.name: 3626A57
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6QET61WW(1.31):bd10/26/2010:svnLENOVO:pn3626A57:pvrThinkPadX201:rvnLENOVO:rn3626A57:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3626A57
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO

Revision history for this message
Greg Gorman (gregg-public) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

Which specific kernel versions did you test? I figure 2.6.32-32.62 is broken - have you tried 2.6.32-33.68, currently sitting in -proposed (https://wiki.ubuntu.com/Testing/EnableProposed)?

Revision history for this message
Greg Gorman (gregg-public) wrote :

@Julian - I'll enable -proposed and check. This is my personal workstation and hard to experiment on during the day because of my 'real' job :) Needs to be stable & dependable.

Revision history for this message
Greg Gorman (gregg-public) wrote :

@Julian - ok had time to enable the -proposed repos and update. Good news, seems to work! Will connect now and not cause GNOME to hang. Gets my vote!

ggo@ggo-laptop:~$ uname -a
Linux ggo-laptop.x.y.com 2.6.32-33-generic-pae #69-Ubuntu SMP Mon Jun 27 16:53:18 UTC 2011 i686 GNU/Linux
ggo@ggo-laptop:~$

Revision history for this message
Greg Gorman (gregg-public) wrote :

I did get a freeze up today, but wow will it be hard to figure out.
VPN was active
VMWare Windows XP session up
practically all 8Gb in use

tried to switch to different wifi network, GNOME froze the instant it associated.

couldn't duplicate it again. :(

Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

Alright - there's a known regression affecting only pae-kernels, where 2.6.32-31.61 is good and 2.6.32-32.62 is bad (see bug #805209).
You said that "any kernel later" than 2.6.32-30.59 is causing this problem - was 2.6.32-31.61 part of your tests?

Revision history for this message
Greg Gorman (gregg-public) wrote :

@Julian - it's a challenge because I probably didn't test every single one of them. I ran every PAE kernel from 59 that was in -stable and saw the lockup issue. Following the suggestion to enable -proposed I am running 69. Haven't tried any others at this point. A quick look at my grub2 config lists these.

I'm pretty sure I tried each PAE to find one that wouldn't lock up. The 'best' one was the one I used to write the bug with. I can try rebooting 31.61 to be sure if you would like me to.

2.6.32-33-generic-pae
2.6.32-33-generic
2.6.32-32-generic-pae
2.6.32-32-generic
2.6.32-31-generic-pae
2.6.32-31-generic
2.6.32-30-generic-pae
2.6.32-30-generic
2.6.32-29-generic-pae
2.6.32-29-generic
2.6.32-28-generic-pae
2.6.32-28-generic
2.6.32-27-generic

Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

Well, testing whether this can be reproduced on 31.61 (or for that matter, any non-pae kernel) would definitely help in isolating the issue.
There's no reason to continue using 33.69 from -proposed, now that you determined it's still broken.

Revision history for this message
Greg Gorman (gregg-public) wrote :

Hi Julian, booted 31.61 PAE and seems to be holding so far. 33.69 PAE worked for a long time and then seemed to lock up once I've used VMWare with a huge image and then closed it.

I'll try 31.61 non-PAE later this evening.

I'll keep running 31.61 PAE for a bit & post if it croaks.

Revision history for this message
Greg Gorman (gregg-public) wrote :

Came in this morning and the system was locked up. Worked great from the time I posted until I left for the night. Here's the last bit in the 'messages' file from the 11th. Most of the other messages are firewall messages about 1x / 10sec.

Jul 11 19:46:20 ggo-laptop kernel: [27927.129173] FIREWALL:IN=wlan2 OUT= MAC=ff:ff:ff:ff:ff:ff:c4:3d:c7:b7:86:a2:08:00 SRC=192.168.222.100 DST=192.168.222.255 LEN=198 TOS=0x00 PREC=0x00 TTL=128 ID=4288 PROTO=UDP SPT=6646 DPT=6646 LEN=178
Jul 11 19:46:29 ggo-laptop kernel: [27935.632873] FIREWALL:IN=wlan2 OUT= MAC=ff:ff:ff:ff:ff:ff:30:46:9a:96:76:bc:08:00 SRC=192.168.222.1 DST=192.168.222.255 LEN=72 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=520 DPT=520 LEN=52
Jul 11 19:46:32 ggo-laptop kernel: [27938.806821] bridge-wlan2: is a Wireless Adapter
Jul 11 19:46:35 ggo-laptop bonobo-activation-server (ggo-21199): could not associate with desktop session: Failed to connect to socket /tmp/dbus-N3RASrv3xg: Connection refused

Revision history for this message
Greg Gorman (gregg-public) wrote :

Booted latest kernel as discussed in bug #805209. Seems to associate without hanging up. Will let it run overnight to see how it goes.

ggo@ggo-laptop:~$ uname -a
Linux ggo-laptop.us.ibm.com 2.6.32-33-generic-pae #70-Ubuntu SMP Thu Jul 7 22:51:12 UTC 2011 i686 GNU/Linux

Revision history for this message
Greg Gorman (gregg-public) wrote :

Seems to be working, stayed up overnight without lockup. I'm going to mark as duplicate of bug #805209, change if you disagree.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.