Opened 7 years ago

Last modified 6 years ago

#7298 reopened defect

Attaching external mouse makes XO irresponsive

Reported by: joe Owned by: dsaxena
Priority: high Milestone: 8.2.0 (was Update.2)
Component: power manager (OHM) Version: Update.1
Keywords: candidate-708:- joyride-2079:+ Cc: mstone, dsaxena, Blaketh
Blocked By: Blocking:
Deployments affected: Action Needed: never set
Verified: no

Description

Build Joyride 2026, firmware Q2D16, machines CSN74801BDF and CSN74804BE8.

Attaching an external USB mouse (either wired or wireless) makes XO absolutely frozen after ~ 5+ minutes. Power to the mouse goes off. The only way to shut the machine down is to hold a power button for at least 5 sec. Reproducible bug, checked several times with 2 XOs.

Change History (12)

comment:1 follow-up: Changed 7 years ago by cjb

Does tapping the power button once help? Power to USB isn't supposed to be maintained during suspend.

If it doesn't, I'll need the output of "dmesg". If you don't want to hook up a serial console yourself, I can try it on one of my machines.

comment:2 Changed 7 years ago by mstone

  • Cc mstone dsaxena added

comment:3 in reply to: ↑ 1 Changed 7 years ago by joe

Replying to cjb:

Does tapping the power button once help? Power to USB isn't supposed to be maintained during suspend.

If it doesn't, I'll need the output of "dmesg". If you don't want to hook up a serial console yourself, I can try it on one of my machines.


It doesn't.

comment:4 Changed 7 years ago by cjb

Okay, back with me to investigate.

I'd be interested to know whether this happens on 703 too.

comment:5 Changed 7 years ago by mstone

  • Cc Blaketh added

We made some serious changes to the touchpad driver and the way that HAL and evdev interpret the output of the driver in the 703->708 transition. It's entirely possible that we introduced a regression in USB mice.

comment:6 Changed 6 years ago by dsaxena

It looks like a kernel issue, upon coming out of suspend. This is 2.6.22 on a Joyride build.
Will retest with 703 and 708.

[    1.414758] Restarting tasks ... done.
[    1.492544] hub_port_wait_reset: portstatus=100 portchange=1
[    1.498229] hub_port_wait_reset: device went away!
[    1.504571] BUG: unable to handle kernel paging request at virtual address 00
100100
[    1.512399]  printing eip:
[    1.515121] c055aa09
[    1.517321] *pde = 00000000
[    1.520240] Oops: 0000 [#1]
[    1.523048] PREEMPT
[    1.525277] Modules linked in: i2c_dev usb8xxx libertas ieee80211 ieee80211_c
rypt cs5535_gpio mousedev joydev
[    1.535434] CPU:    0
[    1.535441] EIP:    0060:[<c055aa09>]    Not tainted VLI
[    1.535452] EFLAGS: 00010206   (2.6.22 #1)
[    1.547159] EIP is at evdev_disconnect+0x7d/0xba
[    1.551797] eax: 00000000   ebx: 000ffcf0   ecx: cedbf000   edx: 00000000
[    1.558601] esi: cd9fd320   edi: cd9fd37c   ebp: cb95c600   esp: cedbfe80
[    1.565403] ds: 007b   es: 007b   fs: 0000  gs: 0000  ss: 0068
[    1.571253] Process khubd (pid: 51, ti=cedbf000 task=cedba030 task.ti=cedbf00
0)
[    1.578394] Stack: c87f7800 c87f7800 cd3b6b9c c87f7f08 c0559d10 00000000 c061
2b17 00000246
[    1.586964]        cb51b424 c8adb8c0 c84e9c58 c84e9c58 c056ab01 c19b601c c19b
6000 c84e9000
[    1.595542]        c056db93 cb95c600 cb95c618 c06ce0a0 c3c00458 c053c15d cb95
c618 c06ce0dc
[    1.604113] Call Trace:
[    1.606780]  [<c0559d10>] input_unregister_device+0x6f/0xff
[    1.612409]  [<c0612b17>] _spin_unlock_irq+0x10/0x24
[    1.617427]  [<c056ab01>] hidinput_disconnect+0x22/0x35
[    1.622703]  [<c056db93>] hid_disconnect+0x70/0xc1
[    1.627539]  [<c053c15d>] usb_unbind_interface+0x2d/0x6e
[    1.632902]  [<c0512c12>] __device_release_driver+0x69/0x8e
[    1.638518]  [<c0512fc5>] device_release_driver+0x2c/0x41
[    1.643958]  [<c05125f0>] bus_remove_device+0x5e/0x6c
[    1.649054]  [<c0511072>] device_del+0x1d1/0x243
[    1.653726]  [<c0539f49>] usb_disable_device+0x5c/0xbb
[    1.658908]  [<c0536cf5>] usb_disconnect+0x97/0xf2
[    1.663746]  [<c053732e>] hub_thread+0x326/0xa00
[    1.668412]  [<c040e1dc>] __activate_task+0x1c/0x29
[    1.673342]  [<c0612af1>] _spin_unlock_irqrestore+0x14/0x2a
[    1.678962]  [<c0611449>] __sched_text_start+0x579/0x593
[    1.684314]  [<c040d8e6>] __wake_up_common+0x35/0x53
[    1.689324]  [<c042039d>] autoremove_wake_function+0x0/0x33
[    1.694947]  [<c0537008>] hub_thread+0x0/0xa00
[    1.699436]  [<c04202e5>] kthread+0x36/0x5d
[    1.703663]  [<c04202af>] kthread+0x0/0x5d
[    1.707806]  [<c0403fc3>] kernel_thread_helper+0x7/0x10
[    1.713076]  =======================
[    1.716658] Code: 5e 5c 81 eb 10 04 00 00 eb 21 8d 83 08 04 00 00 b9 06 00 02
 00 ba 1d 00 00 00 e8 a2 f1 ef ff 8b 9b 10 04 00 00 81 eb 10 04 00 00 <8b> 83 10
 04 00 00 8d 74 26 00 8d 83 10 04 00 00 39 f8 75 cb 8d
[    1.737189] EIP: [<c055aa09>] evdev_disconnect+0x7d/0xba SS:ESP 0068:cedbfe80
[  111.512595] PM: Preparing system for mem sleep
[  111.517066] Stopping tasks ... done.
[  111.522721] Suspending console(s)


comment:7 Changed 6 years ago by dsaxena

Just tried 703 and manually suspend/resuming the system via "echo mem > /sys/power/state" and was able to reproduce after a few iterations. The system does wake up and I still have serial console but the UI does not respond to keyb or mouse events at this point. If I suspend again, I now can't wake up b/c input events are not triggering the wakeup. I can still ping the machine but that does not trigger a wakeup either.

comment:8 Changed 6 years ago by dsaxena

  • Owner changed from cjb to dsaxena
  • Priority changed from normal to blocker
  • Status changed from new to assigned

comment:9 Changed 6 years ago by dsaxena

  • Priority changed from blocker to high

comment:10 Changed 6 years ago by dsaxena

  • Action Needed set to never set
  • Resolution set to fixed
  • Status changed from assigned to closed

Just tried to reproduce with joyride 2079 and this is gone.

comment:11 follow-up: Changed 6 years ago by joe

  • Keywords candidate-708:- joyride-2079:+ added
  • Resolution fixed deleted
  • Status changed from closed to reopened

Reopening until the new software is released. See http://lists.laptop.org/pipermail/devel/2008-June/015829.html

comment:12 in reply to: ↑ 11 Changed 6 years ago by joe

Replying to joe:

Reopening until the new software is released. See http://lists.laptop.org/pipermail/devel/2008-June/015829.html

Note: See TracTickets for help on using tickets.