[Bug 282424] [NEW] ssmtp dies with standardise() -- Buffer overflow
Public bug reported:
Binary package hint: ssmtp
A line which begins with a period ('.') and is BUZ_SZ - 1 (e.g. 2047) or
longer in length (not counting \n) will die() with:
ssmtp: standardise() -- Buffer overflow
This is a specific case. The general case is if a buffer passed into
standardise() begins with a period and is BUF_SZ - 1 bytes in length
will produce this error.
I think the fix is to call fgets() with sizeof(buf) - 2 instead of
sizeof(buf) in ssmtp().
With this fix another problem is that in the sent e-mail the line is
truncated by two bytes. The fix is to use (BUF_SZ) in smtp_write()
instead of (BUF_SZ - 2).
Index: ssmtp.c
===
--- ssmtp.c (revision 57)
+++ ssmtp.c (working copy)
@@ -1361,7 +1361,7 @@
ssize_t outbytes = 0;
va_start(ap, format);
- if(vsnprintf(buf, (BUF_SZ - 2), format, ap) == -1) {
+ if(vsnprintf(buf, BUF_SZ, format, ap) == -1) {
die("smtp_write() -- vsnprintf() failed");
}
va_end(ap);
@@ -1628,7 +1628,7 @@
/* don't hang forever when reading from stdin */
while(!feof(stdin) && timeout < MEDWAIT) {
- if (!fgets(buf, sizeof(buf), stdin)) {
+ if (!fgets(buf, sizeof(buf)-2, stdin)) {
/* if nothing was received, then no transmission
* over smtp should be done */
sleep(1);
** Affects: ssmtp (Ubuntu)
Importance: Undecided
Status: New
--
ssmtp dies with standardise() -- Buffer overflow
https://bugs.launchpad.net/bugs/282424
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282424] Re: ssmtp dies with standardise() -- Buffer overflow
** Attachment added: "Demonstrate that a buffer passed into standardise() which begins with a period and is BUF_SZ - 1 bytes in length will die()" http://launchpadlibrarian.net/18474661/test_case.001 -- ssmtp dies with standardise() -- Buffer overflow https://bugs.launchpad.net/bugs/282424 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282424] Re: ssmtp dies with standardise() -- Buffer overflow
I mislabaled test_cast.001. The correct description should be: Demonstrate that a line which is BUZ_SZ - 1 in length (not counting \n) beginning with a period will die(). -- ssmtp dies with standardise() -- Buffer overflow https://bugs.launchpad.net/bugs/282424 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282424] Re: ssmtp dies with standardise() -- Buffer overflow
** Attachment added: "Demonstrate that a buffer passed into standardise() which begins with a period and is BUF_SZ - 1 bytes in length will die()" http://launchpadlibrarian.net/18474874/test_case.002 -- ssmtp dies with standardise() -- Buffer overflow https://bugs.launchpad.net/bugs/282424 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282424] Re: ssmtp dies with standardise() -- Buffer overflow
** Attachment added: "Verification" http://launchpadlibrarian.net/18474878/test_case.003 -- ssmtp dies with standardise() -- Buffer overflow https://bugs.launchpad.net/bugs/282424 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282424] Re: ssmtp dies with standardise() -- Buffer overflow
The fix for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498366 does not address this bug. ** Changed in: ssmtp (Ubuntu) Status: Fix Released => Incomplete -- ssmtp dies with standardise() -- Buffer overflow https://bugs.launchpad.net/bugs/282424 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818049] Re: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]
Verified that this installed successfully (i.e. no DKMS build failures) on trusty for both -142 and -143 kernels. virtualbox-lts-xenial 4.3.40-dfsg-0ubuntu1.14.04.1~14.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818049 Title: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1818049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
A buddy asked me to add that he's also unable to build - Trusty (14.04.5). ... ld -r -o /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-modeset/nv-modeset-interface.o /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-modeset/nvidia-modeset-linux.o LD [M] /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-modeset.o /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c: In function ‘nvidia_drm_lock_user_pages’: /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:140:5: warning: passing argument 6 of ‘get_user_pages’ makes pointer from integer without a cast [enabled by default] pages_pinned = NV_GET_USER_PAGES(address, pages_count, write, force, ^ In file included from include/linux/scatterlist.h:7:0, from include/linux/dma-mapping.h:10, from include/drm/drmP.h:37, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-os-interface.h:32, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:27: include/linux/mm.h:1222:6: note: expected ‘struct page **’ but argument is of type ‘int’ long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:140:5: warning: passing argument 7 of ‘get_user_pages’ from incompatible pointer type [enabled by default] pages_pinned = NV_GET_USER_PAGES(address, pages_count, write, force, ^ In file included from include/linux/scatterlist.h:7:0, from include/linux/dma-mapping.h:10, from include/drm/drmP.h:37, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-os-interface.h:32, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:27: include/linux/mm.h:1222:6: note: expected ‘struct vm_area_struct **’ but argument is of type ‘struct page **’ long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:140:5: error: too many arguments to function ‘get_user_pages’ pages_pinned = NV_GET_USER_PAGES(address, pages_count, write, force, ^ In file included from include/linux/scatterlist.h:7:0, from include/linux/dma-mapping.h:10, from include/drm/drmP.h:37, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-os-interface.h:32, from /tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.c:27: include/linux/mm.h:1222:6: note: declared here long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ make[2]: *** [/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel/nvidia-drm/nvidia-drm-linux.o] Error 1 make[2]: Target `__build' not remade because of errors. make[1]: *** [_module_/tmp/selfgz3636/NVIDIA-Linux-x86_64-367.35/kernel] Error 2 make[1]: Target `modules' not remade because of errors. make[1]: Leaving directory `/usr/src/linux-headers-4.4.0-143-generic' make: *** [modules] Error 2 ERROR: The nvidia kernel module was not created. ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com. ** Attachment added: "nvidia-installer log file for -143 kernel" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+attachment/5249523/+files/nvidia-installer.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
@Alberto, you're right. After talking to him and getting more info I understand he's using an old closed source driver he needs to update. My apologies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896521] [NEW] Mounting a logical volume on a Drobo 5D will hang
Public bug reported:
Given these logical volumes on a Drobo 5D mounting will result in a
hang:
root@atx1:/var/log# lvs vg-drobo
LV VG Attr LSizePool Origin Data% Meta% Move Log
Cpy%Sync Convert
encrypted vg-drobo -wi-a- 1000.00g
persistent vg-drobo -wi-a- 600.00g
timber vg-drobo -wi-ao1.50t
timber2vg-drobo -wi-ao1.00t
root@atx1:/var/log# mount /dev/vg-drobo/timber /mnt/drobo-timber/
# hangs
I expect the mount to succeed without hanging.
This bug is not present in 16.04 / 16.04.1 (latest is
linux-4.4.0-189-generic).
Release bisection revealed it showed up in u16.04.2:
linux-4.8.0-36-generic from LiveCD.
I found it when finally upgrading a 16.04 host which was using 4.4
kernel to 18.04 which uses 4.15 (LTS) / 5.4 (HWE) kernels.
After further commit bisection I found the commit which introduced this
behavior is: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?id=5b91dfe187bbe3a8116432016375f39fff91a237
$ git show 5b91dfe187bb
Mon Apr 18 13:09:10 2016 +0300 5b91dfe187bb usb: storage: scsiglue: limit USB3
devices to 2048 sectors [Felipe Balbi]
diff --git a/drivers/usb/storage/scsiglue.c b/drivers/usb/storage/scsiglue.c
index 9da1fb3d0ff4..88920142e375 100644
--- a/drivers/usb/storage/scsiglue.c
+++ b/drivers/usb/storage/scsiglue.c
@@ -133,6 +133,11 @@ static int slave_configure(struct scsi_device *sdev)
* let the queue segment size sort out the real limit.
*/
blk_queue_max_hw_sectors(sdev->request_queue, 0x7F);
+ } else if (us->pusb_dev->speed >= USB_SPEED_SUPER) {
+ /* USB3 devices will be limited to 2048 sectors. This gives us
+* better throughput on most devices.
+*/
+ blk_queue_max_hw_sectors(sdev->request_queue, 2048);
}
/* Some USB host controllers can't do DMA; they have to use PIO.
I built kernels with this change commented out and confirmed I can
successfully mount the LV from the Drobo using 4.8 and 4.15 kernels.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-117-generic 4.15.0-117.118
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not
found.
Date: Mon Sep 21 12:37:39 2020
HibernationDevice:
#RESUME=UUID=64794be3-24a0-49f9-9239-371624a3d193
RESUME=none
InstallationDate: Installed on 2020-09-20 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
enp0s31f6 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic
root=/dev/mapper/vg--ssd2tb-u18040 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.15.0-117-generic N/A
linux-backports-modules-4.15.0-117-generic N/A
linux-firmware 1.173.19
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3802
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII RANGER
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896521
Title:
Mounting a logical volume on a Drobo 5D will hang
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896521/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896521] Re: Mounting a logical volume on a Drobo 5D will hang
** Attachment added: "syslog entries showing several "blocked for more than 120 seconds" errors" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896521/+attachment/5413021/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896521 Title: Mounting a logical volume on a Drobo 5D will hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
I'll test the 5.8 kernel this weekend. I'll upload a couple of tarballs next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
Cannot upload crash dumps due to timeout presumably due to size (1.6Gb). Here're links instead: 1. http://temp.karakhorum.com/dl/crash_202009120944.tar.bz2 2. http://temp.karakhorum.com/dl/crash_202009121459.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
groovy: 20.10: 5.8.0-19-generic: incremental, no dry-run: Success (no
panic).
Kernel version bisection:
cosmic: 18.10: 4.18.0-25-generic: incremental, dry-run: panic
disco: 19.04: 5.0.0-13-generic: incremental, dry-run: success. 105m19s
(*insanely* fast).
Attempted revision bisection
Within disco tree:
git checkout -b mybisect origin/master
git bisect start
git bisect good Ubuntu-4.18.0-12.13
git bisect bad Ubuntu-5.0.0-10.11
This set my HEAD to:
commit 94710cac0ef4ee177a63b5227664b38c95bbf703 (HEAD, tag: v4.18)
Author: Linus Torvalds
Date: Sun Aug 12 13:41:04 2018 -0700
Linux 4.18
I then did a 'Kernel made' e.g.
cp -a /boot/config-`uname -r` .config
make oldconfig
make clean
custom=bbb01
make -j $(nproc) deb-pkg LOCALVERSION=-${custom}
The resulting kernel would boot but I could not ssh to it. systemctl
would return error about not being able to connect to dbus.
I assumed there are Ubuntu specific bits to the kernel which systemctl
requires so aborted.
** Attachment added: "dmesg from 4.18.0-25-generic panic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+attachment/5414734/+files/dmesg.202009261751
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
Kernel release bisection: cosmic: 4.18.0-26: incremental, dry-run: panic about 303GB cosmic: 4.18.0-26: incremental, dry-run: panic about 21GB cosmic: 4.18.0-26: incremental, dry-run: panic about 22GB disco: 4.19.0-13: incremental, dry-run: testing: success The first run using 4.18.0-26 that was able to get to 303GB before panic is intriguing (it's why I ran it twice). All previous panics when doing an incremental rsync were ~20-22GB in (ala the subsequent two runs). The only thing we can say with certainty is the problem did not reproduce using 4.19.0-13. If the problem is a stack overflow then any changes in stack size, or different paths which use less stack, would result in the problem being less visible using the amount of data I'm copying (~1.4TB). ** Attachment added: "crash files from weekend of 10/3/20" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+attachment/5417903/+files/crash_201003.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820526] [NEW] linux-signed-generic-lts-xenial 4.4.0-143 depends on linux-generic instead of linux-generic-lts-xenial
Public bug reported: Linux 14.04.6 LTS with HWE stack. Am on 4.4.0-142, did a dist-update and 3.13.0-167 gets pulled in e.g. # sudo apt-get install linux-signed-generic-lts-xenial Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic linux-signed-generic-lts-xenial 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/60.2 MB of archives. After this operation, 275 MB of additional disk space will be used. Do you want to continue? [Y/n] apt-cache policy linux-signed-generic-lts-xenial shows dependency on linux-generic instead of linux-generic-lts-xenial. What I expected to happen is that the 3.x kernel bits wouldn't be installed. This may also be why building VirtualBox DKMS module is broken: Processing triggers for linux-image-4.4.0-143-generic (4.4.0-143.169~14.04.2) ... /etc/kernel/postinst.d/dkms: Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) Consult /var/lib/dkms/virtualbox/4.3.36/build/make.log for more information. ** Affects: linux-meta-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Description changed: Linux 14.04.6 LTS with HWE stack. Am on 4.4.0-142, did a dist-update and 3.13.0-167 gets pulled in e.g. # sudo apt-get install linux-signed-generic-lts-xenial Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following extra packages will be installed: - linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic - linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic - linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic + linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic + linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic + linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic Suggested packages: - fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools + fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: - linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic - linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic - linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic - linux-signed-generic-lts-xenial + linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic + linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic + linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic + linux-signed-generic-lts-xenial 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/60.2 MB of archives. After this operation, 275 MB of additional disk space will be used. - Do you want to continue? [Y/n] + Do you want to continue? [Y/n] apt-cache policy linux-signed-generic-lts-xenial shows dependency on linux-generic instead of linux-generic-lts-xenial. What I expected to happen is that the 3.x kernel bits wouldn't be installed. + + This also breaks building VirtualBox DKMS module: + + Processing triggers for linux-image-4.4.0-143-generic (4.4.0-143.169~14.04.2) ... + /etc/kernel/postinst.d/dkms: + Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) + Consult /var/lib/dkms/virtualbox/4.3.36/build/make.log for more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820526 Title: linux-signed-generic-lts-xenial 4.4.0-143 depends on linux-generic instead of linux-generic-lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1820526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820526] Re: linux-signed-generic-lts-xenial 4.4.0-143 depends on linux-generic instead of linux-generic-lts-xenial
** Attachment added: "VirtualBox DKMS build log" https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1820526/+attachment/5247076/+files/make.log ** Description changed: Linux 14.04.6 LTS with HWE stack. Am on 4.4.0-142, did a dist-update and 3.13.0-167 gets pulled in e.g. # sudo apt-get install linux-signed-generic-lts-xenial Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: linux-generic linux-headers-3.13.0-167 linux-headers-3.13.0-167-generic linux-headers-generic linux-image-3.13.0-167-generic linux-image-generic linux-modules-3.13.0-167-generic linux-modules-extra-3.13.0-167-generic linux-signed-generic-lts-xenial 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/60.2 MB of archives. After this operation, 275 MB of additional disk space will be used. Do you want to continue? [Y/n] apt-cache policy linux-signed-generic-lts-xenial shows dependency on linux-generic instead of linux-generic-lts-xenial. What I expected to happen is that the 3.x kernel bits wouldn't be installed. - This also breaks building VirtualBox DKMS module: + This may also be why building VirtualBox DKMS module is broken: Processing triggers for linux-image-4.4.0-143-generic (4.4.0-143.169~14.04.2) ... /etc/kernel/postinst.d/dkms: Error! Bad return status for module build on kernel: 4.4.0-143-generic (x86_64) Consult /var/lib/dkms/virtualbox/4.3.36/build/make.log for more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820526 Title: linux-signed-generic-lts-xenial 4.4.0-143 depends on linux-generic instead of linux-generic-lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1820526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818049] Re: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]
I have the same problem as arQon. Logged as sub-issue of #1820526 (found this ticket after opening that). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818049 Title: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1818049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1398906] Re: avis-support.jar not finding fastutil
Additional info: Using the avis package from sourceforge works as expected (no crash). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1398906 Title: avis-support.jar not finding fastutil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avis/+bug/1398906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1398906] [NEW] avis-support.jar not finding fastutil
Public bug reported:
1. Run avisd in console.
2. Modify avis "hello-world.c" sample app to use "elvin://localhost:2917";
instead of "elvin://public.elvin.org";
3. In console see this crash:
{{{
Dec 03 10:31:23: Avis: Info: Avis event router version 1.2.2
Dec 03 10:31:24: Avis: Info: Router listening on 0.0.0.0/0.0.0.0:2917
(elvin://0.0.0.0)
Dec 03 10:31:55: Avis: Alarm: Server exception:
it/unimi/dsi/fastutil/longs/Long2ObjectOpenHashMap
Exception trace:
java.lang.NoClassDefFoundError:
it/unimi/dsi/fastutil/longs/Long2ObjectOpenHashMap
at org.avis.router.Connection.(Connection.java:82)
at org.avis.router.Router.handleConnRqst(Router.java:634)
at org.avis.router.Router.messageReceived(Router.java:582)
at
org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:570)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648)
at
org.apache.mina.filter.ReadThrottleFilterBuilder$Release.messageReceived(ReadThrottleFilterBuilder.java:186)
at
org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
at
org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
at
org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648)
at
org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:220)
at
org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:264)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException:
it.unimi.dsi.fastutil.longs.Long2ObjectOpenHashMap
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 16 more
}}}
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: avis 1.2.2-2
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Dec 3 11:26:30 2014
InstallationDate: Installed on 2014-05-18 (198 days ago)
InstallationMedia: This
PackageArchitecture: all
SourcePackage: avis
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: avis (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398906
Title:
avis-support.jar not finding fastutil
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avis/+bug/1398906/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] [NEW] Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
Public bug reported: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kernelcrash bionic uec-images ** Attachment added: "cat /proc/version_signature > version.log" https://bugs.launchpad.net/bugs/1895563/+attachment/5410760/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
** Attachment added: "sudo lspci -vnvn > lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+attachment/5410773/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410777/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410775/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410783/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410782/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410778/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410776/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410784/+files/WifiSyslog.txt ** Description changed: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno
[Bug 1895563] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410781/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
apport information ** Tags added: apport-collected ** Description changed: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Sep 13 12:53 seq + crw-rw 1 root audio 116, 33 Sep 13 12:53 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.17 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fu
[Bug 1895563] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410779/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410780/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410786/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410789/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410794/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410792/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410788/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410785/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410790/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410793/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410787/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895563] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1895563/+attachment/5410791/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
