stuck when a device connected

Bug #1854827 reported by Ken SONODA
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Steps to reproduce:
- Login Ubuntu
- Connect to PowerdUSB of ThinkPad USB-C Dock

Expected: Window manager responds mouse moves

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-23-generic 5.3.0-23.25
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ken 1252 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 3 01:09:07 2019
InstallationDate: Installed on 2019-04-27 (219 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20N8CTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=2bbcdfff-f6a0-4ce7-8329-00d9eac16f29 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-23-generic N/A
 linux-backports-modules-5.3.0-23-generic N/A
 linux-firmware 1.183.2
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-11-28 (4 days ago)
dmi.bios.date: 01/22/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0YET27W (1.10 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20N8CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20N8CTO1WW:pvrThinkPadE490:rvnLENOVO:rn20N8CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E490
dmi.product.name: 20N8CTO1WW
dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490
dmi.product.version: ThinkPad E490
dmi.sys.vendor: LENOVO

Revision history for this message
Ken SONODA (ksoda) wrote :
Revision history for this message
Ken SONODA (ksoda) wrote :

It seems that the CurrentDmesg.txt is not sufficient because the problem happened before reboot.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Ken SONODA (ksoda) wrote :

$ dmesg -w > dmesg.log

How can I help with this?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/

Revision history for this message
Ken SONODA (ksoda) wrote :

Thank you for the information. But I gave the device away and I can't try it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.