“Bluetooth: RFCOMM TTY layer initialized” taking long time during boot





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















Output of dmesg:



[   18.062831] wlp1s0: associated
[ 18.516902] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 18.844430] vboxdrv: loading out-of-tree module taints kernel.
[ 18.862837] vboxdrv: Found 8 processor cores
[ 18.880547] vboxdrv: TSC mode is Invariant, tentative frequency 1800001178 Hz
[ 18.880549] vboxdrv: Successfully loaded version 5.2.18_Ubuntu (interface 0x00290001)
[ 18.903066] VBoxNetFlt: Successfully started.
[ 18.925115] VBoxNetAdp: Successfully started.
[ 18.959469] VBoxPciLinuxInit
[ 18.975413] vboxpci: IOMMU not found (not registered)
[ 72.120167] Bluetooth: RFCOMM TTY layer initialized
[ 72.120177] Bluetooth: RFCOMM socket layer initialized
[ 72.120183] Bluetooth: RFCOMM ver 1.11
[ 74.132007] rfkill: input handler disabled



"Bluetooth: RFCOMM TTY layer initialized" Taking alot of time.



Output of dmesg after removing virtualbox:



[   13.302018] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 13.395355] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
[ 13.395360] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 13.395363] pcieport 0000:00:1d.0: device [8086:9d18] error status/mask=00000001/00002000
[ 13.395365] pcieport 0000:00:1d.0: [ 0] Receiver Error (First)
[ 13.411632] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 13.852753] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 17.499926] wlp1s0: authenticate with e4:6f:13:4f:4f:c0
[ 17.500332] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
[ 17.500340] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 17.500344] pcieport 0000:00:1d.0: device [8086:9d18] error status/mask=00000001/00002000
[ 17.500347] pcieport 0000:00:1d.0: [ 0] Receiver Error (First)
[ 17.506088] wlp1s0: send auth to e4:6f:13:4f:4f:c0 (try 1/3)
[ 17.508958] wlp1s0: authenticated
[ 17.512158] wlp1s0: associate with e4:6f:13:4f:4f:c0 (try 1/3)
[ 17.516486] wlp1s0: RX AssocResp from e4:6f:13:4f:4f:c0 (capab=0x411 status=0 aid=1)
[ 17.518462] wlp1s0: associated
[ 17.612677] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 41.905950] Bluetooth: RFCOMM TTY layer initialized
[ 41.905961] Bluetooth: RFCOMM socket layer initialized
[ 41.905967] Bluetooth: RFCOMM ver 1.11
[ 43.554072] rfkill: input handler disabled



Systemd-analyze:



Startup finished in 3.461s (kernel) + 22.792s (userspace) = 26.253s
graphical.target reached after 22.754s in userspace


Systemd-analyze blame:



          13.937s plymouth-quit-wait.service
7.473s postgresql@10-main.service
6.502s NetworkManager-wait-online.service
5.480s fwupd.service
5.170s bolt.service
4.933s mysql.service
3.663s networkd-dispatcher.service
3.618s ModemManager.service
3.532s systemd-journal-flush.service
3.092s udisks2.service
2.637s dev-sda2.device
2.361s motd-news.service
2.348s accounts-daemon.service
2.310s apparmor.service
2.123s plymouth-read-write.service
1.849s gpu-manager.service
1.823s networking.service
1.774s avahi-daemon.service
1.732s bluetooth.service
1.727s grub-common.service
1.710s rsyslog.service
1.682s apport.service
1.643s wpa_supplicant.service


Acer Swift 3 Laptop

The wifi and bluetooth adapter is Intel Wireless 7265. Driver iwlwifi.
256GB Micron 1100 SATA3 M.2 SSD.










share|improve this question









New contributor




Arsh Jethi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Try removing vbox

    – Jeremy31
    Apr 6 at 20:06











  • Didn't work. (Added Dmesg output after removing Virtualbox in post).

    – Arsh Jethi
    2 days ago


















1















Output of dmesg:



[   18.062831] wlp1s0: associated
[ 18.516902] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 18.844430] vboxdrv: loading out-of-tree module taints kernel.
[ 18.862837] vboxdrv: Found 8 processor cores
[ 18.880547] vboxdrv: TSC mode is Invariant, tentative frequency 1800001178 Hz
[ 18.880549] vboxdrv: Successfully loaded version 5.2.18_Ubuntu (interface 0x00290001)
[ 18.903066] VBoxNetFlt: Successfully started.
[ 18.925115] VBoxNetAdp: Successfully started.
[ 18.959469] VBoxPciLinuxInit
[ 18.975413] vboxpci: IOMMU not found (not registered)
[ 72.120167] Bluetooth: RFCOMM TTY layer initialized
[ 72.120177] Bluetooth: RFCOMM socket layer initialized
[ 72.120183] Bluetooth: RFCOMM ver 1.11
[ 74.132007] rfkill: input handler disabled



"Bluetooth: RFCOMM TTY layer initialized" Taking alot of time.



Output of dmesg after removing virtualbox:



[   13.302018] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 13.395355] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
[ 13.395360] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 13.395363] pcieport 0000:00:1d.0: device [8086:9d18] error status/mask=00000001/00002000
[ 13.395365] pcieport 0000:00:1d.0: [ 0] Receiver Error (First)
[ 13.411632] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 13.852753] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 17.499926] wlp1s0: authenticate with e4:6f:13:4f:4f:c0
[ 17.500332] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
[ 17.500340] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 17.500344] pcieport 0000:00:1d.0: device [8086:9d18] error status/mask=00000001/00002000
[ 17.500347] pcieport 0000:00:1d.0: [ 0] Receiver Error (First)
[ 17.506088] wlp1s0: send auth to e4:6f:13:4f:4f:c0 (try 1/3)
[ 17.508958] wlp1s0: authenticated
[ 17.512158] wlp1s0: associate with e4:6f:13:4f:4f:c0 (try 1/3)
[ 17.516486] wlp1s0: RX AssocResp from e4:6f:13:4f:4f:c0 (capab=0x411 status=0 aid=1)
[ 17.518462] wlp1s0: associated
[ 17.612677] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 41.905950] Bluetooth: RFCOMM TTY layer initialized
[ 41.905961] Bluetooth: RFCOMM socket layer initialized
[ 41.905967] Bluetooth: RFCOMM ver 1.11
[ 43.554072] rfkill: input handler disabled



Systemd-analyze:



Startup finished in 3.461s (kernel) + 22.792s (userspace) = 26.253s
graphical.target reached after 22.754s in userspace


Systemd-analyze blame:



          13.937s plymouth-quit-wait.service
7.473s postgresql@10-main.service
6.502s NetworkManager-wait-online.service
5.480s fwupd.service
5.170s bolt.service
4.933s mysql.service
3.663s networkd-dispatcher.service
3.618s ModemManager.service
3.532s systemd-journal-flush.service
3.092s udisks2.service
2.637s dev-sda2.device
2.361s motd-news.service
2.348s accounts-daemon.service
2.310s apparmor.service
2.123s plymouth-read-write.service
1.849s gpu-manager.service
1.823s networking.service
1.774s avahi-daemon.service
1.732s bluetooth.service
1.727s grub-common.service
1.710s rsyslog.service
1.682s apport.service
1.643s wpa_supplicant.service


Acer Swift 3 Laptop

The wifi and bluetooth adapter is Intel Wireless 7265. Driver iwlwifi.
256GB Micron 1100 SATA3 M.2 SSD.










share|improve this question









New contributor




Arsh Jethi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Try removing vbox

    – Jeremy31
    Apr 6 at 20:06











  • Didn't work. (Added Dmesg output after removing Virtualbox in post).

    – Arsh Jethi
    2 days ago














1












1








1








Output of dmesg:



[   18.062831] wlp1s0: associated
[ 18.516902] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 18.844430] vboxdrv: loading out-of-tree module taints kernel.
[ 18.862837] vboxdrv: Found 8 processor cores
[ 18.880547] vboxdrv: TSC mode is Invariant, tentative frequency 1800001178 Hz
[ 18.880549] vboxdrv: Successfully loaded version 5.2.18_Ubuntu (interface 0x00290001)
[ 18.903066] VBoxNetFlt: Successfully started.
[ 18.925115] VBoxNetAdp: Successfully started.
[ 18.959469] VBoxPciLinuxInit
[ 18.975413] vboxpci: IOMMU not found (not registered)
[ 72.120167] Bluetooth: RFCOMM TTY layer initialized
[ 72.120177] Bluetooth: RFCOMM socket layer initialized
[ 72.120183] Bluetooth: RFCOMM ver 1.11
[ 74.132007] rfkill: input handler disabled



"Bluetooth: RFCOMM TTY layer initialized" Taking alot of time.



Output of dmesg after removing virtualbox:



[   13.302018] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 13.395355] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
[ 13.395360] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 13.395363] pcieport 0000:00:1d.0: device [8086:9d18] error status/mask=00000001/00002000
[ 13.395365] pcieport 0000:00:1d.0: [ 0] Receiver Error (First)
[ 13.411632] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 13.852753] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 17.499926] wlp1s0: authenticate with e4:6f:13:4f:4f:c0
[ 17.500332] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
[ 17.500340] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 17.500344] pcieport 0000:00:1d.0: device [8086:9d18] error status/mask=00000001/00002000
[ 17.500347] pcieport 0000:00:1d.0: [ 0] Receiver Error (First)
[ 17.506088] wlp1s0: send auth to e4:6f:13:4f:4f:c0 (try 1/3)
[ 17.508958] wlp1s0: authenticated
[ 17.512158] wlp1s0: associate with e4:6f:13:4f:4f:c0 (try 1/3)
[ 17.516486] wlp1s0: RX AssocResp from e4:6f:13:4f:4f:c0 (capab=0x411 status=0 aid=1)
[ 17.518462] wlp1s0: associated
[ 17.612677] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 41.905950] Bluetooth: RFCOMM TTY layer initialized
[ 41.905961] Bluetooth: RFCOMM socket layer initialized
[ 41.905967] Bluetooth: RFCOMM ver 1.11
[ 43.554072] rfkill: input handler disabled



Systemd-analyze:



Startup finished in 3.461s (kernel) + 22.792s (userspace) = 26.253s
graphical.target reached after 22.754s in userspace


Systemd-analyze blame:



          13.937s plymouth-quit-wait.service
7.473s postgresql@10-main.service
6.502s NetworkManager-wait-online.service
5.480s fwupd.service
5.170s bolt.service
4.933s mysql.service
3.663s networkd-dispatcher.service
3.618s ModemManager.service
3.532s systemd-journal-flush.service
3.092s udisks2.service
2.637s dev-sda2.device
2.361s motd-news.service
2.348s accounts-daemon.service
2.310s apparmor.service
2.123s plymouth-read-write.service
1.849s gpu-manager.service
1.823s networking.service
1.774s avahi-daemon.service
1.732s bluetooth.service
1.727s grub-common.service
1.710s rsyslog.service
1.682s apport.service
1.643s wpa_supplicant.service


Acer Swift 3 Laptop

The wifi and bluetooth adapter is Intel Wireless 7265. Driver iwlwifi.
256GB Micron 1100 SATA3 M.2 SSD.










share|improve this question









New contributor




Arsh Jethi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












Output of dmesg:



[   18.062831] wlp1s0: associated
[ 18.516902] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 18.844430] vboxdrv: loading out-of-tree module taints kernel.
[ 18.862837] vboxdrv: Found 8 processor cores
[ 18.880547] vboxdrv: TSC mode is Invariant, tentative frequency 1800001178 Hz
[ 18.880549] vboxdrv: Successfully loaded version 5.2.18_Ubuntu (interface 0x00290001)
[ 18.903066] VBoxNetFlt: Successfully started.
[ 18.925115] VBoxNetAdp: Successfully started.
[ 18.959469] VBoxPciLinuxInit
[ 18.975413] vboxpci: IOMMU not found (not registered)
[ 72.120167] Bluetooth: RFCOMM TTY layer initialized
[ 72.120177] Bluetooth: RFCOMM socket layer initialized
[ 72.120183] Bluetooth: RFCOMM ver 1.11
[ 74.132007] rfkill: input handler disabled



"Bluetooth: RFCOMM TTY layer initialized" Taking alot of time.



Output of dmesg after removing virtualbox:



[   13.302018] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 13.395355] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
[ 13.395360] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 13.395363] pcieport 0000:00:1d.0: device [8086:9d18] error status/mask=00000001/00002000
[ 13.395365] pcieport 0000:00:1d.0: [ 0] Receiver Error (First)
[ 13.411632] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 13.852753] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 17.499926] wlp1s0: authenticate with e4:6f:13:4f:4f:c0
[ 17.500332] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:00:1d.0
[ 17.500340] pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 17.500344] pcieport 0000:00:1d.0: device [8086:9d18] error status/mask=00000001/00002000
[ 17.500347] pcieport 0000:00:1d.0: [ 0] Receiver Error (First)
[ 17.506088] wlp1s0: send auth to e4:6f:13:4f:4f:c0 (try 1/3)
[ 17.508958] wlp1s0: authenticated
[ 17.512158] wlp1s0: associate with e4:6f:13:4f:4f:c0 (try 1/3)
[ 17.516486] wlp1s0: RX AssocResp from e4:6f:13:4f:4f:c0 (capab=0x411 status=0 aid=1)
[ 17.518462] wlp1s0: associated
[ 17.612677] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 41.905950] Bluetooth: RFCOMM TTY layer initialized
[ 41.905961] Bluetooth: RFCOMM socket layer initialized
[ 41.905967] Bluetooth: RFCOMM ver 1.11
[ 43.554072] rfkill: input handler disabled



Systemd-analyze:



Startup finished in 3.461s (kernel) + 22.792s (userspace) = 26.253s
graphical.target reached after 22.754s in userspace


Systemd-analyze blame:



          13.937s plymouth-quit-wait.service
7.473s postgresql@10-main.service
6.502s NetworkManager-wait-online.service
5.480s fwupd.service
5.170s bolt.service
4.933s mysql.service
3.663s networkd-dispatcher.service
3.618s ModemManager.service
3.532s systemd-journal-flush.service
3.092s udisks2.service
2.637s dev-sda2.device
2.361s motd-news.service
2.348s accounts-daemon.service
2.310s apparmor.service
2.123s plymouth-read-write.service
1.849s gpu-manager.service
1.823s networking.service
1.774s avahi-daemon.service
1.732s bluetooth.service
1.727s grub-common.service
1.710s rsyslog.service
1.682s apport.service
1.643s wpa_supplicant.service


Acer Swift 3 Laptop

The wifi and bluetooth adapter is Intel Wireless 7265. Driver iwlwifi.
256GB Micron 1100 SATA3 M.2 SSD.







networking drivers bluetooth 18.10 boot-time






share|improve this question









New contributor




Arsh Jethi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Arsh Jethi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 days ago







Arsh Jethi













New contributor




Arsh Jethi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Apr 6 at 17:18









Arsh JethiArsh Jethi

63




63




New contributor




Arsh Jethi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Arsh Jethi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Arsh Jethi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Try removing vbox

    – Jeremy31
    Apr 6 at 20:06











  • Didn't work. (Added Dmesg output after removing Virtualbox in post).

    – Arsh Jethi
    2 days ago



















  • Try removing vbox

    – Jeremy31
    Apr 6 at 20:06











  • Didn't work. (Added Dmesg output after removing Virtualbox in post).

    – Arsh Jethi
    2 days ago

















Try removing vbox

– Jeremy31
Apr 6 at 20:06





Try removing vbox

– Jeremy31
Apr 6 at 20:06













Didn't work. (Added Dmesg output after removing Virtualbox in post).

– Arsh Jethi
2 days ago





Didn't work. (Added Dmesg output after removing Virtualbox in post).

– Arsh Jethi
2 days ago










0






active

oldest

votes












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






Arsh Jethi is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131721%2fbluetooth-rfcomm-tty-layer-initialized-taking-long-time-during-boot%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








Arsh Jethi is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Arsh Jethi is a new contributor. Be nice, and check out our Code of Conduct.













Arsh Jethi is a new contributor. Be nice, and check out our Code of Conduct.












Arsh Jethi is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131721%2fbluetooth-rfcomm-tty-layer-initialized-taking-long-time-during-boot%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

GameSpot

日野市

Tu-95轟炸機