Bionic)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Status: Invalid
** Affects
** Description changed:
[Impact]
- * Support for Solarflare X2542 network adapter
-(Medford2 / SFC9250) in the sfc driver.
+ * Support for Solarflare X2542 network adapter
+ (Medford2 / SFC9250) in the sfc driver.
- * This network adapter is present on recent hardware,
-at le
[Bionic][PULL] sfc: patches for LP#1836635
https://lists.ubuntu.com/archives/kernel-team/2019-July/102196.html
--
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: suppo
Regression test results/log/script,
for documentation purposes.
** Attachment added: "lp1836635-test-regression.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836635/+attachment/5277232/+files/lp1836635-test-regression.tar.xz
--
You received this bug notification because you a
The documentation about the feature/parameters has been merged [1]
into Server Guide -> Installation -> Advanced Installaion -> iSCSI [2].
It's not yet published right now, so the HTML might be updated later.
cheers,
Mauricio
[1] https://code.launchpad.net/~mfo/serverguide/ibft/+merge/370264
[2]
The verification for bionic/cosmic -proposed is expected to finish by
tomorrow (Apr 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/1821395
Title:
fscache: jobs might hang when fscac
Verification successful with xfstests on nfs+fscache.
No regression in cosmic-proposed from cosmic-updates.
cosmic-updates / 4.18.0-17:
Failures: generic/035 generic/258 generic/294 generic/448 generic/467
generic/477 generic/484 generic/490 generic/495
Failed 9 of 437 tests
cosmic-proposed / 4
Verification successful with xfstests on nfs+fscache.
No regression in bionic-proposed from bionic-updates.
bionic-updates / 4.15.0-47:
Failures: generic/035 generic/075 generic/091 generic/112 generic/263
generic/294 generic/306 generic/307 generic/430 generic/431 generic/434
generic/469 gener
Regression testing setup/steps
===
fscache
---
sudo apt-get -y install cachefilesd
echo 'RUN=yes' | sudo tee -a /etc/default/cachefilesd
sudo modprobe fscache
sudo systemctl start cachefilesd
nfs
---
sudo apt-get -y install nfs-kernel-server
sudo systemctl start nfs-kernel-server
sudo mk
with the patch
for weeks and has not observed any other issues/regressions.
[Other Info]
* This is only required in Cosmic (for the Bionic HWE kernel),
and is already applied in Disco.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubunt
testcase, kernel part.
** Attachment added: "kprobe-test.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+attachment/5255994/+files/kprobe-test.c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
testcase, userspace part.
** Attachment added: "test.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+attachment/5255995/+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.launc
testcase
original kernel :: latest cosmic version:
$ uname -rv
4.18.0-18-generic #19-Ubuntu SMP Tue Apr 2 18:13:16 UTC 2019
[ 654.491029] kprobe_test: loading out-of-tree module taints kernel.
[ 654.493322] kprobe_test: module verification fail
testcase
test kernel :: latest cosmic version + patch:
$ uname -rv
4.18.0-18-generic #19+test20190415b1 SMP Mon Apr 15 15:43:20 UTC 2019
[ 169.145212] kprobe_test: loading out-of-tree module taints kernel.
[ 169.149144] kprobe_test: module
Patch posted for SRU:
[C][PATCH 0/1] Fix write()/fsync() deadlock in write_cache_pages()
https://lists.ubuntu.com/archives/kernel-team/2019-April/100084.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
The change introduced by the patch is evident in the kernel message log for
Thread 0:
between page indexes 2 and 1 there's now another function call to
write_cache_pages()
instead of just another iteration of the for-loop inside one call.
Original kernel:
[ 695.276320] Thread 0 running, TID = 3
Hi @mathew-hodson,
This fix is needed in the Linux kernel package for Xenial as well (it
duplicates the zfs-linux/dkms source).
Shouldn't the 'linux' source package still be tracked?
Thanks,
Mauricio
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Verification successful with disco-proposed.
No warning nor oops anymore.
# rmadison -s disco-proposed linux
linux | 5.0.0-26.27 | disco-proposed | source
# uname -rv
5.0.0-26-generic #27-Ubuntu SMP Tue Aug 13 17:47:39 UTC 2019
# ./setup-bcache-wb_percent-before-attach.sh >/dev/null 2>&1
[ 171
Verification done for 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
---
$ uname -rv
4.4.0-160-gene
ricio Faria de Oliveira (mfo)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Kern
Public bug reported:
Description/patches to be provided this week.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubu
Verification successful with bionic-proposed.
No warning nor oops anymore.
# uname -rv
4.15.0-59-generic #66-Ubuntu SMP Wed Aug 14 10:56:44 UTC 2019
# ./setup-bcache-wb_percent-before-attach.sh >/dev/null 2>&1
[ 105.696881] bcache: register_bdev() registered backing device loop0
[ 105.703809] b
ay into stable kernels
+(e.g., v5.2.8 which made Eoan/19.10 recently).
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Unde
For documentation purposes, in a recent Xenial/4.4 kernel,
this kernel error log is seen (with options to ignore the
hardware error/fault that panics/reboots the system).
[ 113.658876] bnx2x: [bnx2x_stats_comp:205(eno1)]timeout waiting for stats
finished
[ 123.648066] bnx2x: [bnx2x_state_wait:3
Somewhat similarly on recent 5.2 kernel without the fix.
(again with options to ignore hardware errors/faults)
Aug 19 17:15:15 HOSTNAME kernel: Uhhuh. NMI received for unknown reason 21 on
CPU 0.
Aug 19 17:15:15 HOSTNAME kernel: perf interrupt took too long (3222 > 2500),
lowering kernel.perf_ev
Older crashdump analysis confirmed the bnx2x driver/status
being in traffic class setup / stop hardware in LLDP path.
PID: 3936 TASK: 883fdc9b1c00 CPU: 11 COMMAND: "kworker/11:0"
#0 [883fec593ce0] __schedule at 81850bae
#1 [883fec593d30] schedule at 818510f5
#2 [
[X/B][PATCH] bnx2x: Disable multi-cos feature.
https://lists.ubuntu.com/archives/kernel-team/2019-August/103282.html
[D][PATCH] bnx2x: Disable multi-cos feature.
https://lists.ubuntu.com/archives/kernel-team/2019-August/103283.html
--
You received this bug notification because you are a member o
Hi Drew,
There's a mpt3sas fix in v5.3-rc3 for a problem that may cause an adapter
firmware fault
(although not sure of the exact fault state code; but it should cause a reset
anyway).
If you could please test either
1) v5.3-rc2 [1] to confirm the issue happens with v5.3-rc2 but not with
v5.3-
Mentioned upstream candidate fix is:
commit df9a606184bfdb5ae3ca9d226184e9489f5c24f7
Author: Suganath Prabu
Date: Tue Jul 30 03:43:57 2019 -0400
scsi: mpt3sas: Use 63-bit DMA addressing on SAS35 HBA
Although SAS3 & SAS3.5 IT HBA controllers support 64-bit DMA addressing, as
pe
Hi Martin,
There's a potential fix for this upstream, in v5.3-rc1 mainline build (thus not
in v5.2),
which is also applied to bionic-proposed (4.15.0-60.67).
Could you please test whether the issue is resolved with bionic-proposed
[1] ?
If that doesn't help, further regression/bisect test steps
Hi Drew,
That's very good news! So it looks like that patch resolves the
problem.
Could you please test the kernel in bionic-proposed [1] (4.15.0-60-generic)
which has that patch to confirm it's also working correctly?
Thanks!
Mauricio
[1] https://wiki.ubuntu.com/Testing/EnableProposed
--
Yo
Drew,
Thanks for testing bionic-proposed!
So it will be resolved for bionic kernels shortly, when it hit bionic-updates.
Disco/19.04 will get this patch via stable updates in the near future
[1].
Eoan has it applied (LP: #1839588).
So this is all good.
Thanks again,
Mauricio
[1] https://lists
** Changed in: linux (Ubuntu Eoan)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Pa
** Description changed:
The ZFS kernel modules aren't built with debug symbols,
which introduces problems/issues for debugging/support.
- Patches will be sent soon for linux and zfs/spl-linux,
- covering X/B/D/E/Unstable.
+ Patches are required in:
+ 1) linux kernel packaging, to add infras
Test Build 1) Old behavior
goal: show limitations/issues.
- original packaging
- zfs not built with debug symbols
- zfs modules not present in debug package
- extra modules lack .gnu_debuglink section
Original packaging:
There are no ZFS modules in the debug package:
$ dpkg-deb -x linu
Test Build 4) All debug symbols disabled
goal: show no zfs debug symbol activity happens either (along w/ other
debug symbol stuff)
- test packaging
- nothing built with debug symbols
- no debug package present
- no .gnu_debuglink section at all
- (no regressions)
Test packaging, debug symbols
Test Build 2) New behavior if ZFS modules are *not* built with debug
symbols
goal: show failsafe/backwards compatible behavior if zfs-dksm doesn't
support/build debug symbols
and kernel build log reports missing debug symbols, and extra modules
have .gnu_debuglink.
- test packaging
- zfs
Test Build 3) New behavior if ZFS modules are built with debug symbols
goal: show zfs debug symbols are correctly built and packaged into non-
debug & debug packages.
- test packaging
- zfs built with debug symbols
- zfs modules present in debug package
- extra modules *have* .gnu_debuglink secti
[Unstable][PATCH 0/6] Add support for ZFS debug symbols
https://lists.ubuntu.com/archives/kernel-team/2019-August/103425.html
--
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/1840704
Title:
Hi Martijn,
Thanks for testing bionic-proposed!
So it will be resolved for bionic kernels shortly, when it hit bionic-updates.
Disco/19.04 will get this patch via stable updates in the near future
[1].
Eoan has it applied (LP: #1837725).
So this is all good.
Thanks again,
Mauricio
** Also aff
Attaching the debdiffs for zfs-linux/spl-linux on X/B/D/E,
for documentation purposes; will send testing/notes later.
Independently of the kernel packaging approach determined
to enable debug symbols on ZFS/SPL modules, these kind of
patches for the userspace packages are be required anyway,
and c
Marking status on B/X/D as Incomplete.
(email below sent to kernel-team mailing list
as replies to both patch series above).
Please hold / don't apply this patch for now.
The reporter hit an apparently unrelated Oops in 3 of 40 nodes,
and it hasn't been possible yet to determine whether this pat
** Description changed:
[Impact]
- * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
-(settings for network interface, initiator, and target) in the installer
-because the 'iscsi_ibft' module is not present in udeb packages.
+ * It's not possible to access i
** Changed in: linux (Ubuntu)
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/1829563
Title:
[4.15] bcache device
** Patch added: "bionic_d-i.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265731/+files/bionic_d-i.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Test Procedure with KVM guests + iPXE
=
- 2 guests: iSCSI target/server and iSCSI initiator/client.
- 1 bridge for iSCSI traffic (virbr-iscsi, new), static ip.
- 1 bridge for internet access (virbr0, exists), dhcp ip.
Host:
Configure the iSCSI bridge an
Test procedure for the partman-iscsi changes
Based on the previous comment setup.
iSCSI initiator:
---
...
Note there's no 'iscsi_auto' in the kernel cmdline:
iPXE> ifopen net0
iPXE> kernel http://192.168.122.1:8000/vmlinuz ini
** Patch added: "cosmic_d-i.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265734/+files/cosmic_d-i.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
** Patch added: "bionic_hw-detect.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265732/+files/bionic_hw-detect.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Adding patches and test procedure for the debian-installer userspace part.
(disk-detect probes iSCSI iBFT disks; partman-iscsi sets ISCSI_AUTO=true for
booting.)
The d-i patches should be uploaded/built _after_ hw-detect and partman-iscsi
are successfully built and published, so that its new vers
** Patch added: "cosmic_hw-detect.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265735/+files/cosmic_hw-detect.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
** Patch added: "disco_d-i.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265737/+files/disco_d-i.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
** Patch added: "cosmic_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265736/+files/cosmic_partman-iscsi.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Patch added: "disco_hw-detect.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265738/+files/disco_hw-detect.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Patch added: "eoan_d-i.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265740/+files/eoan_d-i.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
** Patch added: "eoan_hw-detect.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265741/+files/eoan_hw-detect.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
** Patch added: "disco_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265739/+files/disco_partman-iscsi.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Patch added: "eoan_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265742/+files/eoan_partman-iscsi.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: "bionic_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265733/+files/bionic_partman-iscsi.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
e: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Fix Released
** Also affects: partman-iscsi (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: debian-installer (Ubuntu Bi
Installer (non-kernel) patches submitted to Debian for feedback.
- disk-detect: https://bugs.debian.org/924675
- partman-iscsi: https://bugs.debian.org/924680
** Bug watch added: Debian Bug tracker #924675
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924675
** Bug watch added: Debian Bug
Hi Marius @lazamarius1,
Per the kernel.ubuntu.com schedule, the version for Bionic/linux ->
Xenial/linux-hwe should land soon.
You can verify the version/timestamps for each package/release at the bottom of
these pages
(the linux-hwe version comes a bit after the corresponding linux version)
ht
@lazamarius1,
Actually linux-hwe for Bionic with this fix has just been uploaded.
See in https://launchpad.net/ubuntu/+source/linux-hwe
Changelog
linux-hwe (4.15.0-47.50~16.04.1) xenial; urgency=medium
...
* [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() (LP: #1802021)
- srcu
cosmic-proposed verification done;
iscsi_ibft.ko is present in udeb and loads correctly.
---
$ uname -rv
4.18.0-17-generic #18-Ubuntu SMP Wed Mar 13 14:34:40 UTC 2019
$ apt-get download scsi-modules-4.18.0-17-generic-di
$ dpkg-deb -c scsi-modules-4.18.0-17-generic-di_4.18.0-17.18_amd64.udeb | gr
bionic-proposed verification done;
iscsi_ibft.ko is present in udeb and loads correctly.
---
$ uname -rv
4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019
$ apt-get download scsi-modules-4.15.0-47-generic-di
$ dpkg-deb -c scsi-modules-4.15.0-47-generic-di_4.15.0-47.50_amd64.udeb | gr
Public bug reported:
[Impact]
* This problem hard locks up 2 CPUs in a deadlock, and this
soft locks up other CPUs as an effect; the system becomes
unusable.
* This is relatively rare / difficult to hit because it's a
corner case in scheduling/load balancing that needs timing
with
Analysis
The 1st hard lockup is harder to get the interesting data out of, as apparently
the registers with variables
related to the cpu number have been clobbered by more recent calls in the
spinlock path.
Looking at the 2nd hard lockup:
addr2line + code shows us that try_to_wake_up(
--
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/1821259
Title:
Hard lockup in 2 CPUs due to deadlock in cpu_stoppers
Status in linux package in Ubuntu:
Incomplete
Bug description:
[I
Test-case (kmod-stopper.c)
-
$ sudo apt-get -y install gcc make libelf-dev linux-headers-$(uname -r)
$ touch Makefile # fake it, and use this make line:
$ make -C /lib/modules/$(uname -r)/build M=$(pwd) obj-m=kmod-stopper.o modules
$ echo 9 | sudo tee /proc/sys/kernel/printk
$ sudo insm
Test-case on Xenial;
$ ls -1d /sys/devices/system/cpu/cpu[0-9]*
/sys/devices/system/cpu/cpu0
/sys/devices/system/cpu/cpu1
Original
$ uname -rv
4.4.0-144-generic #170-Ubuntu SMP Thu Mar 14 11:56:20 UTC 2019
$ sudo insmod kmod-stopper/kmod-stopper.ko
[ 74.198379] mod_init() :: this cp
Both xenial and bionic original/patched kernels
were tested with stress-ng scheduler class, and
no regressions were observed.
$ stress-ng --version
stress-ng, version 0.09.56 (gcc 8.3, x86_64 Linux 4.15.0-47-generic) 💻🔥
$ sudo stress-ng --class scheduler --sequential 0
$ uname -rv
4.4.0-144-gene
Since Bionic already has the fix commit applied,
the original kernel version doesn't hit the problem.
--
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/1821259
Title:
Hard lockup in 2 CPUs
[X][PATCH 0/4] LP#1821259 Fix for deadlock in cpu_stopper
https://lists.ubuntu.com/archives/kernel-team/2019-March/099427.html
[B][PATCH 0/2] Fix for LP#1821259 (pending patches for) Fix for deadlock in
cpu_stopper
https://lists.ubuntu.com/archives/kernel-team/2019-March/099432.html
** Also affe
Public bug reported:
< NOTE: patches will be sent to kernel-team mailing list. >
[Impact]
* fscache issue where jobs get hung when fscache disk is full.
* trivial upstream fix; already applied in X/D, required in B/C:
commit c5a94f434c82 ("fscache: fix race between enablement and
droppi
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => Conf
[B/C][PATCH 0/1] Fix for LP#1821395 (fscache: jobs might hang when fscache disk
is full)
https://lists.ubuntu.com/archives/kernel-team/2019-March/099448.html
** Description changed:
- < NOTE: patches will be sent to kernel-team mailing list. >
-
[Impact]
- * fscache issue where jobs get h
Updating bug tags to verification done.
As mentioned by users in this LP bug, the verification period of 5 days
is _usually_ not enough to reproduce this problem, however, we have some
datapoints that support the fix is good.
1) The fix has been first delivery in linux-azure, 3 weeks ago, and has
Marking X/B as verification done.
The user reports the issue occurs much less often now.
Apparently that environment hits some corner case or this may still be expected
sometimes under memory pressure (i.e., one big shrinking operation acquired the
lock and must finish).
Nonetheless, the fix re
** Patch added: "cosmic_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5267256/+files/cosmic_partman-iscsi.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Patch removed: "bionic_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5265733/+files/bionic_partman-iscsi.debdiff
** Patch removed: "cosmic_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/52
** Patch added: "eoan_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5267258/+files/eoan_partman-iscsi.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Hi Eric,
Nice catch. Sorry about that!
Sure, just attached the partman-iscsi debdiffs with the LP bug mentioned
in changelog.
Thanks,
Mauricio
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
** Patch added: "disco_partman-iscsi.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+attachment/5267257/+files/disco_partman-iscsi.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
Dan, thanks for the review/fixes/upload!
--
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/1817321
Title:
installer does not support iSCSI iBFT
Status in debian-installer package in Ubuntu
verification done for disco/hw-detect.
disk-detect found the iscsi target/lun configured in ibft.
$ wget http://boot.ipxe.org/ipxe.lkrn
$ wget
http://archive.ubuntu.com/ubuntu/dists/disco/main/installer-amd64/20101020ubuntu570/images/netboot/ubuntu-installer/amd64/{linux,initrd.gz}
$ python3 -m
verification done for cosmic/hw-detect.
disk-detect found the iscsi target/lun configured in ibft.
cosmic currently needed the workaround to download/install
the iscsi_ibft.ko module, because the d-i changes are not
yet in (update to kernel version to includes it in scsi-modules.udeb).
$ wget ht
verification done for bionic/hw-detect.
disk-detect found the iscsi target/lun configured in ibft.
bionic currently needed the workaround to download/install
the iscsi_ibft.ko module, because the d-i changes are not
yet in (update to kernel version that includes it in scsi-modules.udeb).
$ wget
verification done for disco/partman-iscsi.
Use of partman-iscsi/iscsi_auto correctly writes /etc/iscsi/iscsi.initramfs
with either ISCSI_AUTO=true or iSCSI LUN details with the right MAC address.
~ # grep 'retrieving partman-iscsi' /var/log/syslog
Jun 6 14:04:03 anna[1582]: DEBUG
verification done for cosmic/partman-iscsi.
Use of partman-iscsi/iscsi_auto correctly writes /etc/iscsi/iscsi.initramfs
with either ISCSI_AUTO=true or iSCSI LUN details with the right MAC address.
~ # grep 'retrieving partman-iscsi' /var/log/syslog
Jun 6 14:20:51 anna[1521]: DEBU
verification done for bionic/partman-iscsi.
Use of partman-iscsi/iscsi_auto correctly writes /etc/iscsi/iscsi.initramfs
with either ISCSI_AUTO=true or iSCSI LUN details with the right MAC address.
~ # grep 'retrieving partman-iscsi' /var/log/syslog
Jun 6 15:01:20 anna[1605]: DEB
Verified debian-installer in {disco,cosmic,bionic}-proposed.
The verification has been done with the netboot image files
for disco/cosmic/bionic (and hwe-netboot for bionic),
using regular and lvm partitioning,
on VMs for the architectures amd64/i386/arm64/ppc64el
and baremetal for amd64.
All tes
** Attachment added: "kprobe-test.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+attachment/5259304/+files/kprobe-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
Verification successful on Cosmic.
Updated the test-case kernel part (attached), and repeated it 20+ times,
without any process hanging.
In all cases, the new function call into write_cache_pages() is observed
in thread 0, between page index 2 and page index 1.
[ 150.914872] mod_init():161 :: h
Tested with disco-proposed + patch (problem does not happen)
---
# uname -rv
5.0.0-22-generic #23+test20190725b1 SMP Mon Jul 29 14:43:55 -03 2019
# ./setup-bcache-wb_percent-before-attach.sh >/dev/null 2>&1
[ 69.567775] bcache: register_bdev() registered backing device loop0/null
2>&1
[ 69.
Attaching test-case script.
** Attachment added: "setup-bcache-wb_percent-before-attach.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837788/+attachment/5279850/+files/setup-bcache-wb_percent-before-attach.sh
--
You received this bug notification because you are a member of Kerne
Patches sent to the kernel-team mailing list:
[B][PATCH] bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached
https://lists.ubuntu.com/archives/kernel-team/2019-July/102653.html
[D][PATCH] bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached
https://lists.ubuntu.com/ar
Regression testing done on an older/previously supported adapter, SFC
7000 series.
The netperf suite of TCP/UDP STREAM and RR, and TCP_RR ran for ~2 days,
with results in the same ballpark as the original kernel and test kernels.
Now waiting for test results with the new/requested adapter
before
Verification with bionic-proposed of the I/O Error path.
All good, working as expected (see comments #11 to #16).
# uname -rv
4.15.0-56-generic #62-Ubuntu SMP Wed Jul 24 20:18:55 UTC 2019
test 1
--
# ./setup.sh >/dev/null 2>&1
[ 369.375820] bcache: register_bdev() registered backing devic
Verification done for Disco (one patch change only).
Only one of the two bcache devices stop working upon failures in one backing
device.
(see comment #21 for details).
# uname -rv
5.0.0-22-generic #23-Ubuntu SMP Tue Jul 23 17:23:54 UTC 2019
# ./setup-two-bcache-one-cache.sh >/dev/null 2>&1
[
Verification with bionic-proposed of xfstests results.
No regressions introduced by this bcache patchset.
The comparison between -updates and -proposed is not directly possible
because -proposed introduced failures via other components in I/O path
(e.g., block, ext4).
This is described below, an
1 - 100 of 727 matches
Mail list logo
