kernel 5.4.0-58 WORKS without any changes! Good work! THANKS!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895458
Title:
Computer freezes on kernel 5, works on kernel 4
To manage notifications ab
Hi Mauricio,
I don't understand what you are asking me to do...
You are showing me a small difference in the source code, but I am testing
binaries. And between them is the whole complicated build process.
Since I kept the kernels 5.4.0-26 & 5.4.0-28 I re-tested again.
5.4.0-26 boots with and
5.4.0-28 BAD
which leaves the last good
5.4.0-26 GOOD
5.4.0-27 is missing
QED
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895458
Title:
Computer freezes on kernel 5, works on kernel 4
To manage
well
5.4.0-37 bad
The recipe from above does not work for 5.4.0-31*
I will do a binary search without too much "ping - pong" if you tell me the
names of the kernels and how to get them...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
5.4.0-26 kernel boots without dis_ucode_ldr
5.3.0-67 kernel ditto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895458
Title:
Computer freezes on kernel 5, works on kernel 4
To manage notification
1. kernel 5.4.0-48 -"quiet" -"splash" +"dis_ucode_ldr"
cat /proc/cpuinfo > cpuinfo-5.4.0-48.txt
dpkg -s intel-microcode | grep Version > intel-microcode-5.4.0-48.txt
2. kernel 4.15.0-112 -"quiet" -"splash" -"dis_ucode_ldr"
cat /proc/cpuinfo > cpuinfo-4.15.0-112.txt
dpkg -s intel-microcode | grep
Good catch Mauricio!
1. "nomodeset" did not help.
2. "dis_ucode_ldr" succeed.
The logs after the successful boot are attached.
What can I do to make the boot use "dis_ucode_ldr" by default?
** Attachment added: "var_log3.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+a
Removing 'quiet splash' and adding 'earlyprintk=vga ignore_loglevel'
changed nothing - no more info on the screen.
Than I rebooted kernel 5.4.0-48 in recovery mode (Your system is
currently running without video hardware acceleration) and I am
attaching the var_log2.tar.gz
** Attachment added: "v
Please find attached a snapshot of the boot screen
(var_log.tar.gz::var_log/1.jpg) and the screen after Ctrl+x
(var_log.tar.gz::var_log/2.jpg) - it simply freezes and displays nothing
more.
What I did:
1. booted kernel 5.4.0-48 without "quiet" & "splash" - 1.jpg
2. Ctrl+x - the computer totally fr
I am not able to run "apport-collect 1895458" because the computer
freezes
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895458
T
Public bug reported:
The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18.
If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes.
I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot"; it freezes
after Ctrl+x
** Affects: ubuntu
Importance: Undeci
11 matches
Mail list logo