Openmoko Bug #2333: Intermittent kernel oops when using wifi

Openmoko Public Trac bugs at
Mon Mar 1 22:56:43 CET 2010

#2333: Intermittent kernel oops when using wifi
 Reporter:  bt4      |          Owner:  openmoko-devel
     Type:  defect   |         Status:  new           
 Priority:  normal   |      Milestone:                
Component:  unknown  |        Version:  unspecified   
 Severity:  normal   |       Keywords:  wlan oops     
 Haspatch:  0        |      Blockedby:                
Estimated:           |    Patchreview:                
 Blocking:           |   Reproducible:                
 I'm running SHR-Unstable which is up to date as of today (1st march 2010).

 The Kernel version is :-
 Linux om-gta02 2.6.29-rc3 #1 PREEMPT Fri Feb 5 18:47:47 CET 2010 armv4tl

 SHR version number in OPKG is :-

 I have stated that this is an intermittent problem as I am still working
 on a reliable method to reproduce it. I use the NWA (GUI) wifi manager and
 this error regularly occurs forcing me to remove the battery from my
 Freerunner in order to get it working again.

 So far I have been able to reproduce the issue at will using NWA like this

 1. I create two profiles in NWA :-
    a) An WPA-Enterprise network with PEAP and RADIUS server cert
    defined and no MAC address defined
    b) An Open network with a MAC address defined

 2. I then enabled these profiles (in NWA) and also enabled the profile
 called "any_open".

 3. Then sited the Freerunner in a location where non of the profiles
 specified in (1) above are withing range, but there is a third open
 network with a weak signal (Quality=4/94  Signal level=-91 dBm  Noise
 level=-95 dBm).

 4. Let NWA associate with the weak access point (I don't know what
 this AP is; its's just a signal I picked up from my house). I see this
 in dmesg :-
 [  887.860000] AR6000 connected event on freq 2437 with bssid
 00:22:75:dd:76:51  listenInterval=100, beaconInterval = 100, beaconIeLen =
 0 assocReqLen=41
 assocRespLen =59
 [  887.860000] Network: Infrastructure

 5. The signal is weak and I do not recieve a DHCP lease (perhaps the
 UDP does not go well over weak wifi) but NWA says "Connected".

 6. I now disable the "any_open" profile in NWA and see this in dmesg :-
 [  931.290000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [  941.610000] eth0: no IPv6 routers present

 7. Now I quit NWA and although it appears to exit OK, this is when I
 see the Kernel Oops.

 Others have reported this issue to the mailing list so I am hoping we can
 come up with a more concrete method to reproduce this. I will keep working
 on it and if I come up with anything better I will update this bug report.

Ticket URL: <> <>
openmoko trac

More information about the buglog mailing list