From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 209173] New: laptop boot takes 1.20 minutes - i cant seem to find anything wrong other than bluetooth in Dmesg
Date: Sun, 06 Sep 2020 17:52:15 +0000 [thread overview]
Message-ID: <bug-209173-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=209173
Bug ID: 209173
Summary: laptop boot takes 1.20 minutes - i cant seem to find
anything wrong other than bluetooth in Dmesg
Product: Drivers
Version: 2.5
Kernel Version: 5.7.0
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: thiviyan@gmail.com
Regression: No
Created attachment 292379
--> https://bugzilla.kernel.org/attachment.cgi?id=292379&action=edit
dmesg -T output
expected behavior : system supposed to boot within less than 20 seconds
current behavior : it take around 1.30 Minutes to reach user space.
its loads normally when i try live usb disk without the RTL8822be drivers
loaded for wifi and bluetooth but when i try the os which is installed in HDD
with all the drivers it takes a long time to boot. i am not sure if its the
problem caused by the wifi/bluetooth drivers(i have no complains on their
connectivity)
tried solutions : checked UUID of swap and it maches. tried couple different
cmdline options in grub none fixed the issue.
i have attached the dmesg -T output and systemd-analyze critical-chain outputs.
OS: Kali GNU/Linux Rolling x
Host: 81FV Lenovo Legion Y53
Kernel: 5.7.0-kali3-amd64
CPU: Intel i5-8300H (8) @ 4.
GPU: NVIDIA GeForce GTX 1050
GPU: Intel UHD Graphics 630
Memory: 3807MiB / 23995MiB
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-09-06 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-209173-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).