Sorry for the wait, I took a few days off.
This kernel worked well.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5525012/+files/journalctl.log
--
You received this bug notification because you are a member of Kernel
Packages,
I tried the new kernel 5.11.0-36-generic, but the problem is still there.
I'm attaching the log in case it's helpful.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5526932/+files/journalctl.log
--
You received this bug notifica
** Attachment added: "journalctl -k -b -1 > journal.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5518125/+files/journal.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
apport information
** Tags added: apport-collected focal
** Description changed:
Hello,
My laptop run well with last 5.4 linux kernel even if I connect my
thunderbolt dock.
When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock
and 2 monitors connected, the kernel
Could you take a snapshot while you run into a "panic" since even the
journal log you post doesn't have the information of the panic. And does
it only happen 100% when 2 monitors connected? And it's AMDGPU, could
you help verify the latest mainline kernel here?
https://kernel.ubuntu.com/~kernel-ppa
Ok, but I don't know how to "take a snapshot" while my machine run into
a kernel panic.
Can you explain me how to do that ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940113
Title:
5.14.0-rc7 boot without problem even if the dock and the two additional screen
are plugged in.
I put the boot log in attachment
** Attachment added: "journalctl -k -b -1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5520108/+files/journal.log
--
You received this
** Attachment added: "dpkg -i *5.14*.deb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5520109/+files/dpkg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
If it helps, I also post the result of `journalctl -k -b all` here.
I have the impression that the kernel panic of kernel 5.11 does not
appear, the crash occurs systematically between seconds 2 and 4 of the
boot sequence.
However, this extraction contains logs of successful boot on kernel
5.11, w
@Chris Chiu (mschiu77): "And does it only happen 100% when 2 monitors
connected?" → Yes !
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940113
Title:
Linux 5.11.0-25 & 5.11.0-27 panic
Ok, sorry, I went a little too fast!
The attachment #23 does not contain the right log. Apologize.
Fortunately, attachment #25 contains interesting items. Look for the
sequence "-- Reboot --" and there, at occurrence #54 and #55, there
seems to be traces of kernel panic. There are also two boot se
So the mainline 5.14 works for you even with 2 monitors connected, right?
Then could you help me find out which version starts to have this problem by
testing the kernel in the url down below?
https://people.canonical.com/~mschiu77/lp1940113/H/
https://people.canonical.com/~mschiu77/lp1940113/I/
I just tested both kernels and here are the results:
I first rebooted on the 5.11.0-33 kernel with the dock and the two screens
connected.
The system froze after 3s of boot.
I unplugged the dock and rebooted on the 5.11.0-33 kernel.
The boot went well until the desktop. There, I reconnected the
@Chris Chiu (mschiu77): "So the mainline 5.14 works for you even with 2
monitors connected, right?" → Yes !
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940113
Title:
Linux 5.11.0-25
Thanks for the testing result. From your result the 5.13.12 still have
the issue but gone in 5.14, and it helps to find out which commit fix
this. https://www.spinics.net/lists/kernel/msg4038892.html could be the
patch we need. So I re-build a 5.13 kernel based on it. Please help
verify the kernel
You're welcome. Thank you for taking time to solve this problem! The
result was close to the previous version 5.13:
The boot with dock and dual screen crashed at 4s then, after a dozen
seconds, a kernel dump was displayed, then nothing.
The startup without the dock went well, then the connection
The dmesg of 5.13 kept showing the error as follow
août 26 11:18:46 syncom kernel: Workqueue: kacpid acpi_os_execute_deferred
août 26 11:18:46 syncom kernel: RIP: 0010:acpi_ds_exec_end_op+0x182/0x779
But it didn't show in kernel 5.11. That's pretty confusing to me. I may
need more ACPI debug me
I booted the kernel 5.13.12 with the dock unplugged, everything went
well. Once the dock was plugged in, the screen froze but strangely this
time, I could move the mouse on the screen (with the trackpad of the
laptop). Maybe I didn't notice this possibility before?
I then started the kernel 5.14.r
The ACPI error didn't show in 5.13.12, so 5.14 may fix the ACPI related
issues but there should be AMDGPU related issue between 5.11 and 5.13.
Please help me find out ACPI related fix first with the following
kernels. Thanks
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14-rc1/
https://kernel.
There are no deb packages in the first link (rc1).
The rc2 version started and worked without problem with the dock and the
two screens.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5521666/+files/journalctl.log
--
You receiv
There's so build problem with 5.14.0-rc1. Could you try
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.13/? Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940113
Title:
Li
And here is the result: complete freeze of the screens. I attached the logs as
usual.
So 5.14.0-rc2 works and 5.13.13 crash. It remains to find what has been
corrected between these two versions?
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/19401
Yes. There're some amdgpu update between 5.13.3 and 5.14.0-rc2. I'll
pick some of them to narrow down the range. Please help me test the
kernel in https://people.canonical.com/~mschiu77/lp1940113/amd_3.2.137/.
Thanks
--
You received this bug notification because you are a member of Kernel
Package
This time, GDM failed to launch (without dock). I ended the startup sequence on
a blinking cursor in the upper left corner and that was it.
I was able to connect to the TTY2 where I ran htop. There I plugged the dock
and a kernel oops was displayed. Then, htop progressively erased it partially.
>
Good. Please help me test the kernel in
https://people.canonical.com/~mschiu77/lp1940113/amd_3.2.140/. Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940113
Title:
Linux 5.11.0-2
Result: partial freeze of the screens. No mouse but keyboard ok. htop
running but unable to launch a new prompt or any other process.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5523256/+files/journalctl.log
--
You received t
Hmm...It means there's still huge difference.
Please try our 5.14 release candidate
https://people.canonical.com/~mschiu77/lp1940113/5_14_next/. Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
27 matches
Mail list logo
