[Kernel-packages] [Bug 1938462] [NEW] If a computer is booted with a USB drive installed, ZFS will fail to find any pools
Public bug reported: I accidentally booted a computer with a USB drive inserted. After the system booted, I was unable to log in to my desktop environment. I dropped to terminal and found that the zfs volume did not mount and I was dropped into the root directory. zpool status returns that no volume was defined which was worrying. Upon unplugging the USB drive and rebooting, the zfs volume returned and I could log in as usual. lsblk is as follows on a normal boot: NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT ... sda 8:00 111.8G 0 disk ├─sda18:1032G 0 part [SWAP] └─sda28:20 79.8G 0 part sdb 8:16 0 931.5G 0 disk ├─sdb18:17 0 931.5G 0 part └─sdb98:25 0 8M 0 part sdc 8:32 0 931.5G 0 disk ├─sdc18:33 0 931.5G 0 part └─sdc98:41 0 8M 0 part sdd 8:48 0 931.5G 0 disk ├─sdd18:49 0 931.5G 0 part └─sdd98:57 0 8M 0 part ... nvme0n1 259:00 232.9G 0 disk ├─nvme0n1p1 259:10 8M 0 part ├─nvme0n1p2 259:20 512M 0 part /boot/efi └─nvme0n1p3 259:30 232.4G 0 part / zpool status is as follows on a normal boot: pool: zpool state: ONLINE scan: none requested config: NAMESTATE READ WRITE CKSUM zpool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 cache sda2 ONLINE 0 0 0 errors: No known data errors I suspected what happened was that the USB drive somehow took a device node formerly assigned to one of the zfs disks and that threw the zfs loader off. Detaching the drive caused the device node to become reassigned to the zfs disks and thus the system was able to boot as normal. Can a fix be devised for this? Is it possible for ZFS to do some extra work like assigning a UUID to it's volumes during creation, then during remounting, instead of just using the stored device nodes, probe each drive attached for matching UUIDs and remounting the volume based on the UUIDs? ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Description changed: I accidentally booted a computer with a USB drive inserted. After the system booted, I was unable to log in to my desktop environment. I dropped to terminal and found that the zfs volume did not mount and I was dropped into the root directory. zpool status returns that no volume was defined which was worrying. Upon unplugging the USB drive and rebooting, the zfs volume returned and I could log in as usual. - lsblk is as follows: + lsblk is as follows on a normal boot: NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT ... - sda 8:00 111.8G 0 disk + sda 8:00 111.8G 0 disk ├─sda18:1032G 0 part [SWAP] - └─sda28:20 79.8G 0 part - sdb 8:16 0 931.5G 0 disk - ├─sdb18:17 0 931.5G 0 part - └─sdb98:25 0 8M 0 part - sdc 8:32 0 931.5G 0 disk - ├─sdc18:33 0 931.5G 0 part - └─sdc98:41 0 8M 0 part - sdd 8:48 0 931.5G 0 disk - ├─sdd18:49 0 931.5G 0 part - └─sdd98:57 0 8M 0 part + └─sda28:20 79.8G 0 part + sdb 8:16 0 931.5G 0 disk + ├─sdb18:17 0 931.5G 0 part + └─sdb98:25 0 8M 0 part + sdc 8:32 0 931.5G 0 disk + ├─sdc18:33 0 931.5G 0 part + └─sdc98:41 0 8M 0 part + sdd 8:48 0 931.5G 0 disk + ├─sdd18:49 0 931.5G 0 part + └─sdd98:57 0 8M 0 part ... - nvme0n1 259:00 232.9G 0 disk - ├─nvme0n1p1 259:10 8M 0 part + nvme0n1 259:00 232.9G 0 disk + ├─nvme0n1p1 259:10 8M 0 part ├─nvme0n1p2 259:20 512M 0 part /boot/efi └─nvme0n1p3 259:30 232.4G 0 part / - zpool status is as follows: - pool: zpool - state: ONLINE - scan: none requested + zpool status is as follows on a normal boot: + pool: zpool + state: ONLINE + scan: none requested config: - NAMESTATE READ WRITE CKSUM - zpool ONLINE 0 0 0 - raidz1-0 ONLINE 0 0 0 - sdb ONLINE 0 0 0 - sdc ONLINE 0 0 0 - sdd ONLINE 0 0 0 - cache - sda2 ONLINE 0 0 0 + NAMESTATE READ WRITE CKSUM + zpool ONLINE 0 0 0 + raidz1-0 ONLINE 0 0 0 + sdb ONLINE 0 0 0 + sdc ONLINE 0 0 0 + sdd ONLINE 0 0 0 + cache + sda2 ONLINE 0 0 0 errors: No known data errors I suspected what happened was that the USB drive somehow took a device node formerly assigned to
[Kernel-packages] [Bug 1933337] Re: bcmwl fails to build with 5.11 HWE-edge kernel on Ubuntu 20.04 LTS
Wrong package ** Package changed: broadcom-sta (Ubuntu) => bcmwl (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/197 Title: bcmwl fails to build with 5.11 HWE-edge kernel on Ubuntu 20.04 LTS Status in bcmwl package in Ubuntu: New Bug description: When trying to build bcmwl using the latest 5.11 HWE-edge kernel on Ubuntu 20.04 LTS, the kernel module will refuse to build: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] 461 | fs = get_fs(); | ^~ | get_ds /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: incompatible types when assigning to type ‘mm_segment_t’ from type ‘int’ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:2: error: implicit declaration of function ‘set_fs’; did you mean ‘sget_fc’? [-Werror=implicit-function-declaration] 462 | set_fs(get_ds()); | ^~ | sget_fc In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:26: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’? 600 | #define get_ds() (KERNEL_DS) | ^ I understand that a fix for this has been rolled out to Hirsuite (0029 -Update-for-set_fs-removal-in-Linux-5.10.patch). Can this fix please be backported to Focal? Since it fixes the problem for people needing to run LTS and use the HWE-Edge kernel for any given reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844746] [NEW] Kodi hangs up and videos won't play
Public bug reported: Each time that I use kodi, it allows me to sign in and get to the intro screen,etc. It will start to play the video and then hang. I reboot and it does the same thing. Ubuntu 16.04 Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-64-generic 4.15.0-64.73 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2146 F pulseaudio /dev/snd/controlC0: david 2146 F pulseaudio /dev/snd/controlC2: david 2146 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 19 18:30:52 2019 HibernationDevice: RESUME=UUID=f49fbfcf-a1e2-4740-ba41-4dcab30c90dc InstallationDate: Installed on 2017-05-02 (870 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: ZOTAC ZBOX-AD04 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=b95f85bd-633b-4ec2-8e28-e51070b90849 ro quiet plymouth:debug=1=1=1=1=1=1=1=1 splash RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-05-29 (113 days ago) dmi.bios.date: 12/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: NA dmi.board.name: ZBOX-AD04 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/24/2012:svnZOTAC:pnZBOX-AD04:pvrXX:rvnZOTAC:rnZBOX-AD04:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-AD04 dmi.product.version: XX dmi.sys.vendor: ZOTAC ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1844746 Title: Kodi hangs up and videos won't play Status in linux package in Ubuntu: New Bug description: Each time that I use kodi, it allows me to sign in and get to the intro screen,etc. It will start to play the video and then hang. I reboot and it does the same thing. Ubuntu 16.04 Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-64-generic 4.15.0-64.73 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2146 F pulseaudio /dev/snd/controlC0: david 2146 F pulseaudio /dev/snd/controlC2: david 2146 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 19 18:30:52 2019 HibernationDevice: RESUME=UUID=f49fbfcf-a1e2-4740-ba41-4dcab30c90dc InstallationDate: Installed on 2017-05-02 (870 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: ZOTAC ZBOX-AD04 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=b95f85bd-633b-4ec2-8e28-e51070b90849 ro quiet plymouth:debug=1=1=1=1=1=1=1=1 splash RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-05-29 (113 days ago) dmi.bios.date: 12/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: NA dmi.board.name: ZBOX-AD04 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/24/2012:svnZOTAC:pnZBOX-AD04:pvrXX:rvnZOTAC:rnZBOX-AD04:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-AD04 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1726021] [NEW] Artful Aardvark cannot boot dm-raid raid5 array
Public bug reported: Rehash of bug 1313169 / bug 1683105 My patch was ignored. As a result I am left with two unbootable boxes after upgrade. ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New ** Description changed: Rehash of bug 1313169. My patch was ignored. As a result I am left with two unbootable boxes after upgrade. + + System hangs at error device-manager: table: 253:1: raid: unknown target + type followed by dropping to busybox. ** Description changed: - Rehash of bug 1313169. + Rehash of bug 1313169 / bug 1683105 My patch was ignored. As a result I am left with two unbootable boxes after upgrade. - - System hangs at error device-manager: table: 253:1: raid: unknown target - type followed by dropping to busybox. ** Package changed: linux (Ubuntu) => dmraid (Ubuntu) -- 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/1726021 Title: Artful Aardvark cannot boot dm-raid raid5 array Status in dmraid package in Ubuntu: New Bug description: Rehash of bug 1313169 / bug 1683105 My patch was ignored. As a result I am left with two unbootable boxes after upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1726021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685646] [NEW] 'dpkg-reconfigure lirc' doesn't work as expected.
Public bug reported: The lirc package does not respond predictably to the 'sudo dpkg- reconfigure lirc' command. When the command is run, the following messages are displayed: Warning: Stopping lircd.service, but it can still be activated by: lircd.socket Listing '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/baseview.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/choosers.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/config.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/database.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_control.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_model.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_view.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/util.py'... This is followed by the system abruptly dropping back to shell without the configuration screen displayed. No other errors are displayed. There is no errors in dmesg. ** Affects: lirc (Ubuntu) Importance: Undecided Status: New ** Summary changed: - dpkg-reconfigure doesn't work as expected. + 'dpkg-reconfigure lirc' doesn't work as expected. ** Package changed: linux (Ubuntu) => lirc (Ubuntu) -- 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/1685646 Title: 'dpkg-reconfigure lirc' doesn't work as expected. Status in lirc package in Ubuntu: New Bug description: The lirc package does not respond predictably to the 'sudo dpkg- reconfigure lirc' command. When the command is run, the following messages are displayed: Warning: Stopping lircd.service, but it can still be activated by: lircd.socket Listing '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/baseview.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/choosers.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/config.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/database.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_control.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_model.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/mvc_view.py'... Compiling '/usr/lib/x86_64-linux-gnu/python3/dist-packages/lirc/util.py'... This is followed by the system abruptly dropping back to shell without the configuration screen displayed. No other errors are displayed. There is no errors in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1685646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683105] [NEW] Installation of DMRaid should automatically add necessary modules to /etc/initramfs-tools/modules
Public bug reported: This is related to bug 1313169, I have had a sudden bout of clarity on the cause of the issue. I propose this modification to the dmraid installation script as it is a small but necessary enhancement. When dmraid is installed, it adds all the necessary hooks to initramfs- tools. However, it has one oversight, that the required raid modules are not added to /etc/initramfs-tools/modules. Without these modules, dmraid will inevitably fail to initialize the array when started since the kernel would not be able to find the required modules in the image. I propose that when dmraid is installed, during installation the script would check to see if the following items are already in /etc/initramfs- tools/modules, and append the required modules into the bottom of the file if it's not, and then rebuild the initramfs, update grub and if necessary reinstall grub. On uninstall of package, I propose that we should just warn the user but leave the lines in just in case they're using something else that also needs the modules. The following modules should be appended to the /etc/inmitramfs- tools/modules file: raid0 dm_raid raid1 raid10 raid456 async_raid6_recov async_memcpy async_pq async_tx raid6_pq async_xor xor libcrc32c ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => dmraid (Ubuntu) ** Description changed: This is related to bug 1313169, I have had a sudden bout of clarity on the cause of the issue. I propose this modification to the dmraid installation script as it is a small but necessary enhancement. When dmraid is installed, it adds all the necessary hooks to initramfs- tools. However, it has one oversight, that the required raid modules are not added to /etc/initramfs-tools/modules. Without these modules, dmraid will inevitably fail to initialize the array when started since the kernel would not be able to find the required modules in the image. I propose that when dmraid is installed, during installation the script would check to see if the following items are already in /etc/initramfs- tools/modules, and append the required modules into the bottom of the file if it's not, and then rebuild the initramfs, update grub and if necessary reinstall grub. On uninstall of package, I propose that we should just warn the user but leave the lines in just in case they're using something else that also needs the modules. The following modules should be appended to the /etc/inmitramfs- tools/modules file: raid0 dm_raid raid1 raid10 raid456 async_raid6_recov async_memcpy async_pq async_tx raid6_pq + async_xor + xor ** Description changed: This is related to bug 1313169, I have had a sudden bout of clarity on the cause of the issue. I propose this modification to the dmraid installation script as it is a small but necessary enhancement. When dmraid is installed, it adds all the necessary hooks to initramfs- tools. However, it has one oversight, that the required raid modules are not added to /etc/initramfs-tools/modules. Without these modules, dmraid will inevitably fail to initialize the array when started since the kernel would not be able to find the required modules in the image. I propose that when dmraid is installed, during installation the script would check to see if the following items are already in /etc/initramfs- tools/modules, and append the required modules into the bottom of the file if it's not, and then rebuild the initramfs, update grub and if necessary reinstall grub. On uninstall of package, I propose that we should just warn the user but leave the lines in just in case they're using something else that also needs the modules. The following modules should be appended to the /etc/inmitramfs- tools/modules file: raid0 dm_raid raid1 raid10 raid456 async_raid6_recov async_memcpy async_pq async_tx raid6_pq async_xor xor + libcrc32c -- 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/1683105 Title: Installation of DMRaid should automatically add necessary modules to /etc/initramfs-tools/modules Status in dmraid package in Ubuntu: New Bug description: This is related to bug 1313169, I have had a sudden bout of clarity on the cause of the issue. I propose this modification to the dmraid installation script as it is a small but necessary enhancement. When dmraid is installed, it adds all the necessary hooks to initramfs-tools. However, it has one oversight, that the required raid modules are not added to /etc/initramfs-tools/modules. Without these modules, dmraid will inevitably fail to initialize the array when started since the kernel would not be able to find the required modules in the image. I propose that when dmraid is installed,
[Kernel-packages] [Bug 1313169] Re: Ubuntu Trusty Tahr cannot boot on RAID5 array
Followed up on bug 1683105 . I've worked out the exact thing that needs to be done. -- 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/1313169 Title: Ubuntu Trusty Tahr cannot boot on RAID5 array Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Raid array is three identical Western Digital Green series 500GB hard drives on an NVIDIA controller set to RAID5 for a total of 1TiB (931.52GB) storage. Installation was done using the Ubuntu LiveCD. Partitions on the filesystem was created beforehand using gparted. The partition table is set up to be GPT with a 8MB bios_grub partition, a 256MB fat32 EFIBoot partition (not used for this setup, board does not support EFI and is expected to boot from the bios_grub legacy partition), a 4GB swap, 80GB root partition, and the rest for /home. Then the installer is invoked and the partitions are set up. GRUB is told to install to the root of the RAID array in /dev/mapper . The installation went flawlessly. Upon reboot, GRUB loads as expected, and loads the kernel and initrd as expected. However, the kernel gives up on waiting for the root partition and drops to initramfs busybox. "dmesg|grep device" shows the following errors: device-mapper: table: 252:0: raid: unknown target type device-mapper: ioctl: error adding target to table Trying to invoke dmraid -a y results in the following error: ERROR: device-mapper target type "raid" is not in the kernel RAID set "nvidia_babddecf" was not activated. nvidia_babddecf is the assigned volume name by the controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1313169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1628686] Re: kernel BUG at linux-4.8.0/mm/usercopy.c:75!
I ran the command as requested, and got nothing root@helen:~# grep HARDENED_USERCOPY_PAGESPAN= /boot/config-`uname -r` root@helen:~# There appears to be another kernel update today. However that update did not help with the issue. -- 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/1628686 Title: kernel BUG at linux-4.8.0/mm/usercopy.c:75! Status in linux package in Ubuntu: Triaged Bug description: This kernel warning occurs on Ubuntu 16.10 guests with Linux 4.8 on VMware Fusion. The VM will boot but does not make it a graphical display. usercopy: kernel memory overwrite attempt detected to 9bdaf3e0 () (4392 bytes) [ cut here ] kernel BUG at /build/linux-FGN3Aj/linux-4.8.0/mm/usercopy.c:75! invalid opcode: [#1] SMP Modules linked in: intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ipmi_msghandler aesni_intel vmw_balloon aes_x86_64 lrw glue_helper ablk_helper cryptd intel_rapl_perf joydev input_leds serio_raw binfmt_misc snd_ens1371 snd_ac97_codec gameport ac97_bus snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core snd_seq_midi videodev snd_seq_midi_event media snd_rawmidi snd_seq snd_seq_device btusb btrtl btbcm snd_timer btintel snd bluetooth soundcore i2c_piix4 vmw_vmci shpchp nfit floppy(+) mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid vmwgfx ttm psmouse drm_kms_helper syscopyarea sysfillrect ahci libahci e1000 mptspi mptscsih mptbase scsi_transport_spi sysimgblt fb_sys_fops drm pata_acpi fjes CPU: 0 PID: 1293 Comm: glxinfo Not tainted 4.8.0-17-generic #19-Ubuntu Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/02/2015 task: 9bdb74465580 task.stack: 9bdb73f0 RIP: 0010:[] [] __check_object_size+0x111/0x49b RSP: 0018:9bdb73f03c58 EFLAGS: 00010282 RAX: 006c RBX: 9bdaf3e0 RCX: RDX: RSI: 9bdb7a60dc68 RDI: 9bdb7a60dc68 RBP: 9bdb73f03ca0 R08: 79706f6372657375 R09: 656b203a79706f63 R10: 3fffc000 R11: 06c1 R12: 1128 R13: R14: 9bdaf3e01128 R15: 9bdaf3e01127 FS: 7f22f6d20740() GS:9bdb7a60() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55b6cf2c71c8 CR3: b3f91000 CR4: 001406f0 Stack: 9bdb73f16ce8 9bdb73f03ca0 c03df765 3fffc000 9bdaf41c 55b6cf0ca1b0 9bdb73edbc00 9bdaf3e0 1128 9bdb73f03d90 c03c6f0f 9bdb73f03d08 Call Trace: [] ? vmw_cmdbuf_alloc+0x175/0x240 [vmwgfx] [] vmw_execbuf_process+0x8bf/0x1250 [vmwgfx] [] ? __check_object_size+0x12d/0x49b [] ? drm_ioctl+0x236/0x4f0 [drm] [] ? __alloc_pages_nodemask+0x135/0x300 [] ? ttm_read_lock+0x34/0xc0 [ttm] [] vmw_execbuf_ioctl+0xe6/0x180 [vmwgfx] [] vmw_generic_ioctl+0x249/0x280 [vmwgfx] [] vmw_unlocked_ioctl+0x15/0x20 [vmwgfx] [] do_vfs_ioctl+0xa3/0x610 [] ? __do_page_fault+0x203/0x4d0 [] SyS_ioctl+0x79/0x90 [] entry_SYSCALL_64_fastpath+0x1e/0xa8 Code: 1f 03 00 00 49 c7 c0 86 36 6a 9d 48 c7 c2 30 0b 68 9d 48 c7 c6 4c 8e 69 9d 4d 89 e1 48 89 d9 48 c7 c7 10 03 6a 9d e8 03 05 f7 ff <0f> 0b 4c 8b 75 b8 48 8b 5d d0 45 89 fd 4c 8b 65 c8 4c 89 e6 48 RIP [] __check_object_size+0x111/0x49b RSP ---[ end trace 48bce713521eb13e ]--- Disabling CONFIG_HARDENED_USERCOPY_PAGESPAN works around this issue. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8e1f74ea02cf4562404c48c6882214821552c13f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1628686] Re: kernel BUG at linux-4.8.0/mm/usercopy.c:75!
Upgraded to proposed kernel. Linux helen 4.8.0-25-generic #27-Ubuntu SMP Thu Oct 13 03:34:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Issue still occurs: [ 75.257763] usercopy: kernel memory overwrite attempt detected to 9dfb48493d38 () (16 bytes) [ 75.257791] [ cut here ] [ 75.257793] kernel BUG at /build/linux-rb6V7L/linux-4.8.0/mm/usercopy.c:75! [ 75.257795] invalid opcode: [#3] SMP [ 75.257797] Modules linked in: xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo snd_hrtimer binfmt_misc nls_iso8859_1 ir_lirc_codec lirc_dev rc_rc6_mce mceusb snd_hda_codec_via snd_hda_codec_generic kvm_amd kvm nvidia_uvm(POE) irqbypass input_leds serio_raw blackmagic(POE) k8temp snd_usb_audio snd_hda_codec_hdmi snd_usbmidi_lib gspca_sonixj gspca_main v4l2_common videodev media rc_imon_pad imon rc_core snd_hda_intel snd_ctxfi snd_hda_codec snd_hda_core snd_seq_midi snd_seq_midi_event shpchp snd_hwdep snd_rawmidi snd_seq snd_pcm snd_seq_device snd_timer snd soundcore asus_atk0110 i2c_nforce2 wmi mac_hid nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_mirror dm_region_hash dm_log btrfs raid10 raid1 raid0 dm_raid raid456 [ 75.257835] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c pata_acpi nvidia(POE) psmouse drm video firewire_ohci firewire_core floppy ahci fjes forcedeth libahci crc_itu_t pata_amd [ 75.257848] CPU: 1 PID: 2837 Comm: BlackmagicFirmw Tainted: P DOE 4.8.0-25-generic #27-Ubuntu [ 75.257850] Hardware name: System manufacturer System Product Name/M4N78 PRO, BIOS 130304/13/2011 [ 75.257852] task: 9dfb487e0d00 task.stack: 9dfb4849 [ 75.257854] RIP: 0010:[] [] __check_object_size+0x77/0x1dc [ 75.257860] RSP: 0018:9dfb48493ca0 EFLAGS: 00010286 [ 75.257862] RAX: 0063 RBX: 9dfb48493d38 RCX: [ 75.257863] RDX: RSI: 9dfbf7c4dc68 RDI: 9dfbf7c4dc68 [ 75.257865] RBP: 9dfb48493cc0 R08: 0003eee3 R09: 0005 [ 75.257867] R10: 9dfb5fc43238 R11: 040a R12: 0010 [ 75.257868] R13: R14: 9dfb48493d48 R15: 7ffdccd9da50 [ 75.257870] FS: 7fbd30601780() GS:9dfbf7c4() knlGS: [ 75.257872] CS: 0010 DS: ES: CR0: 80050033 [ 75.257874] CR2: 7fbd2f3e4150 CR3: a024a000 CR4: 06e0 [ 75.257875] Stack: [ 75.257877] 9dfb48493d38 0010 7ffdccd9da50 9dfbed7436c8 [ 75.257880] 9dfb48493ce8 c11c11eb 9dfb48493d38 0001 [ 75.257883] 7ffdccd9da50 c11a377a 9dfb57e7d000 [ 75.257885] Call Trace: [ 75.257946] [] __dl_copy_from_user+0x1b/0x40 [blackmagic] [ 75.257974] [] _ZN18IoctlMessageKernel6unpackEv+0x4a/0x160 [blackmagic] [ 75.257997] [] ? blackmagic_ioctl_private+0x35db/0x4080 [blackmagic] [ 75.258001] [] ? filemap_map_pages+0x202/0x410 [ 75.258004] [] ? do_filp_open+0xa5/0x100 [ 75.258008] [] ? trace_buffer_lock_reserve+0x1c/0x50 [ 75.258011] [] ? trace_event_buffer_lock_reserve+0x72/0xf0 [ 75.258036] [] ? blackmagic_ioctl+0x49/0x60 [blackmagic] [ 75.258039] [] ? do_vfs_ioctl+0xa3/0x610 [ 75.258042] [] ? putname+0x54/0x60 [ 75.258045] [] ? do_sys_open+0x1bc/0x280 [ 75.258047] [] ? SyS_ioctl+0x79/0x90 [ 75.258051] [] ? entry_SYSCALL_64_fastpath+0x1e/0xa8 [ 75.258052] Code: 48 0f 44 d1 48 c7 c6 78 4d 2a 9e 48 c7 c1 5c a5 29 9e 48 0f 44 f1 4d 89 e1 49 89 c0 48 89 d9 48 c7 c7 f8 19 2a 9e e8 bd 03 f7 ff <0f> 0b e8 12 d6 fb ff 85 c0 75 78 48 89 df e8 96 2c e4 ff 84 c0 [ 75.258079] RIP [] __check_object_size+0x77/0x1dc [ 75.258082] RSP [ 75.258085] ---[ end trace 476b12ac04efcae0 ]--- -- 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/1628686 Title: kernel BUG at linux-4.8.0/mm/usercopy.c:75! Status in linux package in Ubuntu: Triaged Bug description: This kernel warning occurs on Ubuntu 16.10 guests with Linux 4.8 on VMware Fusion. The VM will boot but does not make it a graphical display. usercopy: kernel memory overwrite attempt detected to 9bdaf3e0 () (4392 bytes) [ cut here ] kernel BUG at /build/linux-FGN3Aj/linux-4.8.0/mm/usercopy.c:75! invalid opcode: [#1] SMP Modules linked in: intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ipmi_msghandler aesni_intel vmw_balloon aes_x86_64 lrw glue_helper ablk_helper cryptd intel_rapl_perf joydev input_leds serio_raw binfmt_misc snd_ens1371 snd_ac97_codec gameport ac97_bus snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core snd_seq_midi videodev snd_seq_midi_event media snd_rawmidi snd_seq
[Kernel-packages] [Bug 1628686] Re: kernel BUG at linux-4.8.0/mm/usercopy.c:75!
Getting the same error with the Blackmagic Intensity module. [ 73.553893] [ cut here ] [ 73.553896] kernel BUG at /build/linux-NNryke/linux-4.8.0/mm/usercopy.c:75! [ 73.553899] invalid opcode: [#3] SMP [ 73.553901] Modules linked in: xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo snd_hrtimer binfmt_misc nls_iso8859_1 snd_hda_codec_via snd_hda_codec_generic ir_lirc_codec lirc_dev rc_rc6_mce mceusb kvm_amd kvm irqbypass nvidia_uvm(POE) snd_hda_codec_hdmi input_leds serio_raw blackmagic(POE) k8temp snd_usb_audio snd_usbmidi_lib gspca_sonixj gspca_main v4l2_common videodev media snd_hda_intel snd_ctxfi snd_hda_codec rc_imon_pad imon rc_core snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd shpchp soundcore asus_atk0110 wmi i2c_nforce2 mac_hid nfsd auth_rpcgss nfs_acl lockd grace sunrpc parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_mirror dm_region_hash dm_log btrfs raid10 raid1 raid0 dm_raid raid456 [ 73.553946] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c pata_acpi nvidia(POE) psmouse firewire_ohci drm forcedeth firewire_core crc_itu_t ahci libahci pata_amd video floppy fjes [ 73.553961] CPU: 0 PID: 2886 Comm: BlackmagicFirmw Tainted: P DOE 4.8.0-22-generic #24-Ubuntu [ 73.553963] Hardware name: System manufacturer System Product Name/M4N78 PRO, BIOS 130304/13/2011 [ 73.553965] task: 939669f39a00 task.stack: 9395e0e24000 [ 73.553967] RIP: 0010:[] [] __check_object_size+0x77/0x1dc [ 73.553974] RSP: 0018:9395e0e27ca0 EFLAGS: 00010286 [ 73.553976] RAX: 0063 RBX: 9395e0e27d38 RCX: [ 73.553978] RDX: RSI: 939677c0dc68 RDI: 939677c0dc68 [ 73.553980] RBP: 9395e0e27cc0 R08: 00087388 R09: 0005 [ 73.553982] R10: 9395e0d6d738 R11: 046c R12: 0010 [ 73.553984] R13: R14: 9395e0e27d48 R15: 7ffc763f0eb0 [ 73.553986] FS: 7efe82091780() GS:939677c0() knlGS: [ 73.553988] CS: 0010 DS: ES: CR0: 80050033 [ 73.553990] CR2: 7efe80e75150 CR3: a0f16000 CR4: 06f0 [ 73.553992] Stack: [ 73.553994] 9395e0e27d38 0010 7ffc763f0eb0 93966715e108 [ 73.553998] 9395e0e27ce8 c10841eb 9395e0e27d38 0001 [ 73.554001] 7ffc763f0eb0 c106677a 9395d75d7000 [ 73.554004] Call Trace: [ 73.554067] [] __dl_copy_from_user+0x1b/0x40 [blackmagic] [ 73.554101] [] _ZN18IoctlMessageKernel6unpackEv+0x4a/0x160 [blackmagic] [ 73.554130] [] ? blackmagic_ioctl_private+0x35db/0x4080 [blackmagic] [ 73.554133] [] ? do_filp_open+0xa5/0x100 [ 73.554164] [] ? blackmagic_ioctl+0x49/0x60 [blackmagic] [ 73.554167] [] ? do_vfs_ioctl+0xa3/0x610 [ 73.554171] [] ? putname+0x54/0x60 [ 73.554174] [] ? do_sys_open+0x1bc/0x280 [ 73.554177] [] ? SyS_ioctl+0x79/0x90 [ 73.554182] [] ? entry_SYSCALL_64_fastpath+0x1e/0xa8 [ 73.554184] Code: 48 0f 44 d1 48 c7 c6 68 4d 8a ae 48 c7 c1 4c a5 89 ae 48 0f 44 f1 4d 89 e1 49 89 c0 48 89 d9 48 c7 c7 e8 19 8a ae e8 bd 03 f7 ff <0f> 0b e8 12 d6 fb ff 85 c0 75 78 48 89 df e8 96 2c e4 ff 84 c0 [ 73.554216] RIP [] __check_object_size+0x77/0x1dc [ 73.554219] RSP [ 73.554222] ---[ end trace c80a6ccc31c55190 ]--- [ 79.352997] retire_capture_urb: 5 callbacks suppressed -- 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/1628686 Title: kernel BUG at linux-4.8.0/mm/usercopy.c:75! Status in linux package in Ubuntu: Triaged Bug description: This kernel warning occurs on Ubuntu 16.10 guests with Linux 4.8 on VMware Fusion. The VM will boot but does not make it a graphical display. usercopy: kernel memory overwrite attempt detected to 9bdaf3e0 () (4392 bytes) [ cut here ] kernel BUG at /build/linux-FGN3Aj/linux-4.8.0/mm/usercopy.c:75! invalid opcode: [#1] SMP Modules linked in: intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ipmi_msghandler aesni_intel vmw_balloon aes_x86_64 lrw glue_helper ablk_helper cryptd intel_rapl_perf joydev input_leds serio_raw binfmt_misc snd_ens1371 snd_ac97_codec gameport ac97_bus snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core snd_seq_midi videodev snd_seq_midi_event media snd_rawmidi snd_seq snd_seq_device btusb btrtl btbcm snd_timer btintel snd bluetooth soundcore i2c_piix4 vmw_vmci shpchp nfit floppy(+) mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid vmwgfx ttm psmouse drm_kms_helper syscopyarea sysfillrect ahci libahci e1000 mptspi mptscsih mptbase
[Kernel-packages] [Bug 1514203] [NEW] mkfs.btrfs and fsck.btrfs gets installed into the wrong directory
Public bug reported: Watching the Ubuntu console while installing, I noticed that mkinitramfs keeps complaining that it could not find fsck.btrfs. I looked into it and noticed that both mkfs.btrfs and fsck.btrfs are being installed into /bin instead of /sbin proper. A quick workaround is to copy the files from /bin to /sbin, but this is a major issue as if the user boots from a btrfs root filesystem and the root filesystem gets corrupted, then the user will not be able to fsck the filesystem when dumped at the initrd. ** Affects: btrfs-tools (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => btrfs-tools (Ubuntu) -- 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/1514203 Title: mkfs.btrfs and fsck.btrfs gets installed into the wrong directory Status in btrfs-tools package in Ubuntu: New Bug description: Watching the Ubuntu console while installing, I noticed that mkinitramfs keeps complaining that it could not find fsck.btrfs. I looked into it and noticed that both mkfs.btrfs and fsck.btrfs are being installed into /bin instead of /sbin proper. A quick workaround is to copy the files from /bin to /sbin, but this is a major issue as if the user boots from a btrfs root filesystem and the root filesystem gets corrupted, then the user will not be able to fsck the filesystem when dumped at the initrd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1514203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1313169] Re: Ubuntu Trusty Tahr cannot boot on RAID5 array
Hi, As I've already made the permanent changes by hand to my Ubuntu installation, I am unable to check if the subsequent kernel versions have this issue fixed without performing a clean reinstall, which I am unwilling to do at the moment. Please confirm with the respective teams to ensure that the fix is in place. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1313169 Title: Ubuntu Trusty Tahr cannot boot on RAID5 array Status in “initramfs-tools” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: Raid array is three identical Western Digital Green series 500GB hard drives on an NVIDIA controller set to RAID5 for a total of 1TiB (931.52GB) storage. Installation was done using the Ubuntu LiveCD. Partitions on the filesystem was created beforehand using gparted. The partition table is set up to be GPT with a 8MB bios_grub partition, a 256MB fat32 EFIBoot partition (not used for this setup, board does not support EFI and is expected to boot from the bios_grub legacy partition), a 4GB swap, 80GB root partition, and the rest for /home. Then the installer is invoked and the partitions are set up. GRUB is told to install to the root of the RAID array in /dev/mapper . The installation went flawlessly. Upon reboot, GRUB loads as expected, and loads the kernel and initrd as expected. However, the kernel gives up on waiting for the root partition and drops to initramfs busybox. dmesg|grep device shows the following errors: device-mapper: table: 252:0: raid: unknown target type device-mapper: ioctl: error adding target to table Trying to invoke dmraid -a y results in the following error: ERROR: device-mapper target type raid is not in the kernel RAID set nvidia_babddecf was not activated. nvidia_babddecf is the assigned volume name by the controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1313169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
