Openmoko Bug #2327: wifi sometimes fails to start with "ar6000_activate: Failed to activate -4" when DEBUG_KERNEL/PREEMPT are disabled

Openmoko Public Trac bugs at docs.openmoko.org
Wed Jan 13 09:25:14 CET 2010


#2327: wifi sometimes fails to start with "ar6000_activate: Failed to activate -4"
when DEBUG_KERNEL/PREEMPT are disabled
-----------------------------+----------------------------------------------
 Reporter:  lindi            |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                 
Component:  System Software  |        Version:                 
 Severity:  normal           |       Keywords:                 
 Haspatch:  0                |      Blockedby:                 
Estimated:                   |    Patchreview:                 
 Blocking:                   |   Reproducible:  sometimes      
-----------------------------+----------------------------------------------
 Steps to reproduce:
 1) echo s3c2440-sdi > /sys/bus/platform/drivers/s3c2440-sdi/bind
 2) ip link show

 Expected results:
 2) the wifi interface appears in the list

 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 2: usb: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
 UP qlen 1000
     link/ether 00:1f:11:01:1f:6b brd ff:ff:ff:ff:ff:ff
 33: wlan: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
     link/ether 00:12:cf:8e:ee:09 brd ff:ff:ff:ff:ff:ff

 Actual results:
 2) the wifi interface does not appear in the list

 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 2: usb: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
 UP qlen 1000
     link/ether 00:1f:11:01:1f:6b brd ff:ff:ff:ff:ff:ff

 More info:
 1) This started to happen when I upgraded from andy-tracking
 a3587e4ed77974ad to andy-tracking a15608f241a40b41 and disabled
 CONFIG_DEBUG_KERNEL and CONFIG_PREEMPT.
 2) I have hit the bug now three times and used wifi succesfully at least
 20 times so there is probably some race somewhere that causes it to only
 happen sometimes.
 3) dmesg from working case:

 {{{
 72651.735000] s3c2440-sdi s3c2440-sdi: powered down.
 72660.080000] s3c2440-sdi s3c2440-sdi: host detect has no irq available
 72660.080000] mapped channel 0 to 0
 72660.085000] s3c2440-sdi s3c2440-sdi: powered down.
 72660.090000] s3c2440-sdi s3c2440-sdi: initialisation done.
 72660.100000] s3c2440-sdi s3c2440-sdi: running at 0kHz (requested: 0kHz).
 72660.110000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72660.110000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72660.125000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72660.130000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72660.150000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72660.160000] mmc1: queuing CIS tuple 0x01 length 3
 72660.175000] mmc1: queuing CIS tuple 0x1a length 5
 72660.180000] mmc1: queuing CIS tuple 0x1b length 8
 72660.185000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested:
 25000kHz).
 72660.190000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested:
 25000kHz).
 72660.200000] mmc1: queuing CIS tuple 0x80 length 1
 72660.200000] mmc1: queuing CIS tuple 0x81 length 1
 72660.205000] mmc1: queuing CIS tuple 0x82 length 1
 72660.210000] mmc1: new SDIO card at address 0001
 72661.275000] BMI Get Target Info: Exit (ver: 0x20000059 type: 0x1)
 72661.330000] AR6000 Reg Code = 0x40000060
 72661.355000] udev: renamed network interface eth0 to wlan
 }}}

 4) dmesg from non-working case:

 {{{
 72138.450000] s3c2440-sdi s3c2440-sdi: host detect has no irq available
 72138.450000] mapped channel 0 to 0
 72138.450000] s3c2440-sdi s3c2440-sdi: powered down.
 72138.455000] s3c2440-sdi s3c2440-sdi: initialisation done.
 72138.465000] s3c2440-sdi s3c2440-sdi: running at 0kHz (requested: 0kHz).
 72138.475000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72138.480000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72138.485000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72138.510000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72138.530000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested:
 195kHz).
 72138.540000] mmc1: queuing CIS tuple 0x01 length 3
 72138.555000] mmc1: queuing CIS tuple 0x1a length 5
 72138.560000] mmc1: queuing CIS tuple 0x1b length 8
 72138.560000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested:
 25000kHz).
 72138.565000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested:
 25000kHz).
 72138.570000] mmc1: queuing CIS tuple 0x80 length 1
 72138.575000] mmc1: queuing CIS tuple 0x81 length 1
 72138.580000] mmc1: queuing CIS tuple 0x82 length 1
 72138.585000] mmc1: new SDIO card at address 0001
 72138.600000] sdio_ar6000 mmc1:0001:1: deviceInsertedHandler: -1
 72138.600000] sdio_ar6000 mmc1:0001:1: kthread_stop (ar6000_io): -4
 72138.605000] ar6000_activate: Failed to activate -4
 72138.610000] sdio_ar6000: probe of mmc1:0001:1 failed with error -4
 }}}

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2327>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac


More information about the buglog mailing list