#9942 NORM 1.5-sof: hang during use (was: os102 freezes while I am using it)

[Zarro Boogs per Child]

#9942: hang during use
------------------------------------+---------------------------------------
           Reporter:  mikus         |       Owner:                                   
               Type:  defect        |      Status:  new                              
           Priority:  normal        |   Milestone:  1.5-software-later               
          Component:  not assigned  |     Version:  Development build as of this date
         Resolution:                |    Keywords:  os102                            
        Next_action:  reproduce     |    Verified:  0                                
Deployment_affected:                |   Blockedby:                                   
           Blocking:                |  
------------------------------------+---------------------------------------
Changes (by Quozl):

  * keywords:  => os102
  * next_action:  never set => reproduce
  * milestone:  Not Triaged => 1.5-software-later


Comment:

 Thanks for the Sugar logs.

 I had hoped they might contain something useful, but they turned out to be
 technically irrelevant ... apart from confirming that the system was
 operational prior to your hang.

 Please provide more data.

  * did you try Ctrl-Alt-Erase or Ctrl-Alt-F1 keys?
  * was ''Automatic power management'' on?
  * had the system entered idle suspend, or manual suspend?

 The rationale behind the last two questions is that I'd like to exclude
 #9836, which can generate identical symptoms to what you report.

 In the absence of further data my gut feel is that this is a hardware
 problem.  You could test for that by using fs-update to install os64 and
 see if the same symptom occurs.

 ----

 For the record, excluding your logs went like this: sugar-session uses ICE
 and libSM to send a SaveYourself to every new client on the X display as
 the client starts up.  Your logs show this was the last thing recorded
 before the hang.  This pattern is found in other normal logs without a
 hang.  The pattern ends in this ''sms_error_handler'' output:

 {{{
 sms_error_handler (0xaa7a1b8, FALSE, 3, 9, 32771, 0)
 }}}

 Now,

  * the first argument is the address of a connection structure in memory,
  * the second argument of FALSE means the following data does not require
 byte swapping,
  * offending minor opcode 3 is SM_SaveYourself, defined in SM.h, so this
 protocol error is in response to a SmsSaveYourself request,
  * the sequence number is 9,
  * error class 32771 is 0x8003 is IceBadValue, defined in ICE.h,
  * severity 0 is IceCanContinue, defined in ICE.h,

 I've checked the Sugar call to SmsSaveYourself and it appears to be coded
 correctly.  It is in sugar-toolkit.git/src/sugar/gsm-client-xsmp.c .  So
 the cause of this message is most likely an X client that does not
 properly support session management.

 Sugar Labs bugs 1624 (gsm-client goes to infinte loop), 1220, 1194, and
 870 all mentioned sms_error_handler but turned out to be irrelevant.  SL
 1624 might give similar symptoms, but your logs are very short, and you
 said nothing worked ... presumably you tried Ctrl-Alt-Escape or Ctrl-
 Alt-F1, SL 1624 won't prevent those keys from working.

 This message is harmless, and irrelevant.

 References:

 http://xorg.freedesktop.org/releases/X11R7.0/doc/PDF/SMlib.pdf

 git://anongit.freedesktop.org/git/xorg/lib/libSM

-- 
Ticket URL: <http://dev.laptop.org/ticket/9942#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system