So in my case, my VM was configured with only 256MB of memory. This
caused no problem on the normal -virtual kernel but caused all sorts of
problems when I installed -lowlatency in the guest.
Upgrading to 384MB solved the problem reliably here, so perhaps this is
not the same thing afterall.
-
Kernel version 5.4.0-37-lowlatency, btw
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in lowlatency kernel with LXD
Status in linux-signed package
I have an LXD Virtual Machine refusing to boot after installing the
-lowlatency kernel on it. Sounds like these _might_ be related, so
here's my info. I'm on a NUC too, btw.
Host: Ubuntu 20.04 LTS, LXD 4.2 snap (running -lowlatency)
Guest: Ubuntu 20.04 LTS
The guest was running without problems
For the record, this continued to bother me until I got a replacement
laptop. I received an exact identical new laptop and have never since
seen this issue... Hardware fault and nothing else!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@Tim - What Patrick said... Or prevent the kernel package from being updated
until the fix is included:
https://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-package
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Okay, so MIGRATION is indeed enabled on the mainline kernel too and that
possibility has been ruled out - So we're not chasing ghosts. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
There must be a better way to do this...
All of these issues seem to arise from a BUG event in swapops.h:129. That
particular spot is a section that's only active, when the kernel was built with
CONFIG_MIGRATION=y. So first step is probably to verify that CONFIG_MIGRATION
is even enabled for
Okay,
Since updating the BIOS of my Lenovo T460s laptop from version 1.15 to
1.20, I've not seen this issue once.
Since I've not been able to successfully reproduce the error at any
point, I can't say for sure that the problem is gone. It has been a
weeks time, however, which is certainly a
The most promising so far is a brand new BIOS upgrade for my system. Haven't
seen the problem since upgrading 4 days ago.
Not quite ready to declare it solved, but certainly looks promising.
Happy holidays.
--
You received this bug notification because you are a member of Kernel
Packages,
Please let me know what kind of info you need, in order to find a
resolution to this issue - I can't imagine it's a hard one to solve,
given the right information. At the very least, determining if this is
indeed a hardware/firmware bug or a kernel bug, would be a HUGE step in
the right direction.
Hmmm, so several crashes again today while on battery. Even with
power/control set to "on" rather than auto. I'm on 4.9-rc8 btw.
--
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/1641322
FWIW, this appears to work around the issue:
Create file /etc/udev/rules.d/90-nvme-power.rules :
---
KERNEL=="nvme*[0-9]n*[0-9]", ATTRS{model}=="SAMSUNG MZSLW1T0HMLH-000L1*",
ATTR{device/power/control}="on"
---
On my system at least.
I'm sure the kernel should somehow blacklist settings that
Okay - Crashed 3 times this morning on rc7 AND rc6.
--
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/1641322
Title:
frequently lost connection to nvme
Status in linux package in Ubuntu:
I'd really like to have this issue resolved, so anything you guys need
to get closer to the culprit, just let me know. So far, 4.9-rc6 mainline
build appears stable.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Darn it... Just had the crash on rc7. Going back to rc6, thinking it may
be workload related... Will report back...
--
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/1641322
Title:
Problem not seen on 4.9-rc6 mainline. Moving on to 4.9-rc7 mainline
now...
--
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/1641322
Title:
frequently lost connection to nvme
Status in
I haven't found a positive fix for this issue in 4.9-rc6, but FWIW, I've
been running 4.9-rc6 for a couple of days without encountering this
issue.
I'll let you know how this goes after further testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I've not found a positive match, but this MIGHT be related to the
following upstream bug.
https://bugzilla.kernel.org/show_bug.cgi?id=112121
** Bug watch added: Linux Kernel Bug Tracker #112121
http://bugzilla.kernel.org/show_bug.cgi?id=112121
--
You received this bug notification because
Okay,
I've been running on 4.9-rc5 mainline all day, at work, with no issue at
all. After I take my laptop home, boom! Same problem. This is likely
triggered more often at home, where I'm on battery more than I am at
work, causing more aggressive power savings to take place.
In any case, my
I've installed latest mainline build and awaits the issue... I have
definitely seen the issue with the 4.9-rc4 mainline build, but the rc5
just yet... I'll be back with an update in a few days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Attachment added: "Captured dmesg output from the error happening"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+attachment/4776493/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Since before the release of Yakkety Yak, I've been having problems with
a new laptop with a Samsung nvme device: 05:00.0 Non-Volatile memory
controller: Samsung Electronics Co Ltd Device a804 (prog-if 02 [NVM
Express])
For whatever reason, I sometimes (often) loose
I'm having this issue on Wily today - Occurs on Wily kernel 4.2.0-15 but
not on 4.2.0-14 for me.
Bug #1503738 mentions this bug # as a duplicate, but while it probably
is the exact same issue, it's on a very different kernel/distro version
for me. Please let me know if the fix is automatically
I'm on a virtual machine and experiencing the same thing. The problem
seems to be covered pretty well in pages mentioned in #8.
My problem in more detail is trying to kexec the 3.16 kernel provided by
linux-generic-lts-utopic in trusty (from original 3.13 kernel, to allow
normal kernel updates on
Lots of talk about bandwidth, but (IMHO) at least as interesting is ping
times (because the results are instantly visible):
I'm on a ThinkPad T431s with an Intel Corporation Centrino Advanced-N
6235 (rev 24)
3.13.0-24-generic without PM (pinging my AP):
$ ping -c 5 192.168.8.2
PING 192.168.8.2
25 matches
Mail list logo
