Openmoko Bug #1983: eth0 doesn't exist / Oops during bootup

Openmoko Public Trac bugs at
Sat Sep 20 15:03:58 CEST 2008

#1983: eth0 doesn't exist / Oops during bootup
    Reporter:  Weiss        |        Owner:  openmoko-devel
        Type:  defect       |       Status:  new           
    Priority:  normal       |    Milestone:                
   Component:  unknown      |      Version:                
    Severity:  normal       |   Resolution:                
    Keywords:  wifi kernel  |    Blockedby:                
Reproducible:  always       |     Blocking:                

Comment(by Weiss):

 Ok - here's the dmesg log with the SDIO bus driver messages enabled.  I
 can see the initial messages working properly, the switch to four-bit I/O,
 some power settings etc.  The errors start, as you suggested, when the
 function is enabled.  There are some response and error codes in the log,
 but I don't know what they mean.

 I also added a debug message just before the
 SDIO_STATUS_FUNC_ENABLE_TIMEOUT exit, and it looks like this happens
 multiple times before the timeout messages appear.

 I tried adding a udelay(10) just after the Cmd52WriteByteCommon in
 SDEnableFunction (after creating the current log), but this didn't appear
 to make any difference.

 So, unless it'd be useful to probe any deeper (which I'd be very willing
 to do - I'm enjoying learning about how to poke around in the kernel),
 I'll initiate the warranty repair/replacement procedure with my reseller
 and this ticket can be closed.  Thanks for all the help and advice.

Ticket URL: <> <>
openmoko trac

More information about the devel mailing list