#11363 NORM 1.75-so: XO-1.75 mouse sometimes unusable on boot

[Zarro Boogs per Child]

#11363: XO-1.75 mouse sometimes unusable on boot
--------------------------------+-------------------------------------------
           Reporter:  dsd       |       Owner:  saadia       
               Type:  defect    |      Status:  assigned     
           Priority:  normal    |   Milestone:  1.75-software
          Component:  kernel    |     Version:  not specified
         Resolution:            |    Keywords:               
        Next_action:  diagnose  |    Verified:  0            
Deployment_affected:            |   Blockedby:               
           Blocking:            |  
--------------------------------+-------------------------------------------

Comment(by avatar):

 Replying to [comment:12 pgf]:
 > Replying to [comment:11 avatar]:
 > > By booting a kernel without mmp-camera
 module(CONFIG_VIDEO_MMP_CAMERA), I no longer get "''psmouse.c: Failed to
 enable mouse on olpc_touchpad/serio''" message anymore.
 >
 > thank you for this report.   i have a pending firmware change which will
 definitely help with this issue, but i'm at a loss as to how the camera
 might affect it.  i'll investigate that.
 >

   A wild guess -- could camera initialisation took up too much CPU
 resource thus "blocking" certain PS/2 commands being issued to FSP?

 > fyi, a much faster way to reproduce the problem, without rebooting, is:
 >
 > {{{
 > modprobe -r psmouse; modprobe psmouse
 > }}}
 >
 > this is known to fail completely after the laptop has suspended and
 resumed at least once, so it's a more interesting test before the first
 suspend.

   Thanks for the hint.  FWIW, the log indicates that there're PS/2 command
 writing timeout during module reload:
 {{{
 [ 3892.744180] eth0: no IPv6 routers present
 [ 3909.969624] olpc_keyboard: olpc_kbd_pad_write which=100 val=f5
 [ 3910.164188] olpc_keyboard: olpc_kbd_pad_write which=100 val=f3
 [ 3910.364186] olpc_keyboard: olpc_kbd_pad_write which=100 val=f4
 [ 3910.564195] psmouse serio1: Unable get OPC state.
 [ 3910.564233] olpc_keyboard: olpc_kbd_pad_write which=100 val=f5
 [ 3910.764299] olpc_keyboard: olpc_kbd_pad_write which=100 val=f3
 [ 3910.964748] olpc_keyboard: olpc_kbd_pad_write which=100 val=f4
 [ 3911.964208] olpc_keyboard: olpc_kbd_pad_write timeout, status=103
 [ 3911.964208] olpc_keyboard: olpc_kbd_pad_write which=100 val=f5
 [ 3912.964179] olpc_keyboard: olpc_kbd_pad_write timeout, status=103
 [ 3912.964208] olpc_keyboard: olpc_kbd_pad_write which=100 val=f3
 [ 3913.964190] olpc_keyboard: olpc_kbd_pad_write timeout, status=103
 [ 3913.964190] olpc_keyboard: olpc_kbd_pad_write which=100 val=f4
 [ 3914.964166] olpc_keyboard: olpc_kbd_pad_write timeout, status=103
 [ 3915.034718] olpc_keyboard: olpc_kbd_pad_open
 [ 3915.034718] olpc_keyboard: olpc_kbd_pad_write which=100 val=f2
 [ 3916.034169] olpc_keyboard: olpc_kbd_pad_write timeout, status=103
 }}}

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