Send buglog mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:

   1. Re: Openmoko Bug #2166: USB keyboard breaks after suspend.
      (Openmoko Public Trac)
   2. Re: Openmoko Bug #2240: removing/reloading g_ether not
      working (Openmoko Public Trac)
   3. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
      to AT     commands" (Openmoko Public Trac)
   4. Re: Openmoko Bug #2276: illume battery module shows -1% as
      the       battery charge state / GTA01 (Openmoko Public Trac)
   5. Re: Openmoko Bug #1435: modem/kernel truncates packages in
      mux mode  after hours of operation (Openmoko Public Trac)
   6. Re: Openmoko Bug #1192: unknown reason cause TI GSM modem
      always    return "+CME ERROR: 512" (Openmoko Public Trac)
--- Begin Message ---
#2166: USB keyboard breaks after suspend.
----------------------+-----------------------------------------------------
 Reporter:  lysgaard  |          Owner:  openmoko-devel             
     Type:  defect    |         Status:  new                        
 Priority:  normal    |      Milestone:                             
Component:  unknown   |        Version:                             
 Severity:  normal    |       Keywords:  usb keyboard suspend resume
 Haspatch:  0         |      Blockedby:                             
Estimated:            |    Patchreview:                             
 Blocking:            |   Reproducible:                             
----------------------+-----------------------------------------------------

Comment(by lindi):

 I am unable reproduce this bug. Here's what I did:

 1) boot andy-tracking b4136a36f31a65d0 with patch for #2240
 2) apm -s
 3) press power button to resume
 4) connected usb keyboard to phone
 5) ifconfig usb0 down
 6) echo host > `find /sys/devices -name usb_mode`
 7) echo 1 > `find /sys/devices -name hostmode`
 8) hit spacebar on keyboard

 and observed
 6) [21474688.120000] hub 1-0:1.0: unable to enumerate USB device on port 2
 7)
 [21474732.560000] usb 1-2: new low speed USB device using s3c-ohci and
 address 4
 [21474732.785000] usb 1-2: New USB device found, idVendor=1241,
 idProduct=1503
 [21474732.790000] usb 1-2: New USB device strings: Mfr=1, Product=2,
 SerialNumber=0
 [21474732.800000] usb 1-2: Product: USB Keyboard
 [21474732.805000] usb 1-2: Manufacturer:
 [21474732.835000] usb 1-2: configuration #1 chosen from 1 choice
 [21474732.880000] input:   USB Keyboard as /class/input/input5
 [21474732.930000] generic-usb 0003:1241:1503.0001: input: USB HID v1.10
 Keyboard [  USB Keyboard] on usb-s3c24xx-2/input0
 [21474732.970000] input:   USB Keyboard as /class/input/input6
 [21474733.015000] generic-usb 0003:1241:1503.0002: input: USB HID v1.10
 Device [  USB Keyboard] on usb-s3c24xx-2/input1
 8) space is printed to console

 Did you do something differently?

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2166#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2240: removing/reloading g_ether not working
----------------------------+-----------------------------------------------
    Reporter:  frankmpunkt  |        Owner:  openmoko-devel
        Type:  defect       |       Status:  closed        
    Priority:  high         |    Milestone:                
   Component:  unknown      |      Version:  unspecified   
    Severity:  normal       |   Resolution:  fixed         
    Keywords:               |     Haspatch:  1             
   Blockedby:               |    Estimated:                
 Patchreview:  positive     |     Blocking:                
Reproducible:  always       |  
----------------------------+-----------------------------------------------
Changes (by arhuaco):

  * reproducible:  => always
  * patchreview:  => positive
  * haspatch:  0 => 1
  * status:  new => closed
  * resolution:  => fixed


Comment:

 Patch sent to andy-tracking. Closing as fixed.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2240#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
 Reporter:  lindi            |          Owner:  openmoko-kernel     
     Type:  defect           |         Status:  new                 
 Priority:  high             |      Milestone:  stable-kernel-2009.1
Component:  System Software  |        Version:  unspecified         
 Severity:  major            |       Keywords:                      
 Haspatch:  0                |      Blockedby:                      
Estimated:                   |    Patchreview:                      
 Blocking:                   |   Reproducible:  sometimes           
-----------------------------+----------------------------------------------

Comment(by arhuaco):

 I tested with your setup. The shr-testing kernel I flashed is recent
 enough.

 - flash http://build.shr-project.org/shr-testing/images/om-gta02/shr-lite-
 image-om-gta02.jffs2
 - flash http://build.shr-project.org/shr-testing/images/om-
 gta02/uImage-2.6.29-oe10+gitr81c61a7d1abb03aecd13f5395aba355e996a1641-r3.4
 -om-gta02.bin
 - boot
 - install http://www.opkg.org/packages/socat_1.3.2.1-r1_armv4t.ipk
 - reboot

 r...@om-gta02 ~ $ fuser /dev/ttySAC0
 1540
 r...@om-gta02 ~ $ kill -9 1540
 r...@om-gta02 ~ $ fuser /dev/ttySAC0

 You might want to move /usr/sbin/gsm0710muxd out of the way while you make
 this test because it can be started while you are testing (it happened to
 me).

  r...@om-gta02 ~ $ cd /sys/class/i2c-adapter/i2c-0/0-0073/neo1973-pm-
 gsm.0/ ; echo 0 > power_on ; sleep 3 ; echo 1 > power_on ; echo 1 > reset
 ; socat - file:/dev/ttySAC0,crtscts,crnl,b115200
  AT-Command Interpreter ready

 (Last command worked in the same way 5 times).

 Relevant kernel messages after you execute the command (once):

  modem wakeup interrupt
  rxerr: port=0 ch=0x00, rxs=0x0000000c


 I tried latest andy-tracking and I think the later rxerr message is OK
 when you start using the port. I enabled dbg in samsung.h (and a few other
 messages, see diffs at the end) and I got this:

 [21474677.270000] modem wakeup interrupt
 [21474834.305000] dbg:s3c24xx_serial_stop_rx: port=c04a06fc
 [   32.630000] modem wakeup interrupt
 [   34.010000] dbg:s3c24xx_serial_startup: port=50000000
 (f5000000,c04a09b4)
 [   34.015000] rxerr: port=0 ch=0x00, rxs=0x0000000c
 [   34.015000] dbg:break!
 [   34.015000] dbg:S3C2410_UERSTAT_FRAME
 [   34.015000] dbg:flag=0
 [   34.020000] dbg:requesting tx irq...
 [   34.025000] dbg:s3c24xx_serial_startup ok
 [   34.030000] dbg:config: 8bits/char
 [   34.035000] dbg:setting ulcon to 00000003, brddiv to 26, udivslot
 00000000
 [   34.035000] dbg:uart: ulcon = 0x00000003, ucon = 0x000003c5, ufcon =
 0x00000011

 Could you repeat the same test? (without the kernel modifications), just
 make sure that /usr/sbin/gsm0710muxd doesn't interrupt your tests.

 Now I guess even when this is working we might get interruptions once in a
 while and that is the problem that was originally reported.

 gsm0710muxd has a watchdog. I assume that if "echo 0 > power_on; sleep 3;
 echo 1 > power_on; echo 1 > reset" is working then the watchdog could do
 exactly the same? (It already resets the modem but there could be a timing
 issue, perhaps a longer delay is needed before the power_on?).

 --- a/drivers/serial/samsung.c
 +++ b/drivers/serial/samsung.c
 @@ -250,10 +250,14 @@ s3c24xx_serial_rx_chars(int irq, void *dev_id)
                                     goto ignore_char;
                         }

 -                       if (uerstat & S3C2410_UERSTAT_FRAME)
 +                       if (uerstat & S3C2410_UERSTAT_FRAME) {
 +                               dbg("S3C2410_UERSTAT_FRAME\n");
                                 port->icount.frame++;
 -                       if (uerstat & S3C2410_UERSTAT_OVERRUN)
 +                       }
 +                       if (uerstat & S3C2410_UERSTAT_OVERRUN) {
 +                               dbg("S3C2410_UERSTAT_OVERRUN\n");
                                 port->icount.overrun++;
 +                       }

                         uerstat &= port->read_status_mask;

 @@ -264,6 +268,7 @@ s3c24xx_serial_rx_chars(int irq, void *dev_id)
                         else if (uerstat & (S3C2410_UERSTAT_FRAME |
                                             S3C2410_UERSTAT_OVERRUN))
                                 flag = TTY_FRAME;
 +                       dbg("flag=%d\n", flag);
                 }


 --- a/drivers/serial/samsung.h
 +++ b/drivers/serial/samsung.h
 @@ -98,10 +98,6 @@ console_initcall(s3c_serial_console_init)
  #define s3c24xx_console_init(drv, inf) extern void no_console(void)
  #endif

 -#ifdef CONFIG_SERIAL_SAMSUNG_DEBUG
 -
 -extern void printascii(const char *);
 -
  static void dbg(const char *fmt, ...)
  {
         va_list va;
 @@ -111,9 +107,5 @@ static void dbg(const char *fmt, ...)
         vsprintf(buff, fmt, va);
         va_end(va);

 -       printascii(buff);
 +       printk(KERN_ERR "dbg:%s", buff);
  }
 -
 -#else
 -#define dbg(x...) do { } while (0)
 -#endif

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:24>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#2276: illume battery module shows -1% as the battery charge state / GTA01
--------------------------------+-------------------------------------------
    Reporter:  arhuaco          |        Owner:  openmoko-kernel
        Type:  defect           |       Status:  closed         
    Priority:  normal           |    Milestone:                 
   Component:  System Software  |      Version:  unspecified    
    Severity:  normal           |   Resolution:  invalid        
    Keywords:                   |     Haspatch:  0              
   Blockedby:                   |    Estimated:                 
 Patchreview:                   |     Blocking:                 
Reproducible:                   |  
--------------------------------+-------------------------------------------
Changes (by arhuaco):

  * status:  new => closed
  * resolution:  => invalid
  * milestone:  stable-kernel-2009.1 =>


Comment:

 I put this error here because it was reported to me and I didn't want to
 forget it.  voltage_now does indeed work. Closing.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2276#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1435: modem/kernel truncates packages in mux mode after hours of operation
------------------------------+---------------------------------------------
    Reporter:  m...@…          |        Owner:  openmoko-kernel
        Type:  defect         |       Status:  closed         
    Priority:  high           |    Milestone:                 
   Component:  hardware       |      Version:  GTA02v4        
    Severity:  normal         |   Resolution:  worksforme     
    Keywords:                 |     Haspatch:  0              
   Blockedby:                 |    Estimated:                 
 Patchreview:                 |     Blocking:                 
Reproducible:                 |  
------------------------------+---------------------------------------------

Comment(by mickey):

 moko11 firmware fixes some flow control issues.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1435#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1192: unknown reason cause TI GSM modem always return "+CME ERROR: 512"
-----------------------------------------+----------------------------------
    Reporter:  sean_chi...@…             |        Owner:  openmoko-devel
        Type:  defect                    |       Status:  closed        
    Priority:  high                      |    Milestone:                
   Component:  hardware                  |      Version:                
    Severity:  critical                  |   Resolution:  fixed         
    Keywords:                            |     Haspatch:  0             
   Blockedby:                            |    Estimated:                
 Patchreview:                            |     Blocking:                
Reproducible:                            |  
-----------------------------------------+----------------------------------
Changes (by mickey):

  * status:  assigned => closed
  * resolution:  => fixed


Comment:

 +COLP=0 and moko11 fixes this for good.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1192#comment:26>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to