** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Bionic)
** Description changed:
[Impact]
- * Users of the Linux kernel's crypto userspace API
-reported BUG() / kernel NULL pointer dereference
-errors after kernel upgrades.
+ * Users of the Linux kernel's crypto userspace API
+ reported BUG() / kernel NULL pointer dereference
+ erro
alg_accept+0x15/0x20 [af_alg]
+ SYSC_accept4+0xff/0x210
+ SyS_accept+0x10/0x20
+ do_syscall_64+0x73/0x130
+ entry_SYSCALL_64_after_hwframe+0x3d/0xa2
** Also affects: linux (Ubuntu Groovy)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Con
)
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
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
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
: 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
** 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
[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
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.
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
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
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");
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
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
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 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 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
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
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
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
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
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
** 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://
** 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_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_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
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,
** 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
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
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
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 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
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
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,
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,
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,
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
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
** 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
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-
** 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,
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:
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 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
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
*** 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
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.)
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 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
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
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 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
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,
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
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 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 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
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:
Hello Hari,
Glad to see you around on bugs again. :)
Could you please confirm whether the fix for this bug also addresses LP bug
1655280?
(i.e., the verification for xenial would be equivalent/also validate that other
bug.)
Thanks,
Mauricio
--
You received this bug notification because you a
nce: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linu
The intel-microcode package [1] had an update in mid November 2019
(version "3.20191115"ish) with an entry apparently related to the
symptoms seen in the kernel log you provided:
'Unexpected Page Faults in Guest Virtualization Environment (SKL-188,
KBL-144, CFL-136 errata)'
If you're running on I
** Changed in: makedumpfile (Ubuntu Disco)
Status: In Progress => Won't Fix
** Changed in: makedumpfile (Ubuntu Disco)
Importance: High => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
** Changed in: makedumpfile (Ub
** Changed in: makedumpfile (Ubuntu Disco)
Importance: Low => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpf
** Changed in: makedumpfile (Ubuntu Disco)
Status: In Progress => Won't Fix
** Changed in: makedumpfile (Ubuntu Disco)
Importance: Low => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
You received this bug notifi
Hi Guilherme, Thadeu,
The re-spinned packages have been uploaded to Bionic and Eoan.
Xenial didn't change, and is still in the upload queue (which
I'll go check about on next week.)
Disco didn't change, and has been removed from the upload queue.
(After discussions with other people, it turns ou
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
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
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
** 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
** 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
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
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
** 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
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: "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
** 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)
+
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
@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
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
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
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
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
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
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
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
Verification successful with netboot image from bionic-proposed:
http://archive.ubuntu.com/ubuntu/dists/bionic-
proposed/main/installer-$ARCH/20101020ubuntu543.11/
Same testing as done on comment #8:
I have tested the installer with regular/lvm disk partition layouts
on amd64/i386/arm64/ppc64e
** 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/1836635
Title:
Bionic: support for Solarflare X2542 network adapter (sfc driver)
Status in debian-installer package in
** Patch added: "d-i_bionic_lp1836635.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/debian-installer/+bug/1836635/+attachment/5291161/+files/d-i_bionic_lp1836635.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Attaching debian-installer debdiff to update the kernel version
so that the netboot images include this driver update on Bionic.
The kernel version eventually settled on is 4.15.0-62 after bug
searching on versions after 4.15.0-58 (which releases this 'fix').
This builds correctly on all architec
Cosmic)
Status: New => Invalid
** Changed in: debian-installer (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: debian-installer (Ubuntu Bionic)
Status: New => In Progress
** Changed in: debian-installer (Ubuntu Bionic)
Assignee: (unassigned) => Mauricio
This fix is released for bionic and disco. Setting both as such.
For some reason the SRU machinery didn't pick it to this LP bug.
Bionic:
~/git/ubuntu-bionic$ git log --oneline origin/master -- drivers/md/bcache/ |
grep 'bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached'
474349a
This seems to cause bug 1844186 per the good/bad versions reported
(4.15.0-58 and -60) being the only mention to nnp in the changelog,
if I read it correctly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Apparently this seems to be introduced by bug 1839037,
which is related to nnp and the only mention to it in
the changelog of linux 4.15.0-60.67 [1] if read right.
[1] https://launchpad.net/ubuntu/+source/linux/4.15.0-60.67
--
You received this bug notification because you are a member of Kernel
Hi Matthew,
I was going through some kernel bugs and it looks this one has already been
released,
but just didn't get updated automatically as its LP number is not directly
mentioned
in the changelog.
Marking it as Fix Released.
Hope this helps!
cheers,
Mauricio
** Changed in: linux (Ubuntu B
Disco currently has the mpt3sas fix in disco-proposed (version 5.0.0-30.32),
also available as linux-hwe kernel in bionic-proposed.
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, w
301 - 400 of 718 matches
Mail list logo
