BTW, I verified this on bionic, all fixed.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1833410
Title
verified zfsutils-linux 0.7.5-1ubuntu16.6 with 4.15.0-55.60, tested
against the Ubuntu zfs regression tests, no failures. Looks good to me.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
verified OK on xenial, 4.4.0-156
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1833410
Title:
idle-p
** Description changed:
+ == SRU Justification, BIONIC ==
+
+ Running the autotest regression test ubuntu_nbd_smoke occasionally trips
+ I/O errors such as:
+
+ [ 700.668758] print_req_error: I/O error, dev nbd0, sector 0
+ [ 700.668840] Buffer I/O error on dev nbd0, logical block 0, async pag
I've been running this for 3+ days now and cannot reproduce this
specific issue. From the look of the error it appears to be a hardware
related NMI issue, so perhaps we have some faulty H/W in this specific
case.
When running these tests for several days now with and without the
kernel parameters
I can't repro this specific issue, I believe it may be a H/W issue as
reported in this bug. Other reasons for the reboot tests failing are
marked in comment #3. Marking this as won't fix.
** Changed in: linux-aws (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notifica
Fix sent to mailing list: https://lists.ubuntu.com/archives/kernel-
team/2019-April/099806.html
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840161
Title:
Very severe regression in ZFS 0.7.12 in 18.04.3
Stat
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** Changed in: thermald (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Tags removed: veri
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** Tags removed: verification-needed verification-needed-bionic
** Changed in: thermald (Ubuntu Bionic)
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** No longer affects: thermald (Ubuntu Bionic)
** Tags removed: verification-needed verification-needed-bi
The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history. This bug has already been fixed
and the verification for bionic can be ignored.
** Changed in: thermald (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Tags removed: veri
I wonder if the msr module is not loaded. Try
sudo modprobe msr
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1840454
Title:
kernel 5.2 disallows thermald's direct MSR writes
Statu
Good point.
--
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/1840454
Title:
kernel 5.2 disallows thermald's direct MSR writes
Status in linux package in Ubuntu:
Incomplete
Status in the
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
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/1840867
The issue was that we had a lockup on a futex on a pthread_cond_wait().
I've added a time out to this and a re-spin with a yield to break the
lockup.
Fix committed:
https://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=e7ef382acc7d49aa21a7e060872717c782db41aa
Please re-test and let me kn
And also this fix is helpful:
https://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=9fdaf8b716038f12a188ba82fa25a8638bdd09bf
--
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/1840867
@Dimitri, so you set the defaults w/o any benchmarking stats?
I'll see if I can get some time to check what the sane options are per-
arch.
Colin
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
@Dimitri,
Seems that for initramfs lz4 makes a lot of sense, see:
https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3/boot-speed-
initramfs-decompression-eoan.ods
The load times for LZ4 is slower than the previous default, however, the
decompression time makes up for this unless one is booting
Seems to occur when exercising /dev/hpet
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1841747
Title:
dev test in ubuntu_stress_smoke_test crashes AWS c5.large with Disco
Status in
The following run as root will cause the instances to hang and then
reboot (by the watchdog?)
#include
#include
#include
#include
#include
int main(void)
{
for (;;) {
int fd;
fd = open("/dev/hpet", O_RDONLY | O_NONBLOCK);
close(fd);
Cosmic is now end-of-life. Does this still occur on Disco?
** Changed in: linux (Ubuntu)
Importance: High => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Pa
Do we have any hunches on how to reproduce this issue?
--
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/1779156
Title:
lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
Statu
That's really helpful to know John, thanks for the feedback.
--
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/1832384
Title:
Unable to unmount apparently unused filesystem
Status in linux
Assignee: Colin Ian King (colin-king)
Status: Triaged
** Also affects: lxc (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: lxc (Ubuntu Disco)
Importance: Undecided
We generally have a 3 week release cycle on kernels, so if it's in
-proposed it probably in the later 1-2 weeks of this cycle.
--
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/1832384
Title:
See also: https://wiki.ubuntu.com/Kernel/StableReleaseCadence
and https://kernel.ubuntu.com/
--
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/1832384
Title:
Unable to unmount apparently un
latter 1-2 weeks of this cycle
--
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/1832384
Title:
Unable to unmount apparently unused filesystem
Status in linux package in Ubuntu:
Incomple
** Changed in: thermald (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1824690
Title:
proc_thermal flooding dmesg
Status in linux package in
Hi Giovanni, do you mind testing the kernels as mentioned in comment
#24,
1. download the .deb packages https://kernel.ubuntu.com/~cking/lp-1824690
2. from the relevant Download directory, install them using:
sudo dpkg -i *.deb
3. reboot and test.
Thank you.
--
You received this bug notifica
Hi Louis,
can you provide some information about the physical devices and also the
benchmark tool you are using for the benchmarking?
Thanks
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: Confirmed =&
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
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/1815178
Title:
18.04: Raid performances on kernel 4.15 and newer are
** Changed in: ubuntu-kernel-tests
Importance: Undecided => Medium
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It appears that syscalls are not available on i386, got zero syscalls on
bionic, cosmic, disco. It works OK on xenial.
sudo lttng list --kernel --syscall
..produces zero syscalls.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
And for amd64 bionic+ it fails to generate syscall info too.
--
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/1802495
Title:
lttng-smoke test failed on i386 4.18 kernel
Status in ubuntu-k
Course bisect, this does not work with stock upstream kernels since at
least 4.7-rc1. For now I'm going to disabled this part of the lttng
tests until I can get it to work again with stock 4.8+ kernels.
@Sam, am I missing something, but has this been failing for a while and
it's not been noticed?
Disabling the kernel system call tracing for the moment:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=b1654ce9e8d7d744af76787b6d4a5ff7bcec387d
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
I've reported this to the upstream lttng project:
https://bugs.lttng.org/issues/1184
** Bug watch added: bugs.lttng.org/issues #1184
https://bugs.lttng.org/issues/1184
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are
FYI I've sponsored this package and it's waiting now for the SRU team to
handle.
--
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/1828763
Title:
Cannot build kernel 4.15.0-48.51 due to an
Fix committed: https://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=a4e26439837ce6e472b502da430ff863f6c7c265
** Changed in: stress-ng
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
** Changed in: stress-ng
Status: Fix Committed => Fix Released
--
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/1813847
Title:
af-alg stressor triggers modprobe throttling
Status i
** Changed in: linux-azure (Ubuntu)
Importance: Undecided => High
** Changed in: linux-azure (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/b
** Changed in: linux-azure (Ubuntu)
Importance: Undecided => High
** Changed in: linux-azure (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/b
Minor note: this appears to be a kernel panic during shutdown rather
than a boot hang issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while reboot
** Changed in: linux-aws (Ubuntu)
Importance: Undecided => High
** Changed in: linux-aws (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/18
So I don't think this is a kernel related issue. The error message
"error while loading shared library" is being emitted from the libc
"fatal_error" shared library dynamic loader from init and an exit() is
being called, causing the kernel to report that init has exited, which
leads to the stack du
The "hyperv_fb: Unable to send packet via vmbus" message is from
synthvid_send(), drivers/video/fbdev/hyperv_fb.c (the Microsoft Hyper-V
Synthetic Video Frame Buffer Driver). This error occurs when
vmbus_sendpacket() fails to send a packet via the write ring buffer (see
hv_ringbuffer_write())
This
I believe the "ERROR ExtHandler /proc/net/route contains no routes" is
from the "Azure Linux Agent", so that's proprietary code that I don't
have any idea how or why it is emitting that message.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@Sean, can you add the info for Joseph?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while rebooting cloud instance
Status in linux-azure package in
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a
I've not been able to reproduce this on my VMs, can I get access to one
of these machines to figure out why it is failing and how to fix this.
--
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
I've been running 4 i3 instances running bionic, cosmic and xenial
without any boot hangs using the following kernel boot parameters:
nmi_watchdog=0 pcie_aspm=off nohpet
These have been running now for 8+ hours, with easily over 70 reboots
per instance w/o any issues. I'll try and factor out which
** Changed in: zfs-linux (Ubuntu)
Status: Fix Released => In Progress
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because
** Changed in: linux-aws (Ubuntu)
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1822175
Title:
i3.metal flavour type fails to respond after a
** Description changed:
+ SRU Bionic
+
+ == SRU Justification ==
+
+ Intensive I/O such as performed by ZFS send/receive can cause hangs because
of monopolization of the global system_taskq. The outcome is that z_zvol hung
+ tasks occur and I/O gets blocked.
+
+ == Fix ==
+
+ Upstream ZFS com
Fix sent to kernel team mailing list for review:
https://lists.ubuntu.com/archives/kernel-team/2019-May/100990.html
** Description changed:
SRU Bionic
== SRU Justification ==
Intensive I/O such as performed by ZFS send/receive can cause hangs because
of monopolization of the global
I suspect this is due to lack of entropy on the machine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1831229
Title:
getrandom02 from ubuntu_ltp_syscalls failed with timeout multip
Maybe exercising the disc(s) may help, this generates interrupts that
get used to add entropy to the entropy pool.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1831229
Title:
getra
..or network too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1831229
Title:
getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier =
3 on D-KVM
Status in ubuntu-k
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1822247
Title:
ubuntu_nbd_smoke_test failed on P9 with Bionic kern
I've applied the patch to the Ubuntu Bionic kernel, please re-test by
downloading and installing all the packages in:
https://kernel.ubuntu.com/~cking/lp-1824690/disco/
..and let me know if that helps.
And to answer your questions in comment #27, the kernel is packages are
just build using the c
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a
@Giovanni - any progress on testing this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1824690
Title:
proc_thermal flooding dmesg
Status in linux package in Ubuntu:
Incomplete
St
I had a quick look at there are quite a few differences between the
Delphix ZFS git repo and the upstream ZFS git repo. Github states: "This
branch is 376 commits ahead of zfsonlinux:master.".
So:
1. Does this issue occur with stock ZFS rather than Delphix ZFS?
2. With the activity you are perfo
Great, thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1824690
Title:
proc_thermal flooding dmesg
Status in linux package in Ubuntu:
Incomplete
Status in thermald package
, this touches a sysfs kernel interface that is not used much.
The fix narrows the scope of touching specific page frames, so the page
frame scope is reduced by the fix.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Description changed:
- == SRU ==
+ == SRU [Xenial][Bionic][Cosmic][Disco][Eoan] ==
== Justification ==
When accessing page frames that are greater than max_pfn using the idle-
page sysfs interface an oops is triggered that kills the process that
writes to the sysfs interface.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Fix committed: https://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=66c09c1a1b73d58855173474daaec98138926e62
Was accidentally killing a child before that child could complete a wait
and reap of it's own child.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
*** This bug is a duplicate of bug 1822247 ***
https://bugs.launchpad.net/bugs/1822247
** This bug has been marked a duplicate of bug 1822247
ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is s
This would require a kernel fix to disable this kernel message.
Perhaps just disabling thermald may be the best way forward for the
moment.
sudo systemctl disable thermald
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubunt
When a laptop reaches a CPU specific temperature threshold it will cause
rapid and immediate shutdown to avoid physically damaging the machine.
Older laptops sometimes have issues because the cooling paths are not
100% effective and can lead to overheating, so you may be OK with
disabling thermald
Thanks Srinivas for the update. If you can let us know when the patch
has landed I can add this into the older kernels as part of a SRU
procedure.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.n
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1750786
Title:
stress-ng enosys stressor triggers a kernel BUG
St
*** This bug is a duplicate of bug 1826626 ***
https://bugs.launchpad.net/bugs/1826626
** This bug has been marked a duplicate of bug 1826626
package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade:
triggers looping, abandoned
--
You received this bug notification beca
Thanks for testing!
--
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/1822247
Title:
ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
Status in ubuntu-kernel-tests:
New
Status in li
Ubuntu runs with a default log level of KERN_WARNING (4), so KERN_NOTICE
(5) should be silently ignored.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1824690
Title:
proc_thermal flo
=> Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1824690
Title:
proc_thermal flooding dm
Hi Giovanni, would you mind testing the fix as mentioned in comment #24
so that we can see if this addresses the issue for you?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1824690
Ti
** Attachment added: "Photo of most of the crashes, hung, no console available,
completely dead"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+attachment/5279525/+files/DSC_0795.JPG
--
You received this bug notification because you are a member of Kernel
Packages, which is su
** Attachment added: "Photo of console - this is where it locks up"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+attachment/5279524/+files/DSC_0805.JPG
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Public bug reported:
Installed Bionic 18.04.2 i386 Desktop on a Lenovo x220i and upgraded to
proposed. The 5.0.0.22 kernel crashes in various ways with video
corruption being a main visible featured.
The CPU is a i3-2350M CPU, a 64 bit capable CPU, being booted with EUFI
firmware disabled, so us
** Description changed:
- Installed Bionic 18.04.2 i386 Desktop on a Lenovo x220i and upgraded to
- proposed. The 5.0.0.22 kernel crashes in various ways with video
- corruption being a main visible featured.
+ Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo x220i
+ and upgraded
One other data point, booting the upgraded machine to the 4.15 kernel
and it works OK, so this corruption/hang is most probably not to do with
changes in userspace on the upgrade to -proposed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Tried the same on an HP Mini 210-1000, Atom N450 and it works fine, so
this is a H/W specific issue.
--
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/1838115
Title:
linux hwe i386 kernel 5
Tried https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.20/ - less
corruption and now the splash screen starts but as soon as splash
transitions to the X display we get an immediate hang.
I believe the 5.0.0 crash occurs before the splash screen starts, so
it's really early in the boot process.
Tried: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.3/
No splash screen, and screen turns off after several seconds and machine is
completely hung after that.
Most probably all of this is a regression in the i915 driver for 32 bit
platforms with Intel® HD Graphics 3000
** Changed in: lin
So I've tested it on a range of Lenovo's that I can get my hands on
(kids, family etc).. and the following fail in the same way:
Lenovo X220 Intel(R) Core(TM) i3-2350M (HD Graphics 3000)
Lenovo X230 Intel(R) Core(TM) i5-3210M (HD Graphics 4000)
Lenovo L430 Intel(R) Core(TM) i3-3120M (HD Graphic
Looks like this is a kernel modeset bug, booting with i915.modeset=0
fixes the issue
--
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/1838115
Title:
linux hwe i386 kernel 5.0.0-21.22~18.04
Did a bisect on the drm i915 driver, came up with no root cause.
Did a full bisect between 4.18 and 4.20, bisected down to a PTI commit:
7757d607c6b3186de42e1fb0210b9c5d8b70 is the first bad commit
commit 7757d607c6b3186de42e1fb0210b9c5d8b70
Author: Joerg Roedel
Date: Wed Jul 18 11:41:1
OK, I've proved that this is the core issue, booting 5.0.0-21.22~18.04.1
with nopti boots successfully.
--
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/1838115
Title:
linux hwe i386 kerne
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
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/1838115
Title:
linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on
Tried today's Linux tip, boots OK, so a reverse bisect to tip should
prove to be instructive on a potential fix.
--
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/1838115
Title:
linux hwe i
1 - 100 of 2270 matches
Mail list logo
