** Description changed:
Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to
linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots
with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter.
In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8,
Public bug reported:
Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to
linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots
with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter.
In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means
Note that this is not limited to containerd; we're running an upstream
version of the prometheus `node_exporter` on several hosts that is also
seeing spurious hangs that started after upgrading to the -132 kernel.
Rebooting into -131 fixes it.
--
You received this bug notification because you are
@Simon, you should upgrade the ubuntu-mainline-kernel script, the
directory layout on kernel-ppa has changed, so the kernels are in a
different location.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
As a workaround you can add "initcall_blacklist=elants_i2c_driver_init"
to GRUB_CMDLINE_LINUX, run 'update-grub', power down the laptop and
start it again.
Works for me. (5.7.1 kernel-ppa mainline)
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
We're seeing a similar crash on a 16.04 based machine running
4.15.0-66-generic ; downgrading to 4.15.0-51-generic appears to prevent
it.
Appended kernel log with very similar entries.
** Attachment added: "kernel log from loading ceph to reboot"
https://bugs.launchpad.net/ubuntu/+source/linu
age: linux-image-4.13.0-38-generic 4.13.0-38.43
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jasper 279
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jasper 2791 F pulseaudio
/dev/snd/controlC0: jasper 2791 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Apr 7 17:49:22 2018
HibernationDevice: RESUME=UUID=26d3afe5-0e06-4669-8d23-c639f3ca7011
tail -f works because it checks the file every sleep-interval seconds (defaults
to 1 second).
tail -f -s 10 /var/log/syslog gives a burst of new lines every 10 seconds.
With this test I see 10-seconds bursts with linux 4.10.0 and 4.13.0
indicating this bug isn't fixed.
--
You received this bug
I have never used this machine with anything less than 15.04, so sorry I
cannot say.
On 10 May 2015 at 12:13, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Jasper, did this issue not occur in a release prior to Vivid?
>
> --
> You received this bug notifi
Sorry Christopher,
Further testing reveals that the bug is still present in 4.1-rc2. No idea why
it worked the first time, but it has not subsequently.
** Tags removed: kernel-bug-fixed-upstream kernel-bug-fixed-upstream-4.1-rc2
needs-reverse-bisect
** Tags added: kernel-bug-exists-upstream ke
I do not use the workaround, and turbo mode is automatically enabled.
--
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/1452460
Title:
Turbo mode on i7 is not enabled upon resume
Status in
The `problem' is fixed in 4.1-rc2.
But
As with the `echo 0... echo 1`... method the processor is _always_ in turbo
once it has resumed from sleep.
On my i7-4500U this is about 2.78 and 2.97Ghz.
** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-rc2
** Tags added: kerne
Using linus' latest kernel from git (12 hours old) the `problem' persists, and
turbo must be re-enabed manually or via systemd script.
I built the deb-pkg target.
I will test the other ubuntu versions soon.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-rc2
--
You r
Many thanks for the quick response. I will disseminate this to the many
questions in ask-ubuntu relating to resume scripts.
--
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/1452460
Title:
Cheers.
--
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/1406132
Title:
Radeon GFX card fails on 3.16.0-28
Status in linux package in Ubuntu:
Triaged
Bug description:
Expected behavi
All kernels from mainline worked (took a selection from 3.16.0 to 3.19)
It turns out that 3.16.0-28 works without
linus-image-extras-3.16.0-28-generic
which contains
/lib/modules/3.16.0-28-generic/kernel/drivers/gpu/drm/radeon/radeon.ko
and
/lib/modules/3.16.0-28-generic/kernel/drivers/video/fbde
Thank you.
Upstream kernel 3.19-rc2 (generic and low latency for Vivid) solved the issue.
** Tags added: kernel-fixed-upstream-3.19-rc2
--
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/1406
Public bug reported:
Expected behaviour, and behaviour on previous kernels (3.16.0-25 and before):
Normal boot, ending in Lighdm login screen or in my case Kodi
Observed behaviour:
Boot ends with blank screen, dmesg shows errors.
Hypothesus:
This is a bug related to upgrading the kernel.
What
me="third_party" pid=2628
comm="apparmor_parser"
[ 160.915247] systemd-logind[1965]: Failed to start user service: Unknown
unit: user@1000.service
[ 160.918592] systemd-logind[1965]: New session 2 of user jasper.
[ 240.043467] INFO: task kworker/2:1:199 blocked for more
20 matches
Mail list logo
