Verification with bionic-proposed of fio results.
For details see comment #5.
Overall performance has improved on the -proposed kernel
(tested in build without the patchset) and the patchset
as is in the -proposed kernel did improve it a bit more.
The results below show 3 results for each cache-
Verification done for bionic-proposed
based on the 3 tests / comments above.
** 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
The feature documentation in the Server Guide has been published [1].
[1] https://help.ubuntu.com/lts/serverguide/advanced-
installation.html#iscsi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Verification done on the new adapter, Solarflare X2542.
The tester reports that iperf3 tests ran solid for 24h-72h.
** 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 sub
[Original Description]
One LXC user reported lots of processes stuck in D state:
several threads waiting in the memory shrinker semaphore
(this symptom was thought to be/fixed via LP bug 1817628).
After some time, a provided crashdump revealed the issue
in ZFS's evict node path running in memory
Problem Details:
---
Helper scripts
(create /zfs.img and mount it on /zfs; and setup kprobe events for debug)
$ sudo ./zfs-mount.sh
$ sudo ./zfs-kprobes.sh
Print kprobe events to screen as we go:
$ sudo cat /sys/kernel/debug/tracing/trace_pipe &
Create file:
- allocates normal/fil
** Attachment added: "kmod-zget.c"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281634/+files/kmod-zget.c
--
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/
Fix Details
---
Problem report (GH Issue) upstream in ZFS on Linux:
https://github.com/zfsonlinux/zfs/issues/4816 ("Looping in zfs_zget()")
With very similar stack trace (syscall -> shrink ->
zfs_{inactive/rmnode/purgedir/zget})
https://github.com/zfsonlinux/zfs/issues/48
** Attachment added: "zfs-mount.sh"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281632/+files/zfs-mount.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.ne
debdiff for zfs-linux (zfs-linux_shrinker-deadlock-xattr.debdiff)
based on ubuntu/xenial-devel branch from LP source pkg git repo [1].
[1] https://git.launchpad.net/ubuntu/+source/zfs-linux
** Patch added: "zfs-linux_shrinker-deadlock-xattr.debdiff"
https://bugs.launchpad.net/ubuntu/+source/z
zfs-test test suite on xenial
-
Build/install the latest zfs-test suite from zfs.git:
$ git clone https://github.com/zfsonlinux/zfs.git
$ cd zfs
$ git log --oneline -1
c81f179 Metaslab max_size should be persisted while unloaded
$ sudo apt-get build-dep zfs-linux
$ su
has been run on original/modified
zfs-dkms package/kernel modules, with no regressions.
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: zfs-linux (Ubuntu Xenial)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Stat
** Attachment added: "zfs-kprobes.sh"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281633/+files/zfs-kprobes.sh
** Attachment removed: "kmod-zget.c"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281631/+files/kmod-zget.c
--
Problem Summary:
---
If an xattr directory inode and its xattr child inode are on the _same_
disposal list,
and the xattr directory inode is _before_ its xattr child inode in this
disposal list...
Then zfs_purgedir() of the xattr directory calls zfs_zget() for the xattr child
inode
Test-case for the problem (kmod-zget.c).
Header comments with steps to reproduce.
** Attachment added: "kmod-zget.c"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1839521/+attachment/5281631/+files/kmod-zget.c
--
You received this bug notification because you are a member of Kerne
zfs-test results w/ original & modified zfs-dkms
original
$ uname -rv
4.4.0-159-generic #187-Ubuntu SMP Thu Aug 1 16:28:06 UTC 2019
$ modinfo zfs | head
filename: /lib/modules/4.4.0-159-generic/updates/dkms/zfs.ko
version:0.
Fix Change Details
--
(Compare with comment #3)
The xattr dir/child inodes are evicted/disposed
immediately on file removal, not on shrinker.
$ touch /zfs/file
<...>-23940 [006] d... 10808.746798: p_zfs_mknode_0:
(zfs_mknode+0x0/0xe00 [zfs]) flag=0x0 dzp=0x88011a
id
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-lin
Colin, thanks for sponsoring and additional testing!
Is this ZFS regression test suite available to other people?
It sounds great for future work with ZFS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Verification done for zfs-linux on xenial-proposed.
The inodes for file, xattr dir, and xattr child are all evicted at file
removal time, not making it to any disposal list after file removal.
So the window/scenario for the problem to occur is not present anymore.
Log
---
$ echo 'deb http://arc
ts not being mark as lost in sync fabric
scan
e02de738c644 scsi: qla2xxx: Fix qla2x00_request_irqs() for MSI
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Kernel
Packages, whi
Hi Sebastian,
Thanks for collecting the data and describing the block device topology,
that's very helpful.
I'll try to reproduce the problem and analyze it.
cheers,
Mauricio
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Chan
Hi Sebastian and Ryan,
I've created the setup that each of you described on a VM,
but unfortunately it wasn't able to reproduce the problem.
I double checked the output of lsblk with Sebastian's and
it's the same (also the bcache sysfs configuration/status),
and with Ryan's description, and both
Ryan,
Part 1)
--
First, please try to reproduce the problem later, not so early in boot,
by disabling the bcache module on the kernel boot parameters, and then
loading it after the system has booted successfully.
(This should be possible as you mentioned the boot disk isn't involved.)
1) Edi
Hi Ryan,
Thanks a bunch for the crashdump; that helps.
I can confirm there's a valid and matching stack trace in the dmesg
file.
I'll take a look.
cheers,
Mauricio
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Tags added: seg
--
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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in linux package in Ubuntu:
In P
Hi Ryan, that's really great findings, thanks.
I'm out on holiday, and will check it next week.
--
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/1867916
Title:
Regression in kernel 4.15.0-
** Description changed:
test
+
01234567890123456789012345678901234567890123456789012345678901234567890123456789
--
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/1860982
Title:
test
St
The autopkgtests regressions are unrelated to this SRU.
Sure enough: the patch is for arm64 only, but the archs failing are
i386, ppc64el, and s390x.
The "regressions" also happen with the version in -updates, in the same
way as in -proposed.
makedumpfile [eoan/i386] [1]
Version
Hey Guilherme,
Thanks for the pointers and confirming these are not regressions, but
known issues. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1869465
Title:
Kdump-Tools: M
Hi Anand,
Thanks for reporting this bug.
Could you please try the kernel version in xenial-proposed? [1]
(version: 4.4.0-185.215)
It has a patch for what seems to be this problem, according
to the stack trace seen in apport's kernel crash dump below.
The patch is: 'net: handle no dst on skb in
The verification for makedumpfile used the vmcore file provided
by another user instead of /proc/vmcore (which is identical, as
it's a simple 'cp' copy of /proc/vmcore, per makedumpfile error.)
$ ls -lh /home/ubuntu/201909170743/vmcore.201909170743
-r 1 ubuntu ubuntu 32G Se
Verification done for Bionic.
bionic-updates: failure.
$ dpkg -s makedumpfile | grep -i version
Version: 1:1.6.5-1ubuntu1~18.04.4
[8.369266] kdump-tools[513]: Starting kdump-tools: * running makedumpfile
-c -d 31 /home/ubuntu/201909170743/vmcore.201909170743
/var/crash/202006171242/dump-i
Verification done for Eoan:
eoan-updates: failure.
$ dpkg -s makedumpfile | grep -i version
Version: 1:1.6.6-2ubuntu2
[8.717056] kdump-tools[514]: Starting kdump-tools: * running makedumpfile
-c -d 31 /home/ubuntu/201909170743/vmcore.201909170743
/var/crash/202006171254/dump-incomplete
[
Verification done for Focal.
focal (-release): failure:
$ dpkg -s makedumpfile | grep -i version:
Version: 1:1.6.7-1ubuntu2
[8.465657] kdump-tools[516]: Starting kdump-tools: * running makedumpfile
-c -d 31 /home/ubuntu/201909170743/vmcore.201909170743
/var/crash/202006171302/dump-incompl
Verification done for Xenial:
xenial-updates: failure.
$ dpkg -s makedumpfile | grep -i version
Version: 1:1.6.3-2~16.04.2
[8.647356] kdump-tools[507]: Starting kdump-tools: * running makedumpfile
-c -d 31 /home/ubuntu/201909170743/vmcore.201909170743
/var/crash/202006171359/dump-incomple
fects: linux (Ubuntu)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Fix Committed
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Affects: linux (Ubuntu Eoan)
Importance: Undec
Test Case:
-
$ cat aa-refcnt-af_alg.c
#include
#include
#include
#include
#include
int main() {
int sockfd;
struct sockaddr_alg sa;
/* Setup the crypto API socket */
sockfd = socket(AF_ALG, SOCK_SEQPACKET, 0);
if (sockfd < 0) {
perror("socket");
kprobes module to monitor the apparmor label reference count.
** Attachment added: "kmod.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883962/+attachment/5385006/+files/kmod.c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Monitoring the label reference count with the kprobes module:
- original kernel: the counter keeps increasing on every pair of
accept()/release() syscalls.
- modified kernel: the counter keeps stable.
Focal:
-
original)
$ uname -rv
5.4.0-38-generic #42-Ubuntu SMP Mon Jun 8 14:14:24 UTC 202
After a few hours with the reproducer running on the original kernel,
the kernel errors about the reference count are observed:
Focal:
-
$ uname -rv
5.4.0-38-generic #42-Ubuntu SMP Mon Jun 8 14:14:24 UTC 2020
$ ./aa-refcnt-af_alg
[ 9581.048189] [ cut here ]
[ 9581.
[B][PATCH 0/1] Fix apparmor reference leak via AF_ALG
https://lists.ubuntu.com/archives/kernel-team/2020-June/36.html
[B][PATCH 1/1] apparmor: check/put label on apparmor_sk_clone_security()
https://lists.ubuntu.com/archives/kernel-team/2020-June/37.html
[F][PATCH 1/1] apparmor: check/put
** Tags added: sts
** Changed in: linux (Ubuntu Groovy)
Status: Won't Fix => Invalid
--
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/1883962
Title:
apparmor reference leak causes
: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Tags: sts
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliv
Hi Martin,
Could you please test if the problem still happens with the latest
kernel version in focal-proposed? (currently 5.4.0-40-generic)
Something along these lines,
$ echo 'deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted' |
sudo tee /etc/apt/sources.list.d/proposed.lis
Martin, thanks.
I'll set the bug status to Incomplete for now,
and we can change it if you hit the issue again.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
)
Status: Won't Fix => In Progress
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Kernel
P
Could you please send /var/log/kern.log* ? Thanks!
--
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/1868388
Title:
watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]
Statu
Hi Sebastian,
Thanks for reporting this bug.
It indeed seems related to bcache per the stack trace in the screenshot.
Could you please collect and upload a sosreport of the failing system
(w/ any kernel version.)
$ sudo sosreport --batch --case-id lp1867916
This should generate a /tmp/sosreport
Hi Marcus,
Since 20.04 is not yet released, and the logs attached do not show the stack
trace
(it seems like an apport behavior, in OopsText.txt, not your/human's fault
AFAIK)
it seems there's little investigation that can be done in this error.
I'd suggest that if you can reproduce this proble
FWIW, bug 1870553 reported for apport, about the lack of the kernel
stack traces.
--
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/1868388
Title:
watchdog: BUG: soft lockup - CPU#11 stuck
Hi Sebastian,
Sure, that's certainly understandable.
For starters, the topology of the block/bcache devices would do it:
(set -x; lsblk; sudo dmsetup table; grep -r ^ /sys/block/bcache*/bcache)
> lp1867916.1.out 2>&1
Then please upload the output file (or copy/paste, if file access is
though.)
*** This bug is a duplicate of bug 1870260 ***
https://bugs.launchpad.net/bugs/1870260
This bug looks like a duplicate report of bug 1870260 (same
reporter/date/description/info.)
Marking thus bug as a duplicate of that as the other has further
comments/another duplicate.
** This bug has be
Oi Josimar,
Por favor, pode coletar um sosreport depois que o problema acontecer
algumas vezes (por exemplo, 24 horas com o notebook ligado), e anexar
nesse bug?
$ sudo sosreport --batch --case-id lp1880639
O arquivo será algo como /tmp/sosreport-*-lp1880639-2020-*.tar.xz
Seu kernel log mostra
Hi Ryan,
Sorry, I couldn't look at this earlier, but can put some cycles this week.
I'm looking at the stack trace, crashdump, and the offending patch.
Thanks again for your work on this.
cheers,
Mauricio
--
You received this bug notification because you are a member of Kernel
Packages, which i
Ryan,
Good progress with your crashdump; thanks!
I could root cause the source of the BUG() / NULL pointer address 0x8,
and its relation to the offending commit you identified.
Could you please provide another crashdump, with the _working_ kernel
4.15.0-88,
with the bcache device _mounted_? I'
Hi Ryan,
Thanks. I've found the problem; working on a fix next week.
Could you please provide/upload the output of these commands?
I can get those from the crashdump, but need to double check.
$ sudo grep ^ /sys/block/*/queue/*_block_size >
lp1867916-queue_block_size 2>&1
$ sudo bcache-super-sh
Ryan,
Thanks! That matches the expected output.
There's a bit more that I got curious about,
which is quicker to get with lsblk than in kdump:
$ lsblk --ascii > lp1867916-lsblk 2>&1
cheers,
Mauricio
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Hi Ryan and Sebastian,
Could you please verify whether these test kernels resolve the problem?
There's 5.4 for Focal/20.04 and 4.15 for Bionic/18.04.
https://people.canonical.com/~mfo/lp1867916/focal/
https://people.canonical.com/~mfo/lp1867916/bionic/
Thank you,
Mauricio
--
You received this
Hi Ryan and Sebastian,
Thanks for testing! Glad it helps.
This is the patch [1] to address the issue on a general level,
but it had a suggestion to be done at the driver level, which
may or may not interfere with the patch being applied -- both
approaches are not mutually exclusive.
I'm working
Sebastian, thanks for the information!
Sebastian, Ryan,
Do you remember specifying a block size of 512 kB for 'make-bcache' when
creating it?
e.g., make-bcache --bdev|-B /dev/mdN --block|-w 512k # or similarly.
Thanks,
Mauricio
--
You received this bug notification because you are a member of
Hi Sebastian, Ryan,
Thanks for checking and clarifying; it's very helpful.
Sebastian,
Yes, I think that makes sense for the physical block size (but not an expert :)
The problem with bcache is it takes it for logical block size as well,
which turns into that error -- as it cannot be greater than
For documentation purposes,
The bcache-specific patch has been sent today.
Waiting on review before providing test kernels.
[PATCH] bcache: check and adjust logical block size for backing devices
https://www.spinics.net/lists/linux-bcache/msg08411.html
cheers,
Mauricio
--
You received this bug
** Tags added: sts-sponsor-mfo
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Ioanna Alifieraki (joalif)
** Changed in: linux (Ubun
Hi Jo,
Thanks for the debdiffs!
The contents look good to me (versioning, dep3 headers)
except that the patch sequence number is missing, and
the changelog lacks a brief description of it.
I just fixed those minor things up, and verified all
debdiffs apply cleanly, quilt push -a applies cleanly,
** Patch added: "lp1869465_focal_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380770/+files/lp1869465_focal_v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
** Patch added: "lp1869465_xenial_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380773/+files/lp1869465_xenial_v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Patch added: "lp1869465_bionic_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380772/+files/lp1869465_bionic_v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Patch added: "lp1869465_eoan_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380771/+files/lp1869465_eoan_v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
** Patch added: "lp1869465_groovy_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869465/+attachment/5380769/+files/lp1869465_groovy_v2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
Hi Jo, Eric,
Eric, thanks for uploading to Groovy!
(Sorry, I had made similar changes to groovy v2 debdiff -- no worries, but just
wanted to let you know I checked those for groovy too, to not give you more
trouble in helping here! :-)
The changes have landed in Groovy, so I just uploaded to
Fo
Hi Daniel,
The build from master-next is no longer needed -- it's been just cut to
4.15.0-89 currently in bionic-proposed.
Can you give that a try instead?
It has all fixes previously in master-next, and nothing new remains in
qla2xxx.
$ git log --oneline Ubuntu-4.15.0-89.89..origin/master-next
Oh, sadly -89 doesn't work either; ok.
Yup, bisecting to find the specific issue/commit would be nice, to get a
better pointer.
On the quick path front, if you still have the time for another test,
could you please try the 5.4 kernel on Focal?
It should install/boot fine on Bionic, done that mys
Hi Daniel,
That's great news.
I had in mind to ask for testing w/ 5.3 HWE if 5.4 worked,
glad you gone ahead and could confirm it works too.
I'll be looking at the logs to try to identify any patch
that's missing and/or broken.
cheers,
Mauricio
--
You received this bug notification because y
Thanks for providing a picture with the strack trace.
This seems to be a duplicate of bug 1845454, for which
the linked Fedora bug report shows similar stack trace.
There's a test kernel builds with a fix in that LP bug,
see comment 11.
As you're able to install/boot with TPM disabled,
then you
Bug 1846542 has equivalent stack traces on 5.3.0-13. Suggested this test
kernel there.
--
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/1845454
Title:
Kernel panic with 19.10 beta image
S
Disco is now fix released with linux 5.0.0-31.33 (bionic: linux-hwe
5.0.0-31.33~18.04.1).
** Changed in: linux (Ubuntu Disco)
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.
ht
Disco is now fix released with linux 5.0.0-31.33 (linux-hwe
5.0.0-31.33~18.04.1).
** Changed in: linux (Ubuntu Disco)
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://bu
This seems to be a duplicate of bug 1845454.
Could you please try the test kernel build in bug 1845454 comment 11 and
tell if that resolves the problem?
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Similarly for bug 1847042.
--
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/1845454
Title:
Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10
(but 5.2 works)
Status
Hi Carlos,
Could you please provide a picture of the screen when it shows
"Kernel Panic Not Syncing: fatal exception in interrupt" ?
--
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/1855541
Verification on Trusty ESM updates.
$ uname -rv
3.13.0-175-generic #226-Ubuntu SMP Fri Nov 8 15:26:34 UTC 2019
The problem does not happen with the test-case.
(kmod.c updated for the new kernel uname strings, same instruction addresses
from test build apply.)
Test case snippets:
Migrated from
This bug has been fixed on Ubuntu 14.04 ESM,
linux kernel package version 3.13.0-175.226.
Marking the LP bug as Fix Released / Trusty.
** Changed in: linux (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packa
Public bug reported:
test
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Verification done on Eoan.
The gfs2_jadd i386 command on amd64 kernel no longer fails with ENOTTY upfront.
# lsb_release -cs
eoan
# dpkg --print-architecture
i386
# uname -m
x86_64
# uname -rv
5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020
# apt-cache madison linux-image-5.3.0-4
Hi Hui,
There seems to be some (small?) difference between your kernel
(5.3.0-1017-raspi2 #19+otg) and the reporter's kernel (original
5.3.0-1017-raspi2 #19-Ubuntu) ?
I realize you're of course aware of the changes introduced in this
'+otg' custom build you're running, but just wanted to mention
Verification successful on Ubuntu 14.04 (ESM):
No interrupts are generated on the PF by the link status check of the VF.
Verified with both Link down and Link up.
# uname -rv
3.13.0-174-generic #225-Ubuntu SMP Wed Oct 2 22:08:03 UTC 2019
# ls -ld /sys/bus/pci/drivers/ixgbe/*/net/*
drwxr-xr-x 5 r
Hi @mluypaert,
Do you still hit this problem?
Would you be able to provide steps of how you run bowtie2/star that
reproudces the problem?
And/or be able to try a workaround that might prevent it from happening?
Thank you,
Mauricio
--
You received this bug notification because you are a member
@mluypaert
Thanks for the details.
Do you know whether the problem reproduces with any bowtie2 example that
I could run for myself? I'm not familiar w/ it.
Apparently there's a workaround for it, if you're willing to test: to
disable NUMA balancing.
This _might_ impact performance on some memo
t; Medium
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
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/1813018
Title:
Kernel Oops
** Description changed:
- Kernel oops occurs randomly every now and then, seemingly when running
- memory-intensive processes (so far, it happened to me when using bowtie2
- or STAR).
+ [Impact]
+
+ * Users on NUMA systems (mostly servers) with
+NUMA balancing enabled (which is by default)
+
** Attachment added: "test.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813018/+attachment/5301230/+files/test.c
--
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/1813018
Titl
Not quite -- using a pastebin (expire 1y):
https://pastebin.ubuntu.com/p/pjMNxkJfJy/
** Description changed:
[Impact]
* Users on NUMA systems (mostly servers) with
NUMA balancing enabled (which is by default)
might hit a crash/BUG() on a race condition
if two simultaneous p
Checking if this snippet is properly spaced in a LP comment text
(instead of Description.)
Task 1 / CPU 1Task 2 / CPU 2
do_huge_pmd_numa_page() do_huge_pmd_numa_page()
- pmd_lock().
- trylock_page() //
** Attachment added: "kmod.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813018/+attachment/5301231/+files/kmod.c
--
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/1813018
Titl
Test-case snippet on original kernel on ESM (3.13.0-174.225)
[ 1387.632017] cpu 4/pid 1920/task TWO :: change_prot_numa() :: address =
0x7f4560e0, end = 0x7f456100
[ 1389.640322] cpu 5/pid 1921/task ONE :: do_huge_pmd_numa_page() :: addr/mask
= 0x7f4560e0, addr = 0x7f4560e0, pmd
Test-case snippet on original kernel (3.13.0-170.220)
[ 330.980173] cpu 5/pid 2126/task ONE :: Stage 4. T1 wake up T2... it may BUG!
<...>
[ 331.975122] cpu 6/pid 2125/task TWO :: Stage 4. T2 sleep for 1s... BUG
afterward?
[ 332.980237] BUG: unable to handle kernel paging request at ea
Test-case snippet on modified kernel on ESM (3.13.0-174.225 + patch)
The problem doesn't happen anymore.
[ 169.972017] cpu 4/pid 1765/task TWO :: change_prot_numa() :: address =
0x7f534f80, end = 0x7f534fa0
[ 171.976313] cpu 5/pid 1766/task ONE :: do_huge_pmd_numa_page() :: ad
** Description changed:
[Impact]
* Users on NUMA systems (mostly servers) with
NUMA balancing enabled (which is by default)
might hit a crash/BUG() on a race condition
if two simultaneous page faults of the same
transparent hugepage go into the path for
migration t
** Tags added: sts
--
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/1813018
Title:
Kernel Oops - unable to handle kernel paging request; RIP is at
wait_migrate_huge_page+0x51/0x70
Statu
101 - 200 of 727 matches
Mail list logo
