Thanks for the update on this compat fix.
I've tested this on:
upstream 5.6-rc5 lowlatency + generic
upstream 5.5 lowlatency + generic
ubuntu 5.4.0-18
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are
Can this be re-tested to see if this now fails after I cleaned up
kernel03?
--
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/1863989
Title:
bad-altstack test from ubuntu_stress_smoke_test
The Ubuntu kernel team recommends to have at least 4GB of free memory to
run ZFS on slow backing store devices for nominal performance. Since
there is OS overhead (kernel, userspace processes etc) a 4GB Raspberry
Pi will perform sub-optimally. Note that the document you referenced in
commet #1
I found this was failing on kernel03 because there was very little space
for the test to enable a large swap file. I cleaned the machine up and
was unable to reproduce the failure. I'm assuming the tests were failing
on kernel03, if not what machine were they being run on?
--
You received this
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are
I've uploaded a fixed package, it's now going to proceed via the normal
SRU process.
--
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/bugs/1860182
Title:
zpool scrub malfunction after
** Description changed:
+ == SRU Request [BIONIC] ==
+
+ The HWE kernel on bionic provides zfs 0.8.1 driver which includes an
+ improved scrub however, the progress stats reported by the kernel are
+ incompatible to the 0.7.x zfs driver.
+
+ == Fix ==
+
+ Use the new zfs 8.x pool_scan_stat_t
Hi Ryan,
We would like to reproduce this bug to debug it further. Can you answer
the questions below relating to your initial comments in the bug:
"Booting some Bionic instances in Azure (gen1 machines).."
Q: What is a gen1 machine? What instance type is this?
"..I see some large delays during
Fix Committed
** Changed in: stress-ng
Status: New => Invalid
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
@Sam. Can you re-run the test and if it's OK then I no longer require
the instance kernel03.
--
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/1863989
Title:
bad-altstack test from
** Changed in: stress-ng
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: stress-ng
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
I confirm in my testing I get a hard kernel lockup with no log output.
--
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/1864063
Title:
vm-segv from ubuntu_stress_smoke_test failed on B
Please ignore the above. Apparently the issue needs a little more
digging and the workaround is insufficient.
--
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/bugs/1861235
Title:
zfs recv
ntu)
Status: New => Incomplete
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affect
** Changed in: stress-ng
Assignee: Colin Ian King (colin-king) => Kleber Sacilotto de Souza
(kleber-souza)
--
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/1864063
Title:
vm-s
To reproduce (on an 8 CPU VM):
sudo apt-get update && sudo apt-get dist-upgrade
sudo apt-get build-dep stress-ng
git clone git://kernel.ubuntu.com/cking/stress-ng
cd stress-ng
make
sudo ./stress-ng --vm-segv 0 -t 10 -v
Comment out a ptrace line and rebuild and re-run and the hang does not
occur.
I spoke too soon. I was able to trip this 4.15.0-89.89 but not
4.15.0-88. So this looks like a regression.
--
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/1864063
Title:
vm-segv from
I can't reproduce this on the systems I'm using. Can I get access to
onibi to try and reproduce this issue?
** Changed in: stress-ng
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
-ng
Importance: Undecided => Medium
** Changed in: stress-ng
Assignee: (unassigned) => Colin Ian King (colin-king)
--
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/1864063
Title:
vm-
What is interesting is the following commit modifies range_tree_clear()
so it performs a zero size check and returns before calling
range_tree_find_impl(). This commit is not in 18.10 and 19.04 Ubuntu ZFS
releases.
commit a1d477c
Author: Matthew Ahrens mahr...@delphix.com
Date: Thu Sep 22
** Changed in: zfs-linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: spl-linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Unfortunately we require some more 5.6 compat fixes as 5.6-rc3 fails to
build with the current 2 compat upstream fixes:
make[3]: Entering directory '/usr/src/linux-headers-5.6.0-050600rc3-generic'
CC [M] /var/lib/dkms/zfs/0.8.3/build/module/avl/avl.o
CC [M]
Soak tested the -proposed kernel for 2 hours with no hang occurring.
Verified OK.
** 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.
.
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Status: In
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
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/1832384
Title:
Unable to unmount apparently unused filesystem
@John, I was wondering what to do about this bug report. Is it still an
issue or shall I close it?
--
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/1832384
Title:
Unable to unmount
AppleTalk is disabled on focal s390x 5.4.0-12 kernels so this bug cannot
be tripped. Marking this as fixed released even though it's not a direct
fix, it does stop the issue.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you
Just to say, I did retry the reproducer test and also re-ran the adt
tests to double check that this no longer fails on 5.4.0-12.
--
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/1854968
@Finom, that's a good observation, much appreciated.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Description changed:
- Description: In the event a particular Azure cloud
..and on a power9 box too. Marking as fix committed for 5.4.0-12
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've re-run this on a power8 VM with 5.4.0-12 and cannot trigger this
failure.
--
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/1855100
Title:
bpf self tests break 5.4.0-7-generic on
*** This bug is a duplicate of bug 1861235 ***
https://bugs.launchpad.net/bugs/1861235
** Bug watch added: Github Issue Tracker for ZFS #8637
https://github.com/zfsonlinux/zfs/issues/8637
** Also affects: linux via
https://github.com/zfsonlinux/zfs/issues/8637
Importance: Unknown
Can you describe the zfs environment and the command that was being
actioned that triggered this issue?
** Bug watch added: Github Issue Tracker for ZFS #8637
https://github.com/zfsonlinux/zfs/issues/8637
** Also affects: linux via
https://github.com/zfsonlinux/zfs/issues/8637
** Changed in: linux-signed-azure (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-signed-azure (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-azure in Ubuntu.
Tested these updates with the kernel team ZFS autotest regression tests
on the following architectures:
arm64 - PASSED
amd64 - PASSED
s390x - PASSED
ppc64el - PASSED
I re-ran the failed lxd test as referenced in comment #5 and it passed,
so I believe the original failure was an artifact of the
OK, I'll look into this sometime this week. Thanks for the information.
** Changed in: zfs-linux (Ubuntu)
Importance: Medium => High
** Changed in: zfs-linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: zfs-linux (Ubuntu)
Importance: High => Medium
--
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/bugs/1860182
Title:
zpool scrub malfunction after kernel upgrade
Status in
Cornered this to zswap and not an issue with mm or I/O. Figured out
that 3 hours soak testing on each bisect step is the only reliably way
to do a bisect. Bisected between 4.20 and 5.0 finally cornered the
issue and hence the commits required to fix this.
** Description changed:
+ == SRU
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Critical
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Running w/o swapfile and zswap and just stress-ng brk and stack
stressors with NO file I/O can also lock the system.
--
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/1799497
Title:
4.15
Couple more notes:
1. Disable file based swap on /swapfile - can reproduce issue
2. Use partition based swap on 2nd disk - can reproduce issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member
Captured the hard lock on the following
(gdb) stepi
0x8c4e29e5 in ?? ()
=> 0x8c4e29e5: eb ec jmp0x8c4e29d3
(gdb) stepi
0x8c4e29d3 in ?? ()
=> 0x8c4e29d3: 8b 07 mov(%rdi),%eax
(gdb) stepi
0x8c4e29d5 in ?? ()
=> 0x8c4e29d5: 85
Dann, tested on my 6640 on an older kernel, now get:
sudo dmidecode
# dmidecode 3.1
# No SMBIOS nor DMI entry point found, sorry.
I guess that's expected.
I'd like to see what Ethan gets on his H/W as I'm not running a cloud
installation on my dev board.
--
You received this bug notification
It needs backporting to eoan, disco bionic, I was just about to upload a
fix to my ppa so I could get it sponsored. Do you want to take it from
here Dann?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: dmidecode (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1
I guess the next question is why dmidecode being run as root is required
on a cloud init? What happens when arches don't have DMI data?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
Assignee: Colin Ian King (colin-king) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1858615
Title:
dmidecode triggers system reboot on Inforce 6640
Sta
So, dmidecode directly mmap's to /dev/mem and does some probing based on
the belief that the system is a x86 architecture even on arm
architectures.
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3, {st_mode=S_IFCHR|0640, st_rdev=makedev(0x1, 0x1), ...}) = 0
mmap(NULL, 65536, PROT_READ,
@ubuntu stable folks - can this be uploaded sometime soon?
--
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/bugs/1856704
Title:
backport 5.3 zfs support to bionic for HWE kernel support
Hi, can you provide me instructions on how to get and install the image
for this board? I'd like to reproduce this issue and get a suitable fix
for this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
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/1855100
Title:
bpf self tests break 5.4.
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are
** Description changed:
- 5.3 kernel functionality back through to 4.15 is required for 5.3 HWE
- kernel support in ZFS and SPL modules.
+ == SRU Justification Bionic ==
+
+ The HWE 5.3 kernel requires ZFS + SPL to support dkms module build
+ functionality for kernels 4.15 through to 5.3.
** Changed in: spl-linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: spl-linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: zfs-linux (Ubuntu Bionic)
> High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
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/1857040
Title:
zfs: upst
After quite a bit of experimentation I found that I can reproduce the bug if I
have zram *and* also swap on the filesystem enabled while exercising the brk
stressors and aiol (to cause lots of I/O). Eventually the system grinds to a
halt, we lose interactivity and we eventually get lockups as
** Changed in: linux-signed-azure (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1858495
Title:
multi
Oh, stupid me, I've just read the info in comment #1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1858615
Title:
dmidecode triggers system reboot on Inforce 6640
Status in
see if it's a broken firmware DMI table
or a kernel issue.
** Changed in: dmidecode (Ubuntu)
Status: New => Triaged
** Changed in: dmidecode (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: dmidecode (Ubuntu)
Importance: Undecided => Medium
--
Can reproduce this with stress-ng exercising high memory pressure scenario
using:
stress-ng --brk 0 -v --aiol 0
--
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/1799497
Title:
4.15
Can reproduce this with stress-ng exercising high memory pressure scenario
using:
stress-ng --brk 0 -v --aiol 0
--
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/1799497
Title:
4.15
I'm assuming the defaults are being used for the moment, this means 50%
of total memory being used in total distributed across the number of
CPUs, as defined in /usr/bin/init-zram-swapping
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
It would be useful to know if one has made any specific zram config
changes, and if so, what your current config is just to help with the
debugging of this issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: zram-config (Ubuntu)
Status: Confirmed =>
I'll get a kernel sorted out for testing by EOD.
--
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/1853044
Title:
5.3.0-23-generic causes fans to spin when idle
Status in linux package in
The next spin of the focal kernel will pick this up when it is built
with the new zfs-dkms driver.
--
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/1857040
Title:
zfs: upstream support
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
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/1799497
Title:
4.15 kernel hard lockup about o
Also should apply:
commit 10fa254539ec41c6b043785d4e7ab34bce383b9f
Author: Brian Behlendorf
Date: Thu Oct 24 10:17:33 2019 -0700
Linux 4.14, 4.19, 5.0+ compat: SIMD save/restore
but this also requires a rather tricky backport of:
commit 006e9a40882468be68f276c946bae812b74ac35c
Author:
ZFS kernel modules are not supported for small memory ARM platforms such
as raspberry pi as it requires at least 4GB of memory to perform without
causing memory pressure issues.
** Changed in: zfs-linux (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
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/1857040
Title:
zfs: upstream support for hardware-accelerated
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I believe this is because a FUSE based file system is being used in the
prior ADT testing and sysinfo is breaking on the FUSE filesystem, so it
may be a problem with with the fuse fs itself or the fuse file system
that is using the kernel fuse core.
--
You received this bug notification because
: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
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/1856900
Title:
stress-ng s
Public bug reported:
5.3 kernel functionality back through to 4.15 is required for 5.3 HWE
kernel support in ZFS and SPL modules.
** Affects: spl-linux (Ubuntu)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Affects: zfs-linux (Ubuntu
I've tested zfs from the -proposed pockets with the ubuntu ZFS autotest
regression tests:
ubuntu_zfs_fstest
ubuntu_zfs_smoke_test
ubuntu_zfs_stress
ubuntu_zfs_xfs_generic
All the following passed the regression testing.
bionic: 0.7.5-1ubuntu16.7
disco: 0.7.12-1ubuntu5.1
eoan:
*I was unable to trip any lockups
** Tags added: verification-done-bionic verification-done-disco
verification-done-eoan
--
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/bugs/1856084
Title:
I've checked that the zfs kernel driver builds and it passes the ZFS
regression tests. Patches look good, so I've uploaded these packages.
** Changed in: zfs-linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu Disco)
Importance: Undecided => Medium
**
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
--
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/bugs/1856084
Title:
Livelock between ZFS evict and writeback threads
Tested with 5.3.0-25-generic #27-Ubuntu with the regression test and it
now works fine. Marking bug as verification-done for eoan
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu)
Importance: High => Low
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
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/1854968
Title:
Indeed, the commit is in in 4.15.0-1057 and has been released. Marking
this bug as fixed released.
commit b502cfeffec81be8564189e5498fd3f252b27900
Author: Taehee Yoo
Date: Wed Sep 4 14:40:49 2019 -0300
ip: frags: fix crash in ip_do_fragment()
BugLink:
*** This bug is a duplicate of bug 1854968 ***
https://bugs.launchpad.net/bugs/1854968
Same root corruption issue as bug 1854968
** This bug has been marked a duplicate of bug 1854968
stress-ng sctp stressor breaks 5.4.0.7-8 on s390x
--
You received this bug notification because you
*** This bug is a duplicate of bug 1854968 ***
https://bugs.launchpad.net/bugs/1854968
Same root issue as bug 1854968
** This bug has been marked a duplicate of bug 1854968
stress-ng sctp stressor breaks 5.4.0.7-8 on s390x
--
You received this bug notification because you are a member
Hrm, I can't see the fix in the Ubuntu-5.3.0-24.26 kernel, so I think
comment #34 a premature SRU test request. As it stands, I tested
Ubuntu-5.3.0-24.26 and the issue still exists, and looking at the source
the fix isn't present so that correlates with my test observations.
--
You received this
See: https://lkml.org/lkml/2019/12/5/476
--
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/1854968
Title:
stress-ng sctp stressor breaks 5.4.0.7-8 on s390x
Status in linux package in
This goes right back to 4.6.x:
.6.7 crash (see below)
4.7.10 crash in xfrm6_dst_ifdown
4.8.17 crash in xfrm6_dst_ifdown
4.12.14 crash (see below)
4.13.16 reports "unregister_netdevice: waiting for eth0 to become free. Usage
count = 2"
4.14.157 reports "unregister_netdevice: waiting for eth0 to
Ah, fails on 5.2.0-15-generic, 5.3.0-18 generic too. Appears that the
regression test was enabled quite recently:
commit b5b9181c2403025b2c7ae7ea44333fd8fe6dbb54 (between 5.4-rc3 and 5.4-rc4)
Author: David Ahern
Date: Mon Oct 21 19:02:43 2019 -0600
selftests: Make l2tp.sh executable
Occurs between 5.3 and 5.4-rc1
--
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/1854968
Title:
stress-ng sctp stressor breaks 5.4.0.7-8 on s390x
Status in linux package in Ubuntu:
Easy steps to reproduce this issue:
sudo modprobe l2tp_core
sudo ./linux-5.4.0/tools/testing/selftests/net/l2tp.sh
./close
where close is compiled from:
#include
#include
#include
#include
int main()
{
int fd;
printf("calling socket..\n");
fd = socket(AF_APPLETALK,
The unregister_netdevice issue occurs running the kernel self test in
testing/selftests/net/l2tp.sh after modprobing the l2tp driver. A hang
can be the produced by running the stress-ng close stressor, this is
just expediting an eventual hang caused by this test.
--
You received this bug
17:59:24 DEBUG| [stdout] # send cpu 63, receive socket 63
17:59:24 DEBUG| [stdout] # send cpu 65, receive socket 65
17:59:24 DEBUG| [stdout] # send cpu 67, receive socket 67
17:59:24 DEBUG| [stdout] # send cpu 69, receive socket 69
17:59:24 DEBUG| [stdout] # send cpu 71, receive socket 71
17:59:24
I added a background task to dump out new dmesg messages and I now see
messages such as the following *before* any stress-ng tests run. I think
we can therefore assume the damage to the kernel occurred in prior ADT
tests.
11:02:46 DEBUG| [stdout] [ 3093.210307] unregister_netdevice: waiting
for
this. I'll re-run this with
the ipmi tool on the console to see if I can see how far it got before
the kernel panic'd.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned
Colin Ian King (colin-king)
--
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/1855143
Title:
5.4.0-7 kernel crash on boot on power box
Status in linux package in Ubuntu:
Invalid
Bug descr
Public bug reported:
boot failures with 5.4.0-7-generic on OPAL power box:
I was running ADT tests and the machine hung/rebooted. I was unable to
log in. After I rebooted the machine with the ipmi tool the machine
crashed with the following kernel output:
[ 51.081421774,5] SkiBoot
Public bug reported:
Running ADT tests on POWER8 5.4.0-7-generic (gulpin) causes reboot of
the bare metal system.
Last output seen while ssh'd into the box:
11:52:34 DEBUG| [stdout] ok 6 selftests: net: tls
11:52:34 DEBUG| [stdout] # selftests: net: run_netsocktests
11:52:34 DEBUG| [stdout] #
Verified for disco:
Run reproducer script with old kernel: 5.0.0-37-generic, results:
cat /root-tmp/etc/.pwd.lock
cat: /root-tmp/etc/.pwd.lock: Input/output error
Run with -proposed kernel: 5.0.0-38-generic
cat /root-tmp/etc/.pwd.lock
foo
Marking as verification-done-disco
** Tags removed:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
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/1854968
Title:
stress-ng sctp stressor bre
701 - 800 of 2248 matches
Mail list logo
