5.7-rc3 boots on my iMac. It gets past the login screen (unlike rc2),
but it still has the slow boot problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874104
Title:
Very slow boot, wake from s
I made a separate report of the 5.7-rc2 kernel bug to ubuntu-bug linux
as you requested. I will also try to monitor the upstream rc kernels and
run tests on them as you have requested.
I agree that the slow boot bug is likely connected to the AMD video card
in my iMac, and thus to the amdgpu drive
So far these lines look most useful. I am not sure if they are enough
for developer.
kernel: amdgpu: [powerplay]
failed to send message 145 ret is 0
There is usually about a week between upstream rc kernels. Between
stable and next -rc1 there is two weeks. If you can tes
I forgot to send you the proper dmesg for the boot of kernel 5.3rc-1. It
is attached. This kernel was not only slow, but it didn't pick up my
wireless card. This was the only kernel I tried that did this.
** Attachment added: "dmesg for 5.3rc1 boot"
https://bugs.launchpad.net/ubuntu/+source/li
I will report the login bug as a new one. As far as bisection past
identifying the line of progression to identify the last kernel that
works and the first one that doesn't, I looked at the further steps one
would have to take and I don't think that my technical capability is up
to it. I have never
It is possible to login with kernel 5.6. The bootup is slow, but it does
boot and gets past the login screen. I have attached the dmesg from that
boot, and will send the systemd analysis in the next message.
** Attachment added: "dmesg.0 for 5.6 boot"
https://bugs.launchpad.net/ubuntu/+source/
Attached is the SystemD analysis for the 5.6 boot. It looks pretty
similar to that of all the kernels I have tried that are 5.3 or newer.
** Attachment added: "SystemD critical chain and blame outputs: 5.6 kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5360469
This is trace from 5.3-rc1. I am not sure if it's right one.
[ 123.722504] kernel: [ cut here ]
[ 123.722541] kernel: WARNING: CPU: 1 PID: 153 at net/wireless/core.c:868
wiphy_register.cold+0xe4/0x2e5 [cfg80211]
[ 123.722541] kernel: Modules linked in: bnep intel_rapl_m
This bug is introduced between v5.2 and v5.3-rc1. Further bisecting
means compiling kernel. Note that stable versions like 5.2.21 are
generally not bisected.
Could you report login bug as new one? Just like you reported this one. Perhaps
via ubuntu-bug linux. It could be reported with working ker
I did the bisection and found that the bad kernels started at 5.3-rc1.
The last 5.2 kernel, 5.2.21, was good. I have attached the SystemD
analysis here of the boots of both kernels. You can see from it that the
problem in rc1 is related to the gpu-manager service.
I will attach the dmesg log of th
I should add that I tested kernels 5.2.15, 5.2.18 and 5.2.20 as well.
All were OK, so the good-bad line is clearly after 5.2.21.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874104
Title:
Very slo
Here is the dmesg log for the bad boot of 5.3-rc1.
** Attachment added: "Log of 5.3-rc1 kernel boot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359789/+files/dmesg.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Good job. Now v5.2 is known good one. v5.3 is known bad. There are also
other kernels tested including latest upstream one.
It is possible to bisect bug to a single commit
https://wiki.ubuntu.com/Kernel/KernelBisection
Bisecting is good way to find developer to look at your bug.
Before that you
Finally, a second dmesg for the 5.2 kernel boot.(I'm not sure whether
dmesg or dmesg.0 is the right one.
** Attachment added: "dmesg.0 for 5.2 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359527/+files/dmesg.0
--
You received this bug notification
This time with the last fast kernel, 5.2. The bootup was slightly slower
than with 4.15, but I think this might relate to snap module loading. I
should also point out that the difference between kernels 4.15, 5.1 and
5.2 vs the kernels after 5.3 is more than what is indicated by the
SystemD analysi
Next is the first of two dmesg logs for the 5.2 kernel.
** Attachment added: "dmesg for 5.2 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359510/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Next, dmesg.0
** Attachment added: "dmesg.0 for 5.3 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359503/+files/dmesg.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Next, a dmesg for that boot. Not sure which it is so I'll send two.
** Attachment added: "dmesg for 5.3 boot (I hope)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5359502/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I uninstalled Virtualbox and tested kernels 5.1 and 5.2. Both showed
fast boots similar to 4.15. I then tested 5.3 by downloading it from the
ppa/mailine. This is where the slow boot started. I have attached two
dmesg's and a systemd analysis of the critical chain and blame for
kernel 5.3. I can't
Virtualbox taints kernel. Could you reproduce this bug with untainted
kernel? Either to uninstall virtualbox or blacklist vboxdrv kernel
module. I guess live USB doesn't use virtualbox but am not sure.
So far last known good version is 5.0. Known bad ones are 5.3 5.4 and
5.7-rc2.
We like to find
I hope this is what you were looking for. In your message, you noted
that the login bug is likely a separate issue and it could be reported
as new. I thought that this is what I already did. If not, should I
report it again? And with what attachments? Thanks.
** Attachment added: "dmesg.0"
htt
Could you attach dmesg from upstream kernel (5.7-rc2) to this bug?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+addcomment
Previous boot is (Computer) /var/log/dmesg.0 It shows version number.
Login bug is likely separate issue. It could be reported as new.
--
You received this
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874104
Title:
Very slow boot, wake from sleep and shutdown with 5.4 kernel
To manage notifications about thi
Thanks for the quick reply. I installed and tested 5.7-rc2 as per
instructions. The new kernel booted up to the login screen, but as
slowly as 5.4.0-25. (Over 2 minutes to the login screen.) When I logged
in with my password, all that happened was that I was returned to the
login screen. I tried lo
dmesg shows watchdog: BUG: soft lockup - CPU#0 stuck for 22s! and useful
looking trace.
Could you test newest upstream kernel (5.7-rc2) from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds
--
You receive
25 matches
Mail list logo
