samus: Can't wake from docked-mode S3 via input devices connected via Type-C dock |
||
Issue descriptionIn http://g/chromeos-discuss/bdO-otq_sGw and further off-list discussion, it was reported that a samus device (not sure of the version) can't be woken from idle-suspend via USB input devices that are connected via a Type-C dock: "I have the Chromebook plugged into a USB C hub with power and USB A (leading to keyboard and mouse) and a USB C-to-Displayport adapter plugged into the monitor." dmargolis@, can you provide some more details? - Chrome OS version from chrome://version - information about make/model of all connected USB devices (especially dock) - confirmation that the devices were already connected when the device suspended If you can file a feedback report using Alt+Shift+i upon waking the device after seeing this issue, that might help too. Thanks!
,
Apr 26 2018
I just reproed and filed a feedback report. Not sure how to find it for you, though, but I referenced this bug in it.
,
Apr 26 2018
Thanks for your feedback ... its here: https://listnr.corp.google.com/report/85363719246 Do you happen to know make/model of the USB hub? I do see this failure: [ 9778.274586] PM: Device 1-3.1.3 failed to resume async: error -32 which might indicate there's some difficulties preventing keyboard (1-3.1.3 ... see below) or perhaps hub in general from providing wake caps. [ 9778.945282] usb 1-3.1.3: New USB device found, idVendor=04d9, idProduct=a0b9 [ 9778.945292] usb 1-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=17 [ 9778.945299] usb 1-3.1.3: Product: ES-87 [ 9778.945304] usb 1-3.1.3: Manufacturer: Keyed Up Labs I'm guessing the mouse, Bus 001 Device 033: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500] Also fails to wake properly? I'll try as well with a usb-c hub I know works to rule out any general regression on samus.
,
Apr 26 2018
Sorry I missed the ref to mystuff URL w/ Apple USB-C A/V adapter in #1 ... ignore request in #3. Just tried on samus (M65) with same dongle connected to keyboard (logitech) directly via USB-A as well as keyboard connected to monitor's (Dell U2410) USB hub and both successfully woke device in docked mode. Need to see if I can track down the monitor next locally. Does your samus wake if the keyboard (or mouse) are directly connected to the Apple dongle?
,
Apr 27 2018
Yes, the mouse also fails to work. I haven't tried connecting directly to the dongle. It doesn't have enough ports (only one USB-A) so I can't really work in that configuration to test this. :-/ Would it be sufficient to plug into the dongle once the problem reproduces? Or do you want me to let the machine fall asleep while the peripherals are plugged in?
,
Apr 27 2018
(Sorry, I mean, do you want me to let it fall alseep when they're plugged into the hub directly, or would it be ok to switch the keyboard to the USB-C hub once the device is asleep?)
,
Apr 27 2018
Sounds like its likely to be an issue w/ hub inside the monitor but would be good to confirm its not apple dongle which also has at least 3 firmware versions I'm aware of. If you could allow it to sleep with say just the keyboard connected to the apple dongle and confirm that it wakes we can focus on hub w/in the monitor.
,
May 9 2018
Unfortunately I also just upgraded to a Pixelbook. Still have the Samus on my desk, so let me see if I repro with the Pixelbook; if not, I will go back to the Samus for regular usage. :)
,
May 11 2018
OK, so Pixelbook + http://www.cablematters.com/pc-899-114-usb-c-to-4k-60hz-displayport-multiport-adapter.aspx (no monitor USB hub involved) still repros this. Interestingly, it seems to me (based on the caps-lock light) that the machine in fact stays on (with the screen off) *until* I hit the keyboard! So what I observe: 1. I come back from getting some cookies. Screen is in power saving mode. 2. I tap caps-lock key. Key lights up. 3. I take some other keys. 4. I tap caps-lock key a few seconds later. Key does not light up. 5. Opening the lid of the Chromebook causes it to wake up; screen powers on, etc.
,
May 11 2018
#9: Mind filing another feedback report immediately after repro-ing this on the Pixelbook? Thanks!
,
May 11 2018
Sure, will do when I am back in the office Monday. :)
,
May 15 2018
Please comment on the bug after the report is filed. Thanks!
,
Sep 12
Sorry for the slow reply. I filed feedback just now, referencing this issue. I"m not sure how to track down the feedback report--I guess you can do that?
,
Sep 12
dmargolis: If you filed the FR from your google.com account, check your Sent box in Gmail. You should see your feedback report there. Copy and paste the listnr link to this bug.
,
Sep 12
Oh, hah. Thanks. https://listnr.corp.google.com/report/85655983175
,
Sep 12
dmargolis: Is this the hub you have? https://www.amazon.com/Cable-Matters-Multiport-Adapter-Ethernet/dp/B01M0K0DL2
,
Sep 12
Yep.
,
Sep 12
By the way, what keyboard are you using? Also, have you tried any different keyboard?
,
Sep 12
It's a kul-es87. I've not tried another. Should mouse work in the case it's the keyboard? I can try that (though I don't think it does). Note that the keyboard may also be daisy chained into the monitor and not directly into the hub. (I'm not at my desk but can check later, if this matters.)
,
Sep 13
Please let me know which mouse you're using too. It would be useful if you could draw a picture in keep or something that shows how each device is attached to the USB tree.
,
Sep 13
Sure. Though I was wrong; the peripherals are plugged directly into the
hub.
So it looks like this:
+-----------------+
+---+
|
| |
|
| |
|
+------------------+ | |
Pixelbook |
| | | |
|
| Monitor | | |
|
| (B326HK) | |
+-----------------+
| ++ |
| || +-------+----+
| || |Hub (Cable |
| +-----------------------+ Matters) |
+------------------+ +------------+
+--------------------------------+ ++
| |
| |
| |
| |
| |
| |
+-+--+ +-----------------------+---------+
Mouse (Logitech | | | |
M-U0007) | | | |
+----+ | Keyboard (KUL ES-87) |
+---------------------------------+
|
||
►
Sign in to add a comment |
||
Comment 1 by dmargolis@google.com
, Apr 26 2018