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 #1928: Settings don't change the suspend
      time (Openmoko Public Trac)
   2. Re: Openmoko Bug #1597: after a long suspend time,        kernel
      thread events/0 sits eating 30% cpu (Openmoko Public Trac)
   3. Re: Openmoko Bug #1841: white screen of death (WSOD) after
      resume (Openmoko Public Trac)
   4. Re: Openmoko Bug #1841: white screen of death (WSOD) after
      resume (Openmoko Public Trac)
   5. Re: Openmoko Bug #1884: [suspend/resume] if press power
      batton    right after suspend, the device won't wake up
      (Openmoko Public Trac)
   6. Openmoko Bug #1929: Wlan stops working after some time...
      (Openmoko Public Trac)
   7. Openmoko Bug #1930: Another keyboard implementation
      (Openmoko Public Trac)
   8. Re: Openmoko Bug #1815: u-boot fails to detect sandisk 8gb
      microsdhc correctly (Openmoko Public Trac)
   9. Re: Openmoko Bug #1930: Another keyboard implementation
      (Openmoko Public Trac)
--- Begin Message ---
#1928: Settings don't change the suspend time
-------------------------+--------------------------------------------------
    Reporter:  wilk      |        Owner:  marek   
        Type:  defect    |       Status:  new     
    Priority:  normal    |    Milestone:  Om2008.9
   Component:  Settings  |      Version:          
    Severity:  blocker   |   Resolution:          
    Keywords:            |    Blockedby:          
Reproducible:  always    |     Blocking:          
-------------------------+--------------------------------------------------

Comment(by madhatter):

 i'm having the same problem after the same update; /etc/angstrom-version
 says "Angstrom P1-Snapshot-20080830".  my list of packages will also be
 attached.

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

--- End Message ---
--- Begin Message ---
#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
--------------------------------+-------------------------------------------
    Reporter:  raster           |        Owner:  zecke     
        Type:  defect           |       Status:  in_testing
    Priority:  normal           |    Milestone:            
   Component:  System Software  |      Version:            
    Severity:  major            |   Resolution:            
    Keywords:                   |    Blockedby:            
Reproducible:                   |     Blocking:            
--------------------------------+-------------------------------------------

Comment(by koe):

 I've also added my dmesg output, it seems that there where no unexpected
 messages after booting.

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

--- End Message ---
--- 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 some wrong assumptions there, we binned svn for kernel work and
 use git for many months.  There's tons of stuff happened to glamo since
 then in the kernel.

 
http://git.openmoko.org/?p=kernel.git;a=tree;f=drivers/mfd/glamo;h=307b9483be4b681140b0ba96edf094de02cc0339;hb=stable

 Also the triggering of hard reset on Glamo is queer.  I have never ever
 seen it occur randomly during use, only during either suspend or resume
 action.  It's part of a larger syndrome of races and crap in kernel
 suspend / resume that we very slowly clamp down on.

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

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

 Well thanks Andy, I am very glad to stand corrected :-)

 As you state I have also only seen it during suspend/resume. But I see it
 on every 2 or 3 resume.

 Regarding the svn => git conversion I should have checked it better before
 posting. I simply jumped into the reference from
 http://wiki.openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware. Sorry about
 that, and I will keep waiting for it to be "debricked".

 Also everyone I show it to is thrilled by the display.

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

--- End Message ---
--- Begin Message ---
#1884: [suspend/resume] if press power batton right after suspend, the device
won't wake up
--------------------------------+-------------------------------------------
    Reporter:  wendy_hung       |        Owner:  andy    
        Type:  defect           |       Status:  new     
    Priority:  high             |    Milestone:  Om2008.9
   Component:  System Software  |      Version:  Om2008.8
    Severity:  critical         |   Resolution:          
    Keywords:                   |    Blockedby:          
Reproducible:  sometimes        |     Blocking:          
--------------------------------+-------------------------------------------

Comment(by Treviño):

 Well, not completely... As said above I'm using only a bleeding edge
 kernel (well, not so much :P) but the rest of the software stack I'm using
 come from the zecke update of about a week ago.

 I'll try to upgrade...

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

--- End Message ---
--- Begin Message ---
#1929: Wlan stops working after some time...
-----------------------------+----------------------------------------------
 Reporter:  Treviño          |          Owner:  openmoko-kernel
     Type:  defect           |         Status:  new            
 Priority:  normal           |      Milestone:                 
Component:  System Software  |        Version:  Om2008.8       
 Severity:  normal           |       Keywords:                 
Blockedby:                   |   Reproducible:                 
 Blocking:                   |  
-----------------------------+----------------------------------------------
 After some minutes of usage (also just for scanning) my phone wlan module
 stops working and trying to scan I get:
  eth0  Failed to read scan data : Resource temporarily unavailable

 dmesg says:
  AR6000 scan complete: 0
  ar6000_ioctl_giwscan(): data length 0

 Doing a ifdown eth0 && ifpu eth0 dosn't solve.

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

--- End Message ---
--- Begin Message ---
#1930: Another keyboard implementation
-----------------------------+----------------------------------------------
 Reporter:  vsviridov        |          Owner:  openmoko-kernel
     Type:  enhancement      |         Status:  new            
 Priority:  normal           |      Milestone:                 
Component:  System Software  |        Version:                 
 Severity:  normal           |       Keywords:                 
Blockedby:                   |   Reproducible:                 
 Blocking:                   |  
-----------------------------+----------------------------------------------
 Just to bring this project to everyone's attention:

 http://blog.gustavobarbieri.com.br/2007/07/24/iphone-like-virtual-
 keyboard-for-n800/

 It's an E17 iPhone-like keyboard implementation

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

--- End Message ---
--- Begin Message ---
#1815: u-boot fails to detect sandisk 8gb microsdhc correctly
---------------------------------+------------------------------------------
 Reporter:  x                    |        Owner:  openmoko-kernel
     Type:  defect               |       Status:  assigned       
 Priority:  normal               |    Milestone:                 
Component:  System Software      |      Version:  GTA02v5        
 Severity:  normal               |   Resolution:                 
 Keywords:  u-boot sdhc sandisk  |    Blockedby:                 
 Blocking:                       |  
---------------------------------+------------------------------------------

Comment(by x):

 Funny.
 I repartitioned the card, and now booting from it works.
 I find it very hard to believe that it has anything to do with the
 partitioning-tool used (and i didn't use gparted in the first place).
 Obviously it's also not the case that booting works if the kernel happens
 to reside in the first 3mb (i can boot from the 2nd partition now, which
 is behind the first 2gb partition).
 So the mmcinit reporting 3mb as capacity in the end seems to be just a
 cosmetic problem. Though there are still cases left where booting doesn't
 work (plus, i had spurious problems mounting the rootfs by a kernel that
 was loaded from the very same fs, which might be a related problem)

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

--- End Message ---
--- Begin Message ---
#1930: Another keyboard implementation
--------------------------------+-------------------------------------------
    Reporter:  vsviridov        |        Owner:  openmoko-kernel
        Type:  enhancement      |       Status:  closed         
    Priority:  normal           |    Milestone:                 
   Component:  System Software  |      Version:                 
    Severity:  normal           |   Resolution:  invalid        
    Keywords:                   |    Blockedby:                 
Reproducible:                   |     Blocking:                 
--------------------------------+-------------------------------------------
Changes (by raster):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 actually it isn't - it is nothing more than a demo app. it isn't a real
 keyboard at all. it just fakes it. had you fooled nicely - as with a lot
 of people :) it's a cool demo, but it is not a keyboard. it can't produce
 keystrokes for apps etc. the closest is illume's keyboard - and it
 actually produces keystrokes and has dictionary lookup support. (better
 close as invalid as it's misleading to use a bug/enhancement item to point
 to using somethng that actually doesn't work! :))

 but yes - noted - known. this has been around a long time. again - really
 just a demo saying "hey - look. i can make a landscape fullscreen keyboard
 on a 4.3" screen using EFL that i can type on that looks a bit/behaves a
 bit like the iphone. check it out". :)

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