"rfkill: input handler disabled" boot time 11 seconds.

Bug #1787824 reported by Erkan ÜNLÜTÜRK
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

My computer is slowly opening, I looked at the output of dmesg and at 11th I get this post.
What i need to do? thanks.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: rfkill 2.31.1-0.4ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 19:44:21 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
 libsmartcols1 2.31.1-0.4ubuntu3.1
InstallationDate: Installed on 2018-08-18 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :
Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :
Revision history for this message
Phillip Susi (psusi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

Changed in util-linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Erkan ÜNLÜTÜRK (erkan-unluturk) wrote :

opening very slow

erkan@unluturk:~$ systemd-analyze
Startup finished in 4.799s (kernel) + 24.242s (userspace) = 29.042s
graphical.target reached after 24.231s in userspace
erkan@unluturk:~$ systemd-analyze blame
         21.198s plymouth-quit-wait.service
          4.086s NetworkManager-wait-online.service
          1.551s dev-sda1.device
          1.088s apparmor.service
           976ms keyboard-setup.service
           896ms plymouth-start.service
           773ms fwupd.service
           626ms snapd.service
           494ms NetworkManager.service
           457ms udisks2.service
           387ms systemd-journal-flush.service
           381ms networkd-dispatcher.service
           345ms ModemManager.service
           331ms accounts-daemon.service
           279ms user@1000.service
           265ms grub-common.service
           253ms systemd-timesyncd.service
           222ms networking.service
           216ms avahi-daemon.service
           208ms speech-dispatcher.service
           185ms systemd-udevd.service
           179ms systemd-sysctl.service
           179ms systemd-udev-trigger.service
lines 1-23

Revision history for this message
Michal Pasniewski (michalp-y) wrote :

same here, this occured after updating from 17 to 18:

:~$ systemd-analyze
Startup finished in 9.891s (firmware) + 2.196s (loader) + 33.839s (kernel) + 22.189s (userspace) = 1min 8.115s
graphical.target reached after 22.184s in userspace
:~$ systemd-analyze blame
         20.698s plymouth-quit-wait.service
          1.304s <email address hidden>
           781ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
           694ms fwupd.service
           485ms snapd.service
           294ms dev-loop0.device
           274ms systemd-logind.service
           272ms dev-loop10.device

Revision history for this message
Charles Wright (wrighrc) wrote :
Download full text (3.3 KiB)

I was watching a video over the network from my x1 system when it went offline.

My system had been up over a day at the time,

Later it came back online and I found this pattern in the logs.

Nov 24 22:08:38 x1 kernel: [ 4491.984774] rfkill: input handler enabled
Nov 24 22:45:15 x1 kernel: [ 6689.350749] r8169 0000:04:00.0 eth0: link down
Nov 24 22:45:18 x1 kernel: [ 6692.350653] r8169 0000:04:00.0 eth0: link up
...
Nov 24 23:28:51 x1 kernel: [ 9305.191129] perf: interrupt took too long (2514 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Nov 24 23:44:36 x1 kernel: [10250.105921] r8169 0000:04:00.0 eth0: link down
Nov 24 23:44:39 x1 kernel: [10253.137255] r8169 0000:04:00.0 eth0: link up
Nov 24 23:44:41 x1 kernel: [10254.820174] r8169 0000:04:00.0 eth0: link down
Nov 24 23:44:53 x1 kernel: [10267.308766] r8169 0000:04:00.0 eth0: link down
Nov 24 23:44:57 x1 kernel: [10270.416767] r8169 0000:04:00.0 eth0: link up
Nov 24 23:45:05 x1 kernel: [10278.366294] r8169 0000:04:00.0 eth0: link down
Nov 24 23:45:08 x1 kernel: [10281.415489] r8169 0000:04:00.0 eth0: link up
Nov 24 23:45:56 x1 kernel: [10329.333933] r8169 0000:04:00.0 eth0: link down
Nov 24 23:46:04 x1 kernel: [10337.815700] r8169 0000:04:00.0 eth0: link down
Nov 24 23:46:11 x1 kernel: [10344.998667] r8169 0000:04:00.0 eth0: link up
Nov 24 23:46:13 x1 kernel: [10346.873959] r8169 0000:04:00.0 eth0: link down
Nov 24 23:46:16 x1 kernel: [10350.226690] r8169 0000:04:00.0 eth0: link up
Nov 24 23:46:18 x1 kernel: [10352.318011] r8169 0000:04:00.0 eth0: link down
Nov 24 23:46:21 x1 kernel: [10355.245040] r8169 0000:04:00.0 eth0: link up

Nov 26 21:14:23 x1 kernel: [129787.573891] rfkill: input handler enabled
Nov 26 21:23:30 x1 kernel: [130334.427437] r8169 0000:03:00.0 eth0: link down
Nov 26 21:23:33 x1 kernel: [130337.443076] r8169 0000:03:00.0 eth0: link up
Nov 26 21:23:57 x1 kernel: [130361.790251] r8169 0000:03:00.0 eth0: link down
Nov 26 21:24:00 x1 kernel: [130364.790674] r8169 0000:03:00.0 eth0: link up
Nov 26 21:41:58 x1 kernel: [131442.193462] r8169 0000:03:00.0 eth0: link down
Nov 26 21:42:01 x1 kernel: [131445.332817] r8169 0000:03:00.0 eth0: link up
Nov 26 21:42:14 x1 kernel: [131458.567170] rfkill: input handler disabled
Nov 26 21:42:16 x1 kernel: [131460.513607] r8169 0000:03:00.0 eth0: link down
Nov 26 21:42:19 x1 kernel: [131464.056605] r8169 0000:03:00.0 eth0: link up
Nov 26 21:42:23 x1 kernel: [131467.593377] r8169 0000:03:00.0 eth0: link down
Nov 26 21:42:30 x1 kernel: [131474.613404] r8169 0000:03:00.0 eth0: link up
Nov 26 21:42:41 x1 kernel: [131485.133432] r8169 0000:03:00.0 eth0: link down
Nov 26 21:42:49 x1 kernel: [131493.199224] rfkill: input handler enabled
Nov 26 21:42:52 x1 kernel: [131496.274226] r8169 0000:03:00.0 eth0: link up
Nov 26 21:42:53 x1 kernel: [131497.548189] r8169 0000:03:00.0 eth0: link down
Nov 26 21:42:56 x1 kernel: [131500.994252] r8169 0000:03:00.0 eth0: link up
Nov 26 21:42:57 x1 kernel: [131501.750754] r8169 0000:03:00.0 eth0: link down
Nov 26 21:43:04 x1 kernel: [131508.486113] r8169 0000:03:00.0 eth0: link up

root@x1:/var/log# uname -a
Linux x1 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.]

Changed in util-linux (Ubuntu):
status: Incomplete → Expired
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.