Might be related? On first attempt in the updater GUI in Ubuntu 23.10
(latest STS stable version), I got
linux-image-nvidia-6.5.0-17-generic: constructing .ko files
./BUILD: 10: make: not found
./BUILD: 11: make: not found
./BUILD: 12: make: not found
./BUILD: 13: make: not found
./BUILD: 14:
I believe with dkms, you need a C compiler and related tools, so that
the nvidia kernel module can be built on your machine during kernel /
driver updates. So that probably means more packages have to be
installed. It might also be a bit more error-prone?
I'm not sure if it could affect secure
Another issue with the 6.2.0-25 kernel is in linux-modules-nvidia-525-generic:
Provides: nvidia-dkms-525 (= 525.116.04-0ubuntu0.23.04.1),
nvidia-prebuilt-kernel
But nvidia-driver-525 Depends: nvidia-dkms-525 (>= 525.125.06)
So the "dkms replacement" version provided by the pre-built modules
In lunar / 23.04, there is no linux-objects-nvidia-535-6.2.0-25-generic
package, but the linux-image-6.2.0-25-generic package has been available
for some time. Package upgrades therefore insist on switching to nvidia-
dkms, no matter what I try to do. So I'm still on 6.2.0-24.
Is this just
It's too late now, but there's a typo in the changelog: "shitfs".
--
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/1876645
Title:
Unable to handle kernel pointer dereference in virtual
Eric, I believe your mirror is lagging behind ab it?
I just installed 4.15.0-24-generic from -proposed and it fixes the issue for me
(tested 2 suspend cycles – previously it would fail 100% of the time).
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
You
Confirming this is still an issue for me after updating my bionic
installation to linux-image-4.15.0-23-generic 4.15.0-23.25, while
https://people.canonical.com/~khfeng/lp1752772-r8169-intx/ worked fine
in recent weeks.
--
You received this bug notification because you are a member of Kernel
I'm pretty sure this is a duplicate of #1752772 , right? Like Kai-Heng
Feng mentioned above. If so, please mark as duplicate.
--
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/1759644
Title:
>From http://kernel.ubuntu.com/~kernel-ppa/mainline/:
works: v4.17-rc1, v4.17-rc3, v4.17-rc4 (-rc2 not tested, but I assume it
works)
fails: v4.16.7
build for 4.16.8 failed, so I was unable to test that one.
--
You received this bug notification because you are a member of Kernel
Packages,
I forgot this yesterday: I accidentally compiled git master HEAD of that
repo first. It worked fine, so something fixed this bug between v4.16.5
and 46dc111dfe47. If required I can try to bisect, but it will take a
while, my CPU is almost 10 years old (takes 1+ hour to compile the
kernel). I guess
I cloned git://git.launchpad.net/~ubuntu-kernel-
test/ubuntu/+source/linux/+git/mainline-crack and checked out tag
v4.16.5, applied the 6 patches listed at the top of
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.5/ and the one debug
patch at https://lkml.org/lkml/2018/4/3/136.
journalctl
Related/Duplicate(?):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772
--
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/1760073
Title:
No network from suspend resume
Status
I have added a link to the upstream kernel.org bugzilla, I believe it's
the same bug.
** Bug watch added: Linux Kernel Bug Tracker #198973
https://bugzilla.kernel.org/show_bug.cgi?id=198973
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=198973
Importance: Unknown
Since updating to bionic, I notice the same symptoms (network not
working after suspend).
I'm adding this comment to note that this makes my network come up again, I'll
try to add this as a post-suspend script as described above:
$ sudo modprobe -r r8169
$ sudo modprobe r8169
(Suggested in
Thanks Joseph!
I now believe I'm seeing two different issues in 4.8 that are not in 4.4 and
slow down my boot, which is very confusing.
- #1: High number of kworkers (fixed in 4.8 using the two patches and bisected
by Doug Smythies already)
- #2: Unknown other issue. I've noticed that when
My boot time comparison: (Wall clock time from GRUB to lightdm ready for login)
4.4: 12.28s
4.8.0-26 + Patches (Joseph's kernel): 21.78s
4.8.0-22 (Yakkety): 25.06s
This is with NetworkManager-wait-online.service enabled, which seems to
take ~8s in my case.
The attached file has systemd-analyze
Thanks Joseph! I'm seeing the same effect described by Martin.
Boot+lightdm+loading Unity 7 is not as fast as it used to be in 16.04.
I need to compare timings (4.8 patched vs 4.8 vs 4.4) tomorrow to make
sure, but I also feel like it's a little faster now with the patches
applied.
The number of
Well, I guess the other patch is required as well for SLUB (not only SLAB as I
assumed at first):
https://patchwork.kernel.org/patch/9361853/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
My problem is probably the same that Doug Smythies described in bug
1626564 . I used the "echo workqueue:workqueue_queue_work >
/sys/kernel/debug/tracing/set_event" method and had about 1000 work
items enqueued by "memcg_kmem_cache_create_func" all at pretty much the
same time, which correlates
This is what I get right after boot and login into Unity 7 (executed in Gnome
Terminal):
$ ps aux | grep kworker | wc -l
1004
Kernel is 4.8.0-22-generic. After a few minutes, only 21 kworkers remain. Load
after 4 minutes is not excessive (1244 sleeping processes), forgot to check
load right
Same here, downgrading to 4.4 from Xenial improved the situation (boot
still feels a little slower than Xenial though, maybe because of the
NetworkManager bug). I use a 7 years old desktop computer based on a
Gigabyte motherboard and AMD Phenom II X4 955 CPU, So it's not Thinkpad-
related.
(From
Since 3.16.7-ckt11 appears to be affected by the ext4+raid0+trim
corruption bug [1], it might be better not to update to -ckt11.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=98501
** Bug watch added: Linux Kernel Bug Tracker #98501
http://bugzilla.kernel.org/show_bug.cgi?id=98501
--
You
This kernel (3.19.7), as well as the SRU-proposed 3.19.8, is also
affected by the ext+raid0+trim chunksize not a power of 2
patch-regression that causes severe data loss. So I certainly don't
want this patch to land on my trusty system with -lts-vivid kernel. :)
I have now verified that building the goldfish kernel from git with the
upstream commit cherry-picked, and then booting that kernel in the
emulator, solves my issue with libupnp.
** Summary changed:
- kernel null pointer dereference after setsockopt(…IP_ADD_MEMBERSHIP…)
+ [fixed-upstream] kernel
I think the goldfish kernel is not maintained in the android source
package, but in this separate linux-goldfish package, so it's time to
move this bug again.
** Package changed: android (Ubuntu) = linux-goldfish (Ubuntu)
** Summary changed:
- goldfish kernel panic after
There's actually a fix upstream, :
https://android.googlesource.com/kernel/goldfish/+/0836a0c191f580ed69254e0b287cdce58481e978
I hope there are plans to rebase to a recent goldfish kernel some time.
:)
--
You received this bug notification because you are a member of Kernel
Packages, which is
26 matches
Mail list logo
