We are waiting for the new kernel too as we are currently blocked with
new installations based on 18.04 LTS. Can you please give a date when it
will be ready? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Thank you for your analysis and test kernel.
A lot of our machines (Supermicro X11 / Xeon W-2133 based) also suffer from the
problem introduced by 4.15.0-177.
I can confirm that the kernel 4.15.0-182-generic #191+lp1973167 provided
by Kai-Heng Feng fixes the issue on my HW.
Could you please proc
Here's a test kernel with the commit:
https://people.canonical.com/~khfeng/lp1973167/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-177-generic freezes on the welco
Same problem here. Can't boot anything after 4.15.0-176. Boot sequence
falls into the emergency mode or never boots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-1
Same problem here with ASUS VivoBook X510U
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-177-generic freezes on the welcome screen
To manage notifications about th
Hi!
After all, I am lucky: my Dell Latitude 5480 succeeds sometimes to start
XUbuntu 18.04.6 LTS normally, but often freezes on boot because "A start job is
running for ..." (several messages of this type), both with
linux-image-4.15.0-177-generic and linux-image-4.15.0-180-generic, while
every
I'm on a Dell Precision 3520 with Kubuntu 18.04, I have the same issue
with 4.15.0-177 and 4.15.0-180. This also seems to disable my sound,
bluetooth, and wifi. Currently booting 4.15.0-176.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
It affects to:
Kubuntu 18.04, Dell Latitude 7490.
I could start by blacklisting the intel-lpss-pci module (in this case the mouse
doesn't work) and loading it again after boot (the mouse works again fine).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
FIXED IT! It is indeed the intel_lpss driver, at least in my case.
This commit:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186&id=3879f4364139acb2bd3932e6a15994f109c49d6b
will not work right when a module that is asynchronously loaded tries t
My "prime suspect" is this commit:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186&id=3879f4364139acb2bd3932e6a15994f109c49d6b
Also see Linus' comments when this patch was submitted to the mainline kernel:
https://www.spinics.net/lists/kernel/m
I have found a change between 176 and 177 that looks suspicious:
diff -upr --color 176/linux-source-4.15.0/kernel/module.c
177/linux-source-4.15.0/kernel/module.c
--- 176/linux-source-4.15.0/kernel/module.c 2022-03-29 19:39:48.0
+0200
+++ 177/linux-source-4.15.0/kernel/module.c 2
> I just installed kernel 4.15.0-180 ... problem is still there
Also for me - no problem in -176, but problems in -177 and -180.
If there's logs that it'd be useful to see, just ask.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
I just installed kernel 4.15.0-180 ... no change ... problem is still
there :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-177-generic freezes on the welcome scr
Trying to isolate the issue, I:
1. Booted my portable Ubuntu 18.04.6 installation on a different machine
(different CPU, chipset, but still Intel). On the other machine, kernel
4.15.0-177 booted without issues, so apparently it does not depend on
the installation, but rather on the hardware or BIO
Have the same problem on ThinkPad T480s and 18.04.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-177-generic freezes on the welcome screen
To manage notification
Also effected - Asus UX430UA Intel I5 running Ubuntu 18.04.6
Noticed 3m delay when processing UFW and possibly boot/efi. Also effected
sound, not checked other functions.
Reverting to 4.15.0-176 resolves the problem
Not sure what log to upload - please advise.
--
You received this bug notificat
I'm affected too
Ubuntu 18.04.6 LTS, Asus UX305UA
** Attachment added: "lshw.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+attachment/5591492/+files/lshw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
I'm affected too.
Kubuntu 18.04, Acer Aspire 5 (A517-51G-5826), NVIDIA GeForce MX130
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-177-generic freezes on the welco
A similar issue here, different hardware and graphics to above machine.
Dell 5000, Ubuntu 18.04, boots OK off "4.15.0-176-generic" but with
"Linux 4.15.0-177-generic" hangs at the welcome screen.
"sudo lspci -vnvn" (when booted off 4.15.0-176-generic) returns:
00:00.0 Host bridge [0600]: Intel Co
Alas! I spoke to seen. The seeming "workaround" only lasted for one
boot, and after that, the ~180 seconds delay is back to stay, although
the Intel IOMMU is still disabled.
So this issue is "sporadic". Maybe even a race condition... :(
And maybe not even related to the intel-lpss driver: The lin
After grepping dmesg for all lines about the "00:15" devices, I found
two lines starting with "DMAR:", which made me think of another machine
running debian which had issues with DMAR: devices that were related to
the Intel IOMMU.
So I tried the workaround I knew from there:
Edit /etc/default/gru
After finding someone reporting the same issue
(https://forums.linuxmint.com/viewtopic.php?t=373747&p=2175201) and
reading that the machine may come alive after a while, I found that
indeed after 3 minutes the machine works. dmesg that reveals that it
seemingly was the initialization of the intel_l
23 matches
Mail list logo
