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 #1841: white screen of death (WSOD) after
      resume (Openmoko Public Trac)
   2. Re: Openmoko Bug #1728: SMS parser bug? (Openmoko Public Trac)
   3. Re: Openmoko Bug #1875: Phone keeps on waking up (suspend
      (wait few seconds or minutes) => wakeup (wait 10s)=> suspend)
      (Openmoko Public Trac)
   4. Re: Openmoko Bug #676: dfu-util upload causes data corruption
      (Openmoko Public Trac)
   5. Re: Openmoko Bug #1983: eth0 doesn't exist / Oops during
      bootup (Openmoko Public Trac)
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
    Reporter:  Rorschach    |        Owner:  openmoko-devel
        Type:  defect       |       Status:  new           
    Priority:  highest      |    Milestone:                
   Component:  unknown      |      Version:  GTA02v5       
    Severity:  critical     |   Resolution:                
    Keywords:  wsod,resume  |    Blockedby:                
Reproducible:  always       |     Blocking:                
----------------------------+-----------------------------------------------

Comment(by andy):

 There's a lot of OOPS and crap in there that shouldn't be.  It's because
 your kernel has sound and bluetooth drivers built-in, but your rootfs has
 out of date modules lying around for these it tries to use as well.

 We should have moved to kernel build-specific module dir in the packaged
 kernel by now to stop this kind of thing from happening, but evidently we
 didn't.

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

--- End Message ---
--- Begin Message ---
#1728: SMS parser bug?
-----------------------+----------------------------------------------------
    Reporter:  odlg    |        Owner:  tick    
        Type:  defect  |       Status:  closed  
    Priority:  high    |    Milestone:          
   Component:  Qtopia  |      Version:  Om2008.8
    Severity:  major   |   Resolution:  fixed   
    Keywords:          |    Blockedby:          
Reproducible:          |     Blocking:          
-----------------------+----------------------------------------------------

Comment(by tick):

 Is the following decode right? (I don't understand it at all :P )
 If is correct, I think you encounter another issue, or your qtopia version
 is not the same as ours.


 ./smsparser
 
0791934329002000840C9193335522291600008090608155708099D6A2B32825264FA098EC95033DA545902C064A3A41D3A236F9741641D264D5997C3A8B206A71E84C0E83A0A750C84C1E83D4A7341964399F4ED0F4E97C8282CD66713A2D8282D369D1A92DBA40C46733

 ByteArray
 
0791934329002000840C9193335522291600008090608155708099D6A2B32825264FA098EC95033DA545902C064A3A41D3A236F9741641D264D5997C3A8B206A71E84C0E83A0A750C84C1E83D4A7341964399F4ED0F4E97C8282CD66713A2D8282D369D1A92DBA40C46733
 Sender:  "+393355229261"
 Text:  "VENERDI' 12/9 ORE 21 IN SEZIONE RIUNIONE TECNICA OBBLIGATORIA,NON
 SONO AMMESSE ASSENZE. DOM"

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

--- End Message ---
--- Begin Message ---
#1875: Phone keeps on waking up (suspend (wait few seconds or minutes) => wakeup
(wait 10s)=> suspend)
---------------------------------------------------+------------------------
    Reporter:  octavsly                            |        Owner:  zecke   
        Type:  enhancement                         |       Status:  new     
    Priority:  normal                              |    Milestone:          
   Component:  Qtopia                              |      Version:  Om2008.8
    Severity:  normal                              |   Resolution:          
    Keywords:  suspend wakeup battery consumption  |    Blockedby:          
Reproducible:  sometimes                           |     Blocking:          
---------------------------------------------------+------------------------

Comment(by octavsly):

 Just had the same behavior. I have increased the log buffer 10 times
 (/etc/syslog.conf) and I was able to get the log of the resume. Here is
 the important part (mind the time stamp jump from 9:26 to 9.30:

 It appears like it tries to suspend then it wakes up


 {{{
 Sep 10 09:26:31 om-gta02 user.notice root: AtChat :  F : "+CMS ERROR: 512"
 Sep 10 09:26:31 om-gta02 user.notice root: AtChat :  T : "AT+CMEE=1"
 Sep 10 09:26:31 om-gta02 user.notice root: AtChat :  F : "+CMS ERROR: 512"
 Sep 10 09:26:31 om-gta02 user.notice root: AtChat :  T : "AT+CFUN=1"
 Sep 10 09:26:31 om-gta02 user.notice root: PowerManagement :  Acking
 suspend
 Sep 10 09:26:31 om-gta02 daemon.notice apmd[1303]: Suspending now
 Sep 10 09:26:31 om-gta02 user.warn kernel: [ 5440.615000] Syncing
 filesystems ... done.
 Sep 10 09:26:31 om-gta02 user.debug kernel: [ 5440.615000] PM: Preparing
 system for mem sleep
 Sep 10 09:30:27 om-gta02 user.warn kernel: [ 5440.905000] Freezing user
 space processes ...
 Sep 10 09:30:27 om-gta02 user.notice root: PowerManagement :  Acked
 suspend 0
 Sep 10 09:30:27 om-gta02 user.notice root: PowerManagement :  APM Event 3
 Sep 10 09:30:27 om-gta02 user.notice root: PowerManagement :  Resume event
 Sep 10 09:30:27 om-gta02 user.notice root: AtChat :  F : "+CMS ERROR: 512"
 Sep 10 09:30:27 om-gta02 user.notice root: AtChat :  T : "^Z"
 Sep 10 09:30:27 om-gta02 user.notice root: AtChat :  W : ""
 Sep 10 09:30:27 om-gta02 user.notice root: AtChat :  W : "%CSQ:  8, 99, 0"
 Sep 10 09:30:27 om-gta02 user.notice root: AtChat :  W : ""
 Sep 10 09:30:27 om-gta02 user.notice root: AtChat :  W : "+CIEV: 1, 1"
 Sep 10 09:30:27 om-gta02 user.notice root: Modem :  void
 CellModemManager::retryRfLevelRequest()
 }}}



 The complete logread is attached.

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

--- End Message ---
--- Begin Message ---
#676: dfu-util upload causes data corruption
-------------------------------------+--------------------------------------
    Reporter:  [EMAIL PROTECTED]  |        Owner:  [EMAIL PROTECTED]
        Type:  defect                |       Status:  reopened                
    Priority:  normal                |    Milestone:                          
   Component:  host utilities        |      Version:                          
    Severity:  normal                |   Resolution:                          
    Keywords:  dfu                   |    Blockedby:                          
Reproducible:                        |     Blocking:                          
-------------------------------------+--------------------------------------

Comment(by madhatter):

 slightly different error, same filesize for me, too:

 [EMAIL PROTECTED] openmoko]# ./dfu-util -a rootfs -R  -U ./tom-
 rootfs-20080910.jffs2
 dfu-util - (C) 2007 by OpenMoko Inc.
 This program is Free Software and has ABSOLUTELY NO WARRANTY

 Opening USB Device 0x0000:0x0000...
 Claiming USB DFU Runtime Interface...
 Determining device status: state = appIDLE, status = 0
 Device really in Runtime Mode, send DFU detach request...
 Resetting USB...
 Opening USB Device...
 Found Runtime: [0x1d50:0x5119] devnum=62, cfg=0, intf=0, alt=6,
 name="rootfs"
 Claiming USB DFU Interface...
 Setting Alternate Setting ...
 Determining device status: state = dfuIDLE, status = 0
 dfuIDLE, continuing
 Transfer Size = 0x1000
 dfu_upload error -108
 [EMAIL PROTECTED] openmoko]#

 -rw-r--r--   1 root     root     258076672 2008-09-10 09:23 tom-
 rootfs-20080910.jffs2


 on phone: U-Boot 1.3.2-moko12

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

--- End Message ---
--- Begin Message ---
#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):

 Thanks for the very quick reply.  I haven't ever seen the WLAN working
 here, but it's very new (in my hands only on Saturday) so I haven't tested
 thoroughly with other images or kernels.  Do you suspect a hardware fault?
 I was surprised that noone else had found the same problem.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1983#comment:2>
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