very long kernel boot time with some KVM switch

Bug #1704614 reported by Corsaire
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I am using a Aten KVM switch CS1794 hooked on my computer.
It allows the switching for USB, HDMI, and audio.
http://www.aten.com/global/en/products/kvm/desktop-kvm-switches/cs1794/#.WWrnguk9iUk

I run a Ubuntu 17.04 system.

I experience a very long boot time, having done an analysis it appears that the main problem is the kernel boot time and more specifically the time it takes to start its USB subsystem.

when you look at the dsmg output you can clearly see a gap between 4-78s and 79-91s, all in the USB sub-process.
---
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: stranche 3670 F.... pulseaudio
 /dev/snd/controlC1: stranche 3670 F.... pulseaudio
 /dev/snd/controlC0: stranche 3670 F.... pulseaudio
DistroRelease: Ubuntu 17.04
HibernationDevice: RESUME=UUID=28d4f703-2b20-4dd3-ba8b-aa363ad5141d
InstallationDate: Installed on 2017-07-14 (2 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=4fde9883-6d7f-4954-90d6-779f37bbdc93 ro console=tty console=ttyUSB0,57600 noplymouth debug
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-26-generic N/A
 linux-backports-modules-4.10.0-26-generic N/A
 linux-firmware 1.164.1
RfKill:

Tags: zesty
Uname: Linux 4.10.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH Z77
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Corsaire (stranche) wrote :
Revision history for this message
Corsaire (stranche) wrote :
Revision history for this message
Corsaire (stranche) wrote :
affects: gnome-control-center (Ubuntu) → ubuntu
Revision history for this message
Corsaire (stranche) wrote :

I booted with 'debug' in linux line in grub and issued a 'journalctl -ab' command

Paul White (paulw2u)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1704614

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Corsaire (stranche) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected zesty
description: updated
Revision history for this message
Corsaire (stranche) wrote : CRDA.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : IwConfig.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : JournalErrors.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : Lspci.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : Lsusb.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : ProcEnviron.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : ProcModules.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : UdevDb.txt

apport information

Revision history for this message
Corsaire (stranche) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Corsaire (stranche) wrote :

I had this problem since I upgraded in 17.04, that is the main reason for me to make a fresh reinstall.
I don't remember however if I had this in 16.** series too.

I did test the mainline kernel, no change

$ uname -a
Linux gallion 4.12.2-041202-generic #201707150832 SMP Sat Jul 15 12:34:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Corsaire (stranche) wrote :
Revision history for this message
Corsaire (stranche) wrote :
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Corsaire (stranche) wrote :

I don't find where to had the kernel-bug-exists-upstream tag...

tags: added: kernel-bug-exists-upstream
Revision history for this message
Corsaire (stranche) wrote :

>I don't find where to had the kernel-bug-exists-upstream tag...

My bad, just found

Revision history for this message
Corsaire (stranche) wrote :
Revision history for this message
Corsaire (stranche) wrote :

My other PC on Fedora Linux hooked to the same KVM switch doesn't take this much to boot.

I attach the logs from this box for comparison.

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

Fedora kernel you used is 4.11 "Linux version 4.11.10-200.fc25.x86_64"

Can you try 4.11 mainline kernel on Ubuntu?

Revision history for this message
Corsaire (stranche) wrote :

Did the test

$ uname -a
Linux gallion 4.11.10-041110-generic #201707121132 SMP Wed Jul 12 15:34:04 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

no luck, same result

I add the analyze files

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

Ok, didn't notice it's two different machines - please file an upstream bug.

Revision history for this message
Corsaire (stranche) wrote :

filled an upstream bug report

Revision history for this message
Corsaire (stranche) wrote :

I followed the upstream bug report guidelines but I can't see my report being processed on the kernel ML, so I guess something made my report rejected...

Any idea ?

Revision history for this message
Corsaire (stranche) wrote :

Today I upgraded my distro to 17.10, problem still remain.

Revision history for this message
Corsaire (stranche) wrote :

new tests, maybe not USB related after all, look at #1736947

To post a comment you must log in.