[Kernel-packages] [Bug 1813496] Re: powertop does not accurately determine battery discharge rate on HP Elitebook 850 G5
Do you see this issue on Linux v5.0? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813496 Title: powertop does not accurately determine battery discharge rate on HP Elitebook 850 G5 Status in linux package in Ubuntu: Incomplete Status in powertop package in Ubuntu: Invalid Bug description: ### Summary: powertop does not accurately determine battery discharge rate on HP Elitebook 850 G5 ### ### Description ### On an HP Elitebook 850 G5 running Ubuntu 18.10 powertop does not accurately report the battery discharge rate. The reported discharge rate & estimated remaining time are always impossibly low / high respectively. See example snippet from powertop header below. ### Configuration ### HP Elitebook 850 G5 Ubunutu 18.10, 4.18.0-13-generic powertop v2.9 tlp w/default settings ### Example ### The battery reports a discharge rate of 366 mW The power consumed was 0.00 J The estimated remaining time is 49 hours, 2 minutes ### Package Version ### powertop: Installed: 2.9-0ubuntu2 Candidate: 2.9-0ubuntu2 Version table: *** 2.9-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ### Steps to Reproduce ### 1. Install Ubuntu 18.10 on HP Elitebook 850 G5 2. Install tlp from repos 3. Install powertop from repos 4. Run powertop while running on battery 5. Examine header info while in the Overview tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813496/+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 1835700] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + phase: Ready for Packaging + phase-changed: Monday, 08. July 2019 05:44 UTC + reason: + prepare-package: Pending -- version not specified variant: debs -- 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/1835700 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Ready for Packaging phase-changed: Monday, 08. July 2019 05:44 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+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 1835040] Re: Touchpd not working properly on Linux
Please test this kernel: https://people.canonical.com/~khfeng/lp1835040/ -- 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/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arnab 931 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-22 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall iBall CompBook M500 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 31 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvn:ct31:cvrTobefilledbyO.E.M.: dmi.product.family: Notebook dmi.product.name: iBall CompBook M500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: iBall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835040/+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 1835700] [NEW] linux: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Eoan) Importance: Medium Status: New ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.07.07-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + -- swm properties -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.07.07-1 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- 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/1835700 Title: linux: -proposed tracker Status in Kernel SRU Workflow:
[Kernel-packages] [Bug 1792672] Re: Regression: acpi reports battery state incorrectly after sleep
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1792672 Title: Regression: acpi reports battery state incorrectly after sleep Status in linux package in Ubuntu: Expired Bug description: On Samsung Series 9 laptops the battery state and the charger status are incorrectly reported in kernel 4.15. This bug is a regression: it has been fixed in 2012 [1] it used to work fine until Linux 14.10 (included). Quoting Matthew McCallum from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161 > If I disconnect power, remove the back cover, disconnect both the main battery and the backup battery, I am able to get power status updates (e.g. battery will show as charging/charged when plugged in, or just regular battery when not). Once I sleep, I have to repeat this process if I want the battery status to work again. > > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gioele 1939 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029 InstallationDate: Installed on 2017-06-24 (447 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.157.20 Tags: xenial Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P07ABK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP900X3D-A03IT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792672/+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 1826831] Re: Network card not working on kernel 4.15.0-48 but works on 4.15.0-47
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1826831 Title: Network card not working on kernel 4.15.0-48 but works on 4.15.0-47 Status in linux package in Ubuntu: Expired Bug description: I have network card installed in pci (lshw): *-pci:3 description: PCI bridge product: 82801 PCI Bridge vendor: Intel Corporation physical id: 1e bus info: pci@:00:1e.0 version: a4 width: 32 bits clock: 33MHz capabilities: pci subtractive_decode bus_master cap_list resources: ioport:c000(size=4096) memory:f710-f71f *-network description: Ethernet interface product: IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY vendor: Sundance Technology Inc / IC Plus Corp physical id: 2 bus info: pci@:04:02.0 logical name: enp4s2 version: 31 serial: c4:e9:84:03:15:ea size: 10Mbit/s capacity: 100Mbit/s width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=off broadcast=yes driver=sundance driverversion=1.2 duplex=half ip=10.108.8.233 latency=32 link=no maxlatency=10 mingnt=10 multicast=yes port=MII speed=10Mbit/s resources: irq:18 ioport:c000(size=128) memory:f711-f71101ff memory:f710-f710 It works normal on Linux 4.15.0-47-generic but not working on Linux 4.15.0-48-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826831/+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 1828227] Re: shiftfs: allow changing ro/rw for subvolumes
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1828227 Title: shiftfs: allow changing ro/rw for subvolumes Status in linux package in Ubuntu: Expired Bug description: Unprivileged users can already toggle whether a subvolume will be ro or rw. Not having this working with shiftfs regresses various use-cases. Issues have already been seen by Stéphane Graber (Cced here). To enable this with shiftfs we need to whitelist BTRFS_IOC_FS_INFO, BTRFS_IOC_SUBVOL_GETFLAGS, BTRFS_IOC_SUBVOL_SETFLAGS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828227/+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 1782608] Re: Fresh Ubuntu 18.04 install uses wrong Realtek wired network driver.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1782608 Title: Fresh Ubuntu 18.04 install uses wrong Realtek wired network driver. Status in linux package in Ubuntu: Expired Bug description: Hi there, Installing Ubuntu 18.04 on my newish laptop which contains a Realtek 8168 NIC seems to use the r8169 driver by default, and should use the r8168 in order to work properly. To fix, I removed or blocked the 8169 driver, installed the 8168 driver and then reconfigured NetworkManager - which was quite difficult for a new user like me. I've included details from my system since I addressed the issue yesterday. Please let me know if there's anything I can do to help more. ~$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ~$ apt-cache policy r8168-dkms r8168-dkms: Installed: 8.045.08-2 Candidate: 8.045.08-2 Version table: *** 8.045.08-2 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status ~$ neofetch OS: Ubuntu 18.04 LTS x86_64 Host: Aspire A515-51G V1.10 Kernel: 4.15.0-23-generic Uptime: 30 mins Packages: 2124 Shell: bash 4.4.19 Resolution: 1920x1080 Terminal: gnome-terminal CPU: Intel i5-8250U (8) @ 3.400GHz GPU: Intel UHD Graphics 620 GPU: NVIDIA GeForce MX150 Memory: 3457MiB / 7725MiB ~$ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0.1 bus info: pci@:02:00.1 logical name: enp2s0f1 version: 12 serial: 98:29:a6:40:b5:f1 size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.045.08-NAPI duplex=half latency=0 link=no multicast=yes port=twisted pair speed=10Mbit/s resources: irq:128 ioport:3000(size=256) memory:a4204000-a4204fff memory:a420-a4203fff ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Jul 19 09:56:08 2018 Dependencies: InstallationDate: Installed on 2018-07-16 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782608/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 6 (for the Disco kernel) commit: 'Revert "bcache: set CACHE_SET_IO_DISABLE in bch_cached_dev_error()"' Problem: if one backing device hits I/O errors the cache device is disabled, but if that cache device is shared by other bcache devices they stop too (even with non-failing backing devices). Original kernel: all bcache devices that share cache device with failing backing device are stopped. Modified kernel: only the bcache device with the failing backing device is stopped. Original kernel: --- root@bionic-bcache:~# uname -rv 5.0.0-21-generic #22-Ubuntu SMP Tue Jul 2 13:27:33 UTC 2019 root@bionic-bcache:~# ./setup-two-bcache-one-cache.sh >/dev/null 2>&1 [ 23.323929] bcache: register_bdev() registered backing device dm-0 [ 23.330821] bcache: register_bdev() registered backing device dm-1 [ 23.335493] bcache: run_cache_set() invalidating existing data [ 23.347255] bcache: register_cache() registered cache device dm-2 [ 24.335738] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set f816e09d-f744-4fc9-b3bd-239f3d5093c6 [ 24.342388] bcache: bch_cached_dev_attach() Caching dm-1 as bcache1 on set f816e09d-f744-4fc9-b3bd-239f3d5093c6 root@bionic-bcache:~# lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk loop2 7:201G 0 loop └─fake-loop2 253:20 1024M 0 dm ├─bcache0 251:00 1024M 0 disk └─bcache1 251:128 0 1024M 0 disk # echo writeback | tee /sys/block/bcache*/bcache/cache_mode writeback # echo always | tee /sys/block/bcache*/bcache/stop_when_cache_set_failed always root@bionic-bcache:~# ./dm_fake_dev.sh /dev/loop0 bad [ 58.915344] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 58.921948] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 58.928886] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 58.931006] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.936386] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.939346] Buffer I/O error on dev bcache0, logical block 262112, async page read root@bionic-bcache:~# [ 58.944685] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.948468] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 58.951078] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.954231] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 58.957216] Buffer I/O error on dev bcache0, logical block 1, async page read # ./dm_fake_dev.sh /dev/loop0 bad [ 167.341298] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 167.347802] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 167.354959] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 167.356585] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.364784] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.369083] Buffer I/O error on dev bcache0, logical block 262112, async page read root@bionic-bcache:~# [ 167.376976] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.381644] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 167.384195] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.387144] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 167.390040] Buffer I/O error on dev bcache0, logical block 1, async page read root@guest-bcache:~# dd if=/dev/zero of=/dev/bcache1 bs=4k & dd if=/dev/zero of=/dev/bcache0 bs=4k & [1] 1464 [2] 1465 root@bionic-bcache:~# [ 178.103060] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 178.107790] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 178.111814] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 178.116428] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 178.119286] bcache:
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
[D/E][PATCH 0/1] LP#1829563 bcache: pending patch for Disco/Eoan https://lists.ubuntu.com/archives/kernel-team/2019-July/102006.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of many patches with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4) and fio (sequential + random read-write). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Unknown Bug description: If you don't use mousewheel or touchpad everything will be fast and responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+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 1835614] Re: Touchpad not recognized
Looks like a duplicate to bug 1835150. Please try linux-oem-osp1 version 5.0.0-1013.14 from eoan-proposed, which should have included the fix. https://launchpad.net/ubuntu/+source/linux-oem-osp1/5.0.0-1013.14 -- 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/1835614 Title: Touchpad not recognized Status in linux package in Ubuntu: Confirmed Bug description: I have an Ubuntu 19.04 installed on HP Omen 15ce-006nk I can not use the touchpad, it seems unrecognized by the OS I attached the output of cat /proc/bus/input/devices > devices ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-20-generic 5.0.0-20.21 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: exo1549 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 6 16:40:01 2019 InstallationDate: Installed on 2019-07-02 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:58e6 Realtek Semiconductor Corp. Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=5c61d159-7664-4d88-86c0-b3884c70e5df ro acpi=off i18042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.08:bd09/29/2017:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 2HQ17EA#BH4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835614/+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 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]
@klfyt, please understand you must share as much information with other as possible if you need other people to help without the hardware. It's already difficult to work without physical access to the target, let alone not having any log, details from you. Changing the status to CONFIRMED doesn't mean a lot, but uploading logs as suggested by launchpad/bugzilla would. -- 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/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Unknown Bug description: If you don't use mousewheel or touchpad everything will be fast and responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+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 1830358] Re: Screen flickering
Thanks for the video! This kind of flickering is going to be low-level. So we should look at the kernel log. If the kernel driver isn't reporting errors then it would probably be a hardware fault. Please wait until the problem happens again and then run: dmesg > dmesgonflicker.txt and send us the file 'dmesgonflicker.txt'. ** Package changed: ubuntu => linux (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/1830358 Title: Screen flickering Status in linux package in Ubuntu: Incomplete Bug description: Using Intel Graphics HD 520 Constant flickering begins after some usage. Rebooting resolves the issue for a short while. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 24 06:42:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704] InstallationDate: Installed on 2019-04-05 (49 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=26ae1f0c-87cf-450a-82e8-a4034f51425d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830358/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
[C][PATCH 0/2] LP#1829563 bcache: pending patches for Cosmic https://lists.ubuntu.com/archives/kernel-team/2019-July/102001.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of many patches with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4) and fio (sequential + random read-write). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 6 (for the Cosmic kernel) commit: 'Revert "bcache: set CACHE_SET_IO_DISABLE in bch_cached_dev_error()"' Problem: if one backing device hits I/O errors the cache device is disabled, but if that cache device is shared by other bcache devices they stop too (even with non-failing backing devices). Original kernel: all bcache devices that share cache device with failing backing device are stopped. Modified kernel: only the bcache device with the failing backing device is stopped. Original kernel --- root@guest-bcache:~# uname -rv 4.18.0-23-generic #24-Ubuntu SMP Wed Jun 12 18:17:39 UTC 2019 root@guest-bcache:~# lsblk -e 252 root@guest-bcache:~# root@guest-bcache:~# ./setup-two-bcache-one-cache.sh >/dev/null 2>&1 [ 35.686002] bcache: register_bdev() registered backing device dm-0 [ 35.695980] bcache: register_bdev() registered backing device dm-1 [ 35.704662] bcache: run_cache_set() invalidating existing data [ 35.719046] bcache: register_cache() registered cache device dm-2 [ 36.705686] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set fce8d558-4657-47dc-ab37-226ada14daf5 [ 36.711827] bcache: bch_cached_dev_attach() Caching dm-1 as bcache1 on set fce8d558-4657-47dc-ab37-226ada14daf5 root@guest-bcache:~# lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk loop2 7:201G 0 loop └─fake-loop2 253:20 1024M 0 dm ├─bcache0 251:00 1024M 0 disk └─bcache1 251:128 0 1024M 0 disk root@guest-bcache:~# echo writeback | tee /sys/block/dm-*/bcache/cache_mode writeback root@guest-bcache:~# cat /sys/block/dm-*/bcache/cache_mode writethrough [writeback] writearound none writethrough [writeback] writearound none root@guest-bcache:~# ./dm_fake_dev.sh /dev/loop0 bad [ 76.875749] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 76.882159] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 76.889453] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 76.892183] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.904907] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.907711] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 76.912607] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.916905] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 76.920345] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.924767] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 76.928404] Buffer I/O error on dev bcache0, logical block 1, async page read root@guest-bcache:~# dd if=/dev/zero of=/dev/bcache1 bs=4k & dd if=/dev/zero of=/dev/bcache0 bs=4k & [ 175.024811] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 175.029844] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.034652] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 175.037465] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.040373] Buffer I/O error on dev bcache0, logical block 2, lost async page write ... [ 175.092196] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.096635] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.101272] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.105829] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable ... [ 175.235700] bcache: bch_count_backing_io_errors() dm-0: IO error on backing device, unrecoverable [ 175.239457] bcache: bch_cached_dev_error() stop bcache0: too many IO errors on backing device dm-0 [ 175.239457] [ 175.324069] bcache: bch_cache_set_error() CACHE_SET_IO_DISABLE already set [ 175.328998] bcache: error on fce8d558-4657-47dc-ab37-226ada14daf5: [ 175.328999] journal io error [ 175.331022] , disabling caching [ 175.334264] bcache: conditional_stop_bcache_device() stop_when_cache_set_failed of bcache0 is "auto" and cache is dirty, stop it to avoid potential data corruption. [ 175.338865] bcache: conditional_stop_bcache_device() stop_when_cache_set_failed of bcache1 is "auto" and cache is dirty, stop it to avoid potential data corruption. [ 175.344097] bcache: cached_dev_detach_finish() Caching disabled for dm-1 [ 176.080139] bcache:
[Kernel-packages] [Bug 1830358] [NEW] Screen flickering
You have been subscribed to a public bug: Using Intel Graphics HD 520 Constant flickering begins after some usage. Rebooting resolves the issue for a short while. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 24 06:42:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704] InstallationDate: Installed on 2019-04-05 (49 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=26ae1f0c-87cf-450a-82e8-a4034f51425d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic ubuntu -- Screen flickering https://bugs.launchpad.net/bugs/1830358 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 7
commit: "bcache: fix ioctl in flash device"
This test needs QEMU+GDB since there's no way to set the variable
from the kernel, because it references incorrect memory/pointer.
In the original kernel, the ioctl() to a flash-only volume
goes from ioctl_dev() down to flash_dev_ioctl()
(which always return -ENOTTY always) only if its backing device
has io_disable == 0, but gets -EIO if io_disable == 1
(which are both wrong as flash device has no backing device).
In the modified kernel, it always go down to flash_dev_ioctl(),
thus -ENOTTY in both cases.
Original kernel:
$ uname -rv
4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019
io_disable = 0:
# ./ioctl
ioctl: Inappropriate ioctl for device
io_disable = 1:
# ./ioctl
ioctl: Input/output error
Modified kernel:
# uname -rv
4.18.0-23-generic #24+test20190619b1 SMP Wed Jun 19 22:33:22 UTC 2019
io_disable = 0:
# ./ioctl
ioctl: Inappropriate ioctl for device
io_disable = 1:
# ./ioctl
ioctl: Inappropriate ioctl for device
Steps
-
$ sudo -i
# ./setup.sh >/dev/null 2>&1
[ 57.607391] bcache: register_bdev() registered backing device dm-0
[ 57.611885] bcache: run_cache_set() invalidating existing data
[ 57.625712] bcache: register_cache() registered cache device dm-1
[ 58.605153] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set
08f1756b-081f-4545-a947-927d429f7ef1
# lsblk -e 252
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:001G 0 loop
└─fake-loop0 253:00 1024M 0 dm
└─bcache0 251:00 1024M 0 disk
loop1 7:101G 0 loop
└─fake-loop1 253:10 1024M 0 dm
└─bcache0 251:00 1024M 0 disk
# echo $((128*1024**2)) > /sys/block/dm-1/bcache/set/flash_vol_create
# lsblk -e 252
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:001G 0 loop
└─fake-loop0 253:00 1024M 0 dm
└─bcache0 251:00 1024M 0 disk
loop1 7:101G 0 loop
└─fake-loop1 253:10 1024M 0 dm
├─bcache0 251:00 1024M 0 disk
└─bcache1 251:128 0 128M 0 disk
# ls -1d /sys/block/bcache1/bcache/cache/volume*
/sys/block/bcache1/bcache/cache/volume1
# cat /sys/module/bcache/sections/.text
0xc05f4000
# cat ioctl.c
#include
#include
#include
#include
int main() {
int fd, rc;
fd = open("/dev/bcache1", O_RDWR);
if (fd == -1) {
perror("open");
return 0;
}
rc = ioctl(fd, 0xcc00ffee); // our cookie.
if (rc == -1)
perror("ioctl");
close(fd);
return 0;
}
# gcc -o ioctl ioctl.c
# ./ioctl
(gdb) add-symbol-file
~/ddeb-4.18.0-23-generic/usr/lib/debug/lib/modules/4.18.0-23-generic/kernel/drivers/md/bcache/bcache.ko
0xc05f4000
(gdb) b *ioctl_dev +0x13
(gdb) c
Thread 4 hit Breakpoint 1, ioctl_dev (b=, mode=134610975,
cmd=3422617582, arg=2) at
/build/linux-JHFGaE/linux-4.18.0/drivers/md/bcache/super.c:641
...
(gdb) p/x 3422617582
$53 = 0xcc00ffee // our cookie.
(gdb) print d.name
$54 = "volume1\000\000\000\000" // matches the volume above.
See it's an incorrect pointer.
No way to set it via any io_disable in sysfs.
(gdb) print ((struct cached_dev *)((void *)d - 0x10)).backing_dev_name
$75 =
"\017\000\000\000\260\373\212s\277\230\377\377\260\373\212s\277\230\377\377
nԇ\377\377\377\377\060qh\211"
(gdb) print ((struct cached_dev *)((void *)d - 0x10)).io_disable
$76 = 0
With the default value (io_disable = 0):
# ./ioctl
ioctl: Inappropriate ioctl for device
(gdb) c
... repeat.
With the forced value (io_disable = 1):
(gdb) set ((struct cached_dev *)((void *)d - 0x10)).io_disable = 1
(gdb) c
# ./ioctl
ioctl: Input/output error
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829563
Title:
bcache: risk of data loss on I/O errors in backing or caching devices
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
[Impact]
* The bcache code in Bionic lacks several fixes to handle
I/O errors in both backing devices and caching devices.
* Partial or permanent errors in backing or caching devices,
specially in writeback mode, can lead to data loss and/or
the application is not notified about failed I/O requests.
* The bcache device might remain available for I/O requests
even if backing device is offline, so writes are undefined.
[Test Case]
* Detailed test cases/steps for the behavior of many patches
with code logic changes are provided in bug comments.
* The patchset has been tested for regressions on each cache
mode (writethrough, writeback, writearound, none) with the
xfstests test suite (on ext4) and fio (sequential + random
read-write).
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
[B][PATCH 00/11] LP#1829563 bcache: risk of data loss on I/O errors in backing or caching devices https://lists.ubuntu.com/archives/kernel-team/2019-July/101989.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of many patches with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4) and fio (sequential + random read-write). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Description changed: [Impact] - * The bcache code in Bionic lacks several fixes to handle -I/O errors in both backing devices and caching devices. + * The bcache code in Bionic lacks several fixes to handle + I/O errors in both backing devices and caching devices. - * Partial or permanent errors in backing or caching devices, -specially in writeback mode, can lead to data loss and/or -the application is not notified about failed I/O requests. + * Partial or permanent errors in backing or caching devices, + specially in writeback mode, can lead to data loss and/or + the application is not notified about failed I/O requests. - * The bcache device might remain available for I/O requests -even if backing device is offline, so writes are undefined. + * The bcache device might remain available for I/O requests + even if backing device is offline, so writes are undefined. [Test Case] - * Detailed test cases/steps for the behavior of almost every -patch with code logic changes are provided in bug comments. + * Detailed test cases/steps for the behavior of almost every + patch with code logic changes are provided in bug comments. - * The patchset has been tested for regressions on each cache -mode (writethrough, writeback, writearound, none) with the -xfstests test suite (on ext4), fio (random read-write) and -iozone (several read/write tests). + * The patchset has been tested for regressions on each cache + mode (writethrough, writeback, writearound, none) with the + xfstests test suite (on ext4) and fio (sequential + random +read-write). [Regression Potential] - * The patchset is relatively large and touches several areas -in bcache code, however, synthetic testing of the patches -has been performed, and extensive regression/stress tests -were run (as mentioned in Test Case section). + * The patchset is relatively large and touches several areas + in bcache code, however, synthetic testing of the patches + has been performed, and extensive regression/stress tests + were run (as mentioned in Test Case section). - * Many patches in the patchset are 'Fixes' patches to other -patches, and no further 'Fixes' currently exist upstream. + * Many patches in the patchset are 'Fixes' patches to other + patches, and no further 'Fixes' currently exist upstream. [Other Info] - * Canonical Field Eng. deploys bcache+writeback extensively -(e.g., BootStack, UA cloud, except rare all-flash cases). - + * Canonical Field Eng. deploys bcache+writeback extensively + (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. ** Description changed: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] - * Detailed test cases/steps for the behavior of almost every - patch with code logic changes are provided in bug comments. + * Detailed test cases/steps for the behavior of many patches + with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4) and fio (sequential + random -read-write). + read-write). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. -- You
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 1 commit "bcache: add CACHE_SET_IO_DISABLE to struct cache_set flags" Problem: the cacheset is not retired immediately on I/O errors in cache device if I/O requests keep coming. Original kernel: bcache device remains on top of caching device, and 'fio' never finishes. Modified kernel: bcache device is removed from caching device, and fio finishes. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup.sh >/dev/null 2>&1 [ 285.677682] bcache: register_bdev() registered backing device dm-0 [ 285.697006] bcache: run_cache_set() invalidating existing data [ 285.710938] bcache: register_cache() registered cache device dm-1 [ 287.686924] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set c589879b-b1c3-49b3-9603-9795ddc750f5 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # ./dm_fake_dev.sh /dev/loop1 bad [ 766.102586] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 766.107602] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 766.113889] bcache: register_bcache() error /dev/dm-1: device already registered On another shell: # fio --name=write --rw=randwrite --filename=/dev/bcache0 --bs=4k --iodepth=8 --ioengine=libaio --runtime=300s --continue_on_error=all write: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=8 fio-3.1 Starting 1 process Jobs: 1 (f=1): [f(1)][100.0%][r=0KiB/s,w=0KiB/s][r=0,w=0 IOPS][eta 00m:00s] < fio never finishes, keeps showing the last line above > < console prints as below when fio starts running > [ 777.451177] bcache: bch_count_io_errors() dm-1: IO error on writing btree, recovering [ 777.490882] bcache: error on c589879b-b1c3-49b3-9603-9795ddc750f5: [ 777.490885] journal io error [ 777.494087] , disabling caching [ 807.900700] bcache: bch_count_io_errors() dm-1: IO error on writing btree, recovering (error msgs looping) bcache0 still present on top of cache device (fake-loop1) # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop fake-loop1 253:101G 0 dm └─bcache0251:00 1024M 0 disk Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # ./setup.sh >/dev/null 2>&1 [ 60.542088] bcache: register_bdev() registered backing device dm-0 [ 60.550509] bcache: run_cache_set() invalidating existing data [ 60.560109] bcache: register_cache() registered cache device dm-1 [ 62.548849] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set f6833a2c-53e6-468e-bf1d-a9f48b73d783 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # ./dm_fake_dev.sh /dev/loop1 bad [ 72.639185] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 72.644876] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 72.650707] bcache: register_bcache() error /dev/dm-1: device already registered On another shell: # fio --name=write --rw=randwrite --filename=/dev/bcache0 --bs=4k --iodepth=8 --ioengine=libaio --runtime=300s --continue_on_error=all [ 97.858468] bcache: bch_count_io_errors() dm-1: IO error on writing btree, recovering [ 97.868519] bcache: error on f6833a2c-53e6-468e-bf1d-a9f48b73d783: [ 97.868520] journal io error [ 97.869998] , disabling caching [ 97.871441] bcache: conditional_stop_bcache_device() stop_when_cache_set_failed of bcache0 is "auto" and cache is clean, keep it alive. [ 97.874423] Buffer I/O error on dev bcache0, logical block 2814, lost async page write [ 97.878697] Buffer I/O error on dev bcache0, logical block 2816, lost async page write [ 97.881702] Buffer I/O error on dev bcache0, logical block 2817, lost async page write [ 97.884790] Buffer I/O error on dev bcache0, logical block 2818, lost async page write [ 97.887709] Buffer I/O error on dev bcache0, logical block 2819, lost async page write [ 97.890558] Buffer I/O error on dev bcache0, logical block 2820, lost async page write [ 97.892419] Buffer I/O error on dev bcache0, logical block 2821, lost async page write [ 97.894228] Buffer I/O error on dev bcache0, logical block 2822, lost async page write [ 97.896107] Buffer I/O error on dev bcache0, logical block 2823, lost async page write [
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 4 commit "bcache: add io_disable to struct cached_dev" Problem: in case of the backing device hits I/o errors or is disconected, the I/O can still be accepted to the bcache device. Original kernel: dd writes in writeback mode to failed backing device complete. Modified kernel: the bcache0 device is removed after some I/O errors in backing device. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup.sh >/dev/null 2>&1 [ 24.820401] bcache: register_bdev() registered backing device dm-0 [ 24.833268] bcache: run_cache_set() invalidating existing data [ 24.848314] bcache: register_cache() registered cache device dm-1 [ 26.824645] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set dd465fa7-4e85-484b-89dd-353c24c6b041 # echo writeback > /sys/block/bcache0/bcache/cache_mode # cat /sys/block/bcache0/bcache/cache_mode writethrough [writeback] writearound none # ./dm_fake_dev.sh /dev/loop0 bad [ 41.439684] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 41.445284] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 41.451846] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 41.454704] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 41.457685] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 41.457743] Buffer I/O error on dev bcache0, logical block 1, async page read # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 49.048036] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 49.051702] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 49.054062] Buffer I/O error on dev bcache0, logical block 2, lost async page write [ 49.056466] Buffer I/O error on dev bcache0, logical block 3, lost async page write [ 49.058867] Buffer I/O error on dev bcache0, logical block 4, lost async page write [ 49.072020] Buffer I/O error on dev bcache0, logical block 5, lost async page write [ 49.074440] Buffer I/O error on dev bcache0, logical block 6, lost async page write [ 49.078658] Buffer I/O error on dev bcache0, logical block 7, lost async page write [ 49.079008] Buffer I/O error on dev bcache0, logical block 6834, lost async page write [ 49.079022] Buffer I/O error on dev bcache0, logical block 6835, lost async page write dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 2.58342 s, 416 MB/s # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 62.696034] buffer_io_error: 260992 callbacks suppressed [ 62.696037] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 62.701996] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 62.704394] Buffer I/O error on dev bcache0, logical block 2, lost async page write [ 62.706763] Buffer I/O error on dev bcache0, logical block 3, lost async page write [ 62.716025] Buffer I/O error on dev bcache0, logical block 4, lost async page write [ 62.718421] Buffer I/O error on dev bcache0, logical block 5, lost async page write [ 62.720821] Buffer I/O error on dev bcache0, logical block 6, lost async page write [ 62.723193] Buffer I/O error on dev bcache0, logical block 7, lost async page write [ 62.725584] Buffer I/O error on dev bcache0, logical block 8, lost async page write [ 62.725763] Buffer I/O error on dev bcache0, logical block 5405, lost async page write dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 2.88915 s, 372 MB/s # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 67.700114] buffer_io_error: 290043 callbacks suppressed [ 67.700117] Buffer I/O error on dev bcache0, logical block 40750, lost async page write [ 67.706230] Buffer I/O error on dev bcache0, logical block 40751, lost async page write [ 67.709846] Buffer I/O error on dev bcache0, logical block 40752, lost async page write [ 67.713503] Buffer I/O error on dev bcache0, logical block 40753, lost async page write [ 67.717241] Buffer I/O error on dev bcache0, logical block 40754, lost async page write [ 67.720938] Buffer I/O error on dev bcache0, logical block 40755, lost async page write [ 67.741395] Buffer I/O error on dev bcache0, logical block 40756, lost async page write dd: error writing '/dev/bcache0': No space left on device [ 67.748145] Buffer I/O error on dev bcache0, logical block 40757, lost async page write [ 67.752352] Buffer I/O error on dev bcache0, logical block 41038, lost async page write [ 67.756642] Buffer I/O error on dev bcache0, logical block 41313,
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 2 commit "bcache: add stop_when_cache_set_failed option to backing device" Problem: upon too many io errors on cache device, bcache code retires cache set, but it doesn't stop the bcache device. (in writeback mode, if it continue to write, writes go to backing device directly; next time bcache re-registers, it writes dirty cached data again, overwriting data) Original kernel: bcache device remains available for writes. Modified kernel: bcache device is not available anymore. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup.sh >/dev/null 2>&1 [ 27.427543] bcache: register_bdev() registered backing device dm-0 [ 27.434844] bcache: run_cache_set() invalidating existing data [ 27.445652] bcache: register_cache() registered cache device dm-1 [ 29.435245] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set 68e969a1-0f60-4978-a109-b48559970472 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # echo writeback > /sys/block/bcache0/bcache/cache_mode # dd if=/dev/zero of=/dev/bcache0 bs=4k dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 5.14109 s, 209 MB/s # ./dm_fake_dev.sh /dev/loop1 bad [ 135.316335] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 135.330181] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 135.337019] bcache: register_bcache() error /dev/dm-1: device already registered # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 142.754766] bcache: error on 68e969a1-0f60-4978-a109-b48559970472: [ 142.754769] journal io error [ 142.757583] , disabling caching dd: error writing '/dev/bcache0': No space left on device [ 143.299557] bcache: bch_count_io_errors() dm-1: IO error on reading dirty data from cache, recovering [ 143.305560] bcache: bch_count_io_errors() dm-1: IO error on reading dirty data from cache, recovering [ 143.308463] bcache: bch_count_io_errors() dm-1: IO error on reading dirty data from cache, recovering # ./dm_fake_dev.sh /dev/loop1 good [ 171.220172] bcache: bch_count_io_errors() dm-1: IO error on reading dirty data from cache, recovering [ 171.426360] bcache: register_bcache() error /dev/dm-1: device already registered 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 32.066 s, 33.5 MB/s dd: closing input file '/dev/zero': Bad file descriptor # # [ 174.589309] bcache: cached_dev_detach_finish() Caching disabled for dm-0 [ 174.599062] bcache: cache_set_free() Cache set 68e969a1-0f60-4978-a109-b48559970472 unregistered # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # ./setup.sh >/dev/null 2>&1 [ 39.981825] bcache: register_bdev() registered backing device dm-0 [ 39.987359] bcache: run_cache_set() invalidating existing data [ 40.000743] bcache: register_cache() registered cache device dm-1 [ 41.985275] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set 9b509864-84be-428e-ad8a-293d546ec2e9 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # echo writeback > /sys/block/bcache0/bcache/cache_mode # dd if=/dev/zero of=/dev/bcache0 bs=4k dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 5.96102 s, 180 MB/s # ./dm_fake_dev.sh /dev/loop1 bad [ 81.798129] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 81.804533] Buffer I/O error on dev dm-1, logical block 262128, async page read [ 81.810630]
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 5 commit "bcache: stop bcache device when backing device is offline" Problem: bcache is unaware that a backing device goes offline, and accepts writes. Original kernel: bcache doesn't realize backing device is offline. Modified kernel: bcache device is removed after backing device is offline. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # apt install -y linux-modules-extra-$(uname -r)=4.15.0-55.60 # modprobe scsi_debug dev_size_mb=1024 # dmesg | tail [ 17.339336] scsi host2: scsi_debug: version 1.86 [20160430] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 17.339667] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0186 PQ: 0 ANSI: 7 [ 17.339989] sd 2:0:0:0: Power-on or device reset occurred [ 17.340184] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 17.348436] sd 2:0:0:0: [sda] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB) [ 17.352496] sd 2:0:0:0: [sda] Write Protect is off [ 17.352501] sd 2:0:0:0: [sda] Mode Sense: 73 00 10 08 [ 17.360686] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 17.451956] sd 2:0:0:0: [sda] Attached SCSI disk # ./setup-sda.sh >/dev/null 2>&1 [ 37.515474] bcache: run_cache_set() invalidating existing data [ 37.527275] bcache: register_cache() registered cache device dm-0 [ 37.625160] bcache: register_bdev() registered backing device sda [ 38.466997] bcache: bch_cached_dev_attach() Caching sda as bcache0 on set 0e23e266-6032-4700-a4c9-464964ed1349 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk sda8:001G 0 disk └─bcache0251:00 1024M 0 disk # echo writeback > /sys/block/sda/bcache/cache_mode # echo 1 > /sys/block/sda/device/delete [ 77.878624] sd 2:0:0:0: [sda] Synchronizing SCSI cache # sleep 10 # # dd if=/dev/zero of=/dev/bcache0 bs=4k [ 120.268072] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 120.271978] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 120.274554] Buffer I/O error on dev bcache0, logical block 2, lost async page write [ 120.276671] Buffer I/O error on dev bcache0, logical block 3, lost async page write [ 120.278760] Buffer I/O error on dev bcache0, logical block 4, lost async page write [ 120.288042] Buffer I/O error on dev bcache0, logical block 5, lost async page write [ 120.290178] Buffer I/O error on dev bcache0, logical block 6, lost async page write [ 120.296043] Buffer I/O error on dev bcache0, logical block 7, lost async page write [ 120.298167] Buffer I/O error on dev bcache0, logical block 8, lost async page write [ 120.300220] Buffer I/O error on dev bcache0, logical block 3260, lost async page write dd: error writing '/dev/bcache0': No space left on device 262143+0 records in 262142+0 records out 1073733632 bytes (1.1 GB, 1.0 GiB) copied, 3.49705 s, 307 MB/s # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # modprobe scsi_debug dev_size_mb=1024 # dmesg | tail [ 27.855163] scsi host2: scsi_debug: version 1.86 [20160430] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 27.855497] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0186 PQ: 0 ANSI: 7 [ 27.855829] sd 2:0:0:0: Power-on or device reset occurred [ 27.855883] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 27.863979] sd 2:0:0:0: [sda] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB) [ 27.868028] sd 2:0:0:0: [sda] Write Protect is off [ 27.868031] sd 2:0:0:0: [sda] Mode Sense: 73 00 10 08 [ 27.876114] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 27.966877] sd 2:0:0:0: [sda] Attached SCSI disk # # ./setup-sda.sh >/dev/null 2>&1 [ 46.294586] bcache: run_cache_set() invalidating existing data [ 46.306769] bcache: register_cache() registered cache device dm-0 [ 46.400510] bcache: register_bdev() registered backing device sda [ 47.247662] bcache: bch_cached_dev_attach() Caching sda as bcache0 on set d3d7816b-6bd9-4dea-bf0c-4bde76b45f91 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk sda8:001G 0 disk └─bcache0251:00 1024M 0 disk # echo writeback > /sys/block/sda/bcache/cache_mode # echo 1 > /sys/block/sda/device/delete [ 85.713826] sd 2:0:0:0: [sda] Synchronizing SCSI cache # sleep 10 [ 90.428125] bcache: cached_dev_status_update() sda:
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 6 Make sure that if two bcache devices share a cache device, only one bcache device is offlined in case of I/O errors in only one backing device. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup-two-bcache-one-cache.sh >/dev/null 2>&1 [ 20.464988] bcache: register_bdev() registered backing device dm-0 [ 20.474082] bcache: register_bdev() registered backing device dm-1 [ 20.485464] bcache: run_cache_set() invalidating existing data [ 20.496253] bcache: register_cache() registered cache device dm-2 [ 21.478688] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set e247271f-eea4-46ea-8ffe-4b04299a7c24 [ 21.484183] bcache: bch_cached_dev_attach() Caching dm-1 as bcache1 on set e247271f-eea4-46ea-8ffe-4b04299a7c24 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk loop2 7:201G 0 loop └─fake-loop2 253:20 1024M 0 dm ├─bcache0 251:00 1024M 0 disk └─bcache1 251:128 0 1024M 0 disk # echo writeback | tee /sys/block/dm-*/bcache/cache_mode writeback # cat /sys/block/dm-*/bcache/cache_mode writethrough [writeback] writearound none writethrough [writeback] writearound none # ./dm_fake_dev.sh /dev/loop0 bad [ 56.142318] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 56.151754] Buffer I/O error on dev dm-0, logical block 262128, async page read [ 56.158706] bcache: register_bcache() error /dev/dm-0: device already registered (emitting change event) [ 56.161631] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 56.169723] Buffer I/O error on dev bcache0, logical block 262112, async page read [ 56.172303] Buffer I/O error on dev bcache0, logical block 1, async page read root@guest-bcache:~# dd if=/dev/zero of=/dev/bcache1 bs=4k & dd if=/dev/zero of=/dev/bcache0 bs=4k & [1] 1400 [2] 1401 # [ 85.400054] Buffer I/O error on dev bcache0, logical block 0, lost async page write [ 85.403138] Buffer I/O error on dev bcache0, logical block 1, lost async page write [ 85.417864] Buffer I/O error on dev bcache0, logical block 2, lost async page write [ 85.419699] Buffer I/O error on dev bcache0, logical block 3, lost async page write [ 85.421510] Buffer I/O error on dev bcache0, logical block 4, lost async page write [ 85.423301] Buffer I/O error on dev bcache0, logical block 5, lost async page write [ 85.450407] Buffer I/O error on dev bcache0, logical block 6, lost async page write [ 85.452248] Buffer I/O error on dev bcache0, logical block 7, lost async page write [ 85.453980] Buffer I/O error on dev bcache0, logical block 8, lost async page write [ 85.455722] Buffer I/O error on dev bcache0, logical block 9, lost async page write dd: error writing '/dev/bcache0': No space left on device dd: error writing '/dev/bcache1': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 4.23916 s, 253 MB/s [2]+ Exit 1 dd if=/dev/zero of=/dev/bcache0 bs=4k # 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 6.5355 s, 164 MB/s [1]+ Exit 1 dd if=/dev/zero of=/dev/bcache1 bs=4k # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk loop2 7:201G 0 loop └─fake-loop2 253:20 1024M 0 dm ├─bcache0 251:00 1024M 0 disk └─bcache1 251:128 0 1024M 0 disk fake-loop0 253:001G 0 dm └─bcache0251:00 1024M 0 disk Nothing is removed, since no I/O errors are detected. Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # ./setup-two-bcache-one-cache.sh >/dev/null 2>&1 [ 29.341483] bcache: register_bdev() registered backing device dm-0 [ 29.351963] bcache: run_cache_set() invalidating existing data [ 29.365256] bcache: register_cache() registered cache device dm-2 [ 29.365566] bcache: register_bdev() registered backing device dm-1 [ 30.357267] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set ee57b847-da70-4b65-888b-e5795ecf6c46 [ 30.363117] bcache: bch_cached_dev_attach() Caching dm-1 as bcache1 on set ee57b847-da70-4b65-888b-e5795ecf6c46 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache1 251:128 0 1024M 0 disk
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
I/O Error Test 3 commit "bcache: fix inaccurate io state for detached bcache devices" Probçem: on detached bcache devices, iostat reports non-zero 'avgqu-sz' and '%util' even after IO stopped. Original kernel: iostat fields are non-zero on I/O idle. Modified kernel: iostat fields are all zero on I/O idle. Original # uname -rv 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 # ./setup.sh >/dev/null 2>&1 [ 118.371172] bcache: register_bdev() registered backing device dm-0 [ 118.377221] bcache: run_cache_set() invalidating existing data [ 118.386614] bcache: register_cache() registered cache device dm-1 [ 120.373682] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set 4f2b6518-1a58-42e0-8720-42b535cb826f # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # echo 1 > /sys/block/bcache0/bcache/detach [ 131.847360] bcache: cached_dev_detach_finish() Caching disabled for dm-0 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm # dd if=/dev/zero of=/dev/bcache0 bs=4k dd: error writing '/dev/bcache0': No space left on device 262142+0 records in 262141+0 records out 1073729536 bytes (1.1 GB, 1.0 GiB) copied, 3.86316 s, 278 MB/s # sync # iostat -xy 1 10 /dev/bcache0 | grep bcache0 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 bcache0 0.000.00 0.00 0.00 0.00 0.00 0.00 0.000.000.00 262224.00 0.00 0.00 0.00 100.00 Modified # uname -rv 4.15.0-55-generic #60+test20190703build1bcache1-Ubuntu SMP Wed Jul 3 21:41:37 UTC # ./setup.sh >/dev/null 2>&1 [ 26.923296] bcache: register_bdev() registered backing device dm-0 [ 26.928998] bcache: run_cache_set() invalidating existing data [ 26.940144] bcache: register_cache() registered cache device dm-1 [ 28.920772] bcache: bch_cached_dev_attach() Caching dm-0 as bcache0 on set bf256397-22a4-40ac-8ff3-0026fd28354c # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1 253:10 1024M 0 dm └─bcache0 251:00 1024M 0 disk # echo 1 > /sys/block/bcache0/bcache/detach [ 42.292538] bcache: cached_dev_detach_finish() Caching disabled for dm-0 # lsblk -e 252 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:001G 0 loop └─fake-loop0 253:00 1024M 0 dm └─bcache0 251:00 1024M 0 disk loop1 7:101G 0 loop └─fake-loop1
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "setup-two-bcache-one-cache.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275535/+files/setup-two-bcache-one-cache.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of almost every patch with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4), fio (random read-write) and iozone (several read/write tests). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "setup.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275533/+files/setup.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of almost every patch with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4), fio (random read-write) and iozone (several read/write tests). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "setup-sda.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275534/+files/setup-sda.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of almost every patch with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4), fio (random read-write) and iozone (several read/write tests). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
Tests with I/O errors = The I/O error tests in the caching and backing device have been simulated with the device mapper dm-linear and dm-error targets. The tests are based on the patch messages, which describe a problem and/or expected behavior, so to exercise the change. Comparisons/comments between the original & modified/test kernels are provided in the next comments. The test script initially sets up fake DM devices in 'good' state with the linear target, and later can switch them to 'bad' state with the error target, and back again. (attached script: 'dm_fake_dev.sh') The bcache setup uses the DM devices above (for caching and backing devices) on top of loop devices in a virtual machine for flexibility. (attached script: 'setup.sh') One test uses a scsi-debug SCSI disk as backing device to offline it. (attached script: 'setup-sda.sh') One test uses 2 bcache devices with 1 shared cache device to ensure only one bcache device is stopped if 1 backing device has failures. (attached script: 'setup-two-bcache-one-cache.sh') -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of almost every patch with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4), fio (random read-write) and iozone (several read/write tests). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "test-bcache-cache-modes.fio.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275532/+files/test-bcache-cache-modes.fio.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of almost every patch with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4), fio (random read-write) and iozone (several read/write tests). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
Tests with fio == The fio tool has been run for performance tests on the original and modified kernels in sequential (rw) and random read/write (randrw) on all cache modes available (writethrough, writeback, writearound, none). Summary: no regressions observed, same IOPS and BW metrics, run three times (test1, test2, test3) on 'orig' and 'test'. # fio \ --name=test \ --filename=/dev/bcache0 \ --runtime=180s \ --ioengine=libaio \ --rw=$RW_MODE \ --bs=4k \ --iodepth=16 \ --numjobs=8 \ --group_reporting (attached script: 'test-bcache-cache-modes.fio.sh') Details: --- The bcache device is made of - caching device: 100 GB partition in NVMe drive - backing device: 1 TB partition in SCSI disk $ dpkg -s fio | grep Version: Version: 3.1-1 # grep -e read: -e write: fio.test*/fio.*/fio.test.*.log | sed 's,/fio, fio,g' | sort -s -k4,4 -k3,3 -k2,2 fio.test1 fio.orig fio.test.none.randrw.log: read: IOPS=79, BW=318KiB/s (325kB/s)(55.9MiB/180092msec) fio.test2 fio.orig fio.test.none.randrw.log: read: IOPS=81, BW=328KiB/s (336kB/s)(57.7MiB/180137msec) fio.test3 fio.orig fio.test.none.randrw.log: read: IOPS=80, BW=324KiB/s (331kB/s)(56.9MiB/180142msec) fio.test1 fio.test fio.test.none.randrw.log: read: IOPS=81, BW=326KiB/s (334kB/s)(57.4MiB/180222msec) fio.test2 fio.test fio.test.none.randrw.log: read: IOPS=80, BW=324KiB/s (331kB/s)(56.0MiB/180177msec) fio.test3 fio.test fio.test.none.randrw.log: read: IOPS=77, BW=312KiB/s (319kB/s)(54.8MiB/180103msec) fio.test1 fio.orig fio.test.none.rw.log: read: IOPS=81.8k, BW=319MiB/s (335MB/s)(56.2GiB/180023msec) fio.test2 fio.orig fio.test.none.rw.log: read: IOPS=82.7k, BW=323MiB/s (339MB/s)(56.8GiB/180070msec) fio.test3 fio.orig fio.test.none.rw.log: read: IOPS=82.8k, BW=323MiB/s (339MB/s)(56.9GiB/180006msec) fio.test1 fio.test fio.test.none.rw.log: read: IOPS=83.2k, BW=325MiB/s (341MB/s)(57.1GiB/180035msec) fio.test2 fio.test fio.test.none.rw.log: read: IOPS=85.2k, BW=333MiB/s (349MB/s)(58.5GiB/180030msec) fio.test3 fio.test fio.test.none.rw.log: read: IOPS=82.9k, BW=324MiB/s (339MB/s)(56.9GiB/180003msec) fio.test1 fio.orig fio.test.writearound.randrw.log: read: IOPS=78, BW=315KiB/s (322kB/s)(55.3MiB/180123msec) fio.test2 fio.orig fio.test.writearound.randrw.log: read: IOPS=78, BW=313KiB/s (321kB/s)(55.1MiB/180114msec) fio.test3 fio.orig fio.test.writearound.randrw.log: read: IOPS=81, BW=325KiB/s (333kB/s)(57.2MiB/180108msec) fio.test1 fio.test fio.test.writearound.randrw.log: read: IOPS=81, BW=324KiB/s (332kB/s)(57.0MiB/180107msec) fio.test2 fio.test fio.test.writearound.randrw.log: read: IOPS=78, BW=315KiB/s (323kB/s)(55.4MiB/180069msec) fio.test3 fio.test fio.test.writearound.randrw.log: read: IOPS=78, BW=312KiB/s (320kB/s)(54.9MiB/180109msec) fio.test1 fio.orig fio.test.writearound.rw.log: read: IOPS=81.8k, BW=319MiB/s (335MB/s)(56.2GiB/180046msec) fio.test2 fio.orig fio.test.writearound.rw.log: read: IOPS=81.6k, BW=319MiB/s (334MB/s)(56.0GiB/180004msec) fio.test3 fio.orig fio.test.writearound.rw.log: read: IOPS=82.7k, BW=323MiB/s (339MB/s)(56.8GiB/180002msec) fio.test1 fio.test fio.test.writearound.rw.log: read: IOPS=82.8k, BW=323MiB/s (339MB/s)(56.9GiB/180097msec) fio.test2 fio.test fio.test.writearound.rw.log: read: IOPS=79.6k, BW=311MiB/s (326MB/s)(54.6GiB/180003msec) fio.test3 fio.test fio.test.writearound.rw.log: read: IOPS=81.7k, BW=319MiB/s (335MB/s)(56.1GiB/180056msec) fio.test1 fio.orig fio.test.writeback.randrw.log: read: IOPS=81, BW=327KiB/s (335kB/s)(57.5MiB/180146msec) fio.test2 fio.orig fio.test.writeback.randrw.log: read: IOPS=79, BW=318KiB/s (326kB/s)(55.9MiB/180075msec) fio.test3 fio.orig fio.test.writeback.randrw.log: read: IOPS=80, BW=321KiB/s (329kB/s)(56.5MiB/180103msec) fio.test1 fio.test fio.test.writeback.randrw.log: read: IOPS=80, BW=324KiB/s (331kB/s)(56.9MiB/180082msec) fio.test2 fio.test fio.test.writeback.randrw.log: read: IOPS=79, BW=317KiB/s (325kB/s)(55.8MiB/180106msec) fio.test3 fio.test fio.test.writeback.randrw.log: read: IOPS=79, BW=316KiB/s (324kB/s)(55.6MiB/180144msec) fio.test1 fio.orig fio.test.writeback.rw.log: read: IOPS=72.4k, BW=283MiB/s (297MB/s)(49.7GiB/180097msec) fio.test2 fio.orig fio.test.writeback.rw.log: read: IOPS=97.6k, BW=381MiB/s (400MB/s)(67.1GiB/180238msec) fio.test3 fio.orig fio.test.writeback.rw.log: read: IOPS=82.9k, BW=324MiB/s (339MB/s)(56.9GiB/180002msec) fio.test1 fio.test fio.test.writeback.rw.log: read: IOPS=81.5k, BW=318MiB/s (334MB/s)(55.0GiB/180002msec) fio.test2 fio.test fio.test.writeback.rw.log: read: IOPS=72.1k, BW=282MiB/s (295MB/s)(49.5GiB/180165msec) fio.test3 fio.test fio.test.writeback.rw.log: read: IOPS=81.8k, BW=319MiB/s (335MB/s)(56.2GiB/180037msec) fio.test1 fio.orig fio.test.writethrough.randrw.log: read: IOPS=80, BW=321KiB/s (329kB/s)(56.5MiB/180137msec) fio.test2 fio.orig
[Kernel-packages] [Bug 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "test-bcache-cache-modes.xfstests.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5275531/+files/test-bcache-cache-modes.xfstests.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of almost every patch with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4), fio (random read-write) and iozone (several read/write tests). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
Tests with xfstests === The xfstests test suite has been run on the original and modified kernels -- on all cache modes available (writethrough, writeback, writearound, none). Summary: no regressions observed; apparently one FIX achieved in the writearound cache mode (generic/371). (attached script: 'test-bcache-cache-modes.sh') Details: --- The bcache device is made of - caching device: 1 GB partition in NVMe drive - backing device: 5 GB partition in SCSI disk ubuntu@buneary:~/xfstests-dev$ git log --oneline -1 f769a923 (HEAD -> master, origin/master, origin/HEAD) xfs: project quota ineritance flag test The comparison of the output of xfstests/check script for the 'Failures' with original (orig) and modified (test) test kernels is provided below. # grep ^Failures: xfstests.*/xfstests.*.*.log | sed 's,/, ,' | sort -k 2,2 -k 1,1 xfstests.orig xfstests.test.none.log:Failures: ext4/032 generic/484 generic/491 generic/504 generic/537 xfstests.test xfstests.test.none.log:Failures: ext4/032 generic/484 generic/491 generic/504 generic/537 xfstests.orig xfstests.test.writearound.log:Failures: ext4/032 generic/371 generic/451 generic/484 generic/491 generic/504 generic/537 xfstests.test xfstests.test.writearound.log:Failures: ext4/032 <.> generic/451 generic/484 generic/491 generic/504 generic/537 xfstests.orig xfstests.test.writeback.log:Failures: generic/484 generic/491 generic/504 generic/537 xfstests.test xfstests.test.writeback.log:Failures: generic/484 generic/491 generic/504 generic/537 xfstests.orig xfstests.test.writethrough.log:Failures: ext4/032 generic/484 generic/491 generic/504 generic/537 xfstests.test xfstests.test.writethrough.log:Failures: ext4/032 generic/484 generic/491 generic/504 generic/537 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of almost every patch with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4), fio (random read-write) and iozone (several read/write tests). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 1833319] Re: Performance degradation when copying from LVM snapshot backed by NVMe disk
I enabled -proposed and installed 4.4.0-1088-aws #99-Ubuntu, and again went through the test case on a c5.large instance on aws. The problem is solved and performance is restored, and performs the same as a non-snapshot mounted disk. Again, we can see merging has been enabled with: $ cat /sys/block/nvme1n1/queue/nomerges 0 The problem is fixed. Happy with verification status of 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/1833319 Title: Performance degradation when copying from LVM snapshot backed by NVMe disk Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1833319 [Impact] When copying files from a mounted LVM snapshot which resides on NVMe storage devices, there is a massive performance degradation in the rate sectors are read from the disk. The kernel is not merging sector requests and is instead issuing many small sector requests to the NVMe storage controller instead of one larger request. Experiments have shown a 14x-25x performance degradation in reads, where copies used to take seconds, now take minutes, and copies which took thirty minutes now take many hours. The following was found with btrace, running alongside cat (see Testing): A = IO remapped to different device Q = IO handled by request queue G = Get request U = Unplug request I = IO inserted onto request queue D = IO issued to driver C = IO completion When reading from the LVM snapshot, we see: 259,01 113 0.001117160 1606 A R 837872 + 8 <- (252,0) 835824 259,01 114 0.001117276 1606 Q R 837872 + 8 [cat] 259,01 115 0.001117451 1606 G R 837872 + 8 [cat] 259,01 116 0.001117979 1606 A R 837880 + 8 <- (252,0) 835832 259,01 117 0.001118119 1606 Q R 837880 + 8 [cat] 259,01 118 0.001118285 1606 G R 837880 + 8 [cat] 259,01 122 0.001121613 1606 I RS 837640 + 8 [cat] 259,01 123 0.001121687 1606 I RS 837648 + 8 [cat] 259,01 124 0.001121758 1606 I RS 837656 + 8 [cat] ... 259,01 154 0.001126118 377 D RS 837648 + 8 [kworker/1:1H] 259,01 155 0.001126445 377 D RS 837656 + 8 [kworker/1:1H] 259,01 156 0.001126871 377 D RS 837664 + 8 [kworker/1:1H] ... 259,01 183 0.001848512 0 C RS 837632 + 8 [0] Now what is happening here, is that a request for 8 sector read is placed onto the IO request queue, and is then inserted one at a time to the driver request queue and then fetched by the driver. Comparing this behaviour to reading data from a LVM snapshot on 4.6+ mainline or the Ubuntu 4.15 HWE kernel: M = IO back merged with request on queue 259,00 194 0.000532515 1897 A R 7358960 + 8 <- (253,0) 7356912 259,00 195 0.000532634 1897 Q R 7358960 + 8 [cat] 259,00 196 0.000532810 1897 M R 7358960 + 8 [cat] 259,00 197 0.000533864 1897 A R 7358968 + 8 <- (253,0) 7356920 259,00 198 0.000533991 1897 Q R 7358968 + 8 [cat] 259,00 199 0.000534177 1897 M R 7358968 + 8 [cat] 259,00 200 0.000534474 1897 UT N [cat] 1 259,00 201 0.000534586 1897 I R 7358464 + 512 [cat] 259,00 202 0.000537055 1897 D R 7358464 + 512 [cat] 259,00 203 0.002242539 0 C R 7358464 + 512 [0] This shows us a 8 sector read is added to the request queue, and is then subsequently [M]erged backward with other requests on the queue until the sum of all of those merged requests becomes 512 sectors. From there, the 512 sector read is placed onto the IO queue, where it is fetched by the device driver, and completes. [Fix] The problem is that the NVMe driver on 4.4 xenial kernel is not merging 8 sector requests. Merging is controlled per device by this sysfs entry: /sys/block/nvme1n1/queue/nomerges On 4.4 xenial, reading from this yields 2, or (QUEUE_FLAG_NOMERGES). On 4.6+ and 4.15 HWE kernel, reading from this yields 0, or allowing merge. Setting this to 0 on the 4.4 kernel with: # echo "0" > /sys/block/nvme1n1/queue/nomerges and testing again, we find performance is restored and the problem is fixed. Performing a btrace, we see 8 sector reads get backmerged into a 512 sector read which is done in one go. The problem was fixed in 4.5 upstream with the below commit: commit ef2d4615c59efb312e531a5e949970f37ca1c841 Author: Keith Busch Date: Thu Feb 11 13:05:40 2016 -0700 Subject: NVMe: Allow request merges This commit removes the QUEUE_FLAG_NOMERGES flag from being set during driver init, allowing requests to be
[Kernel-packages] [Bug 1835677] Re: Megal33t bug: touchpad with mousewheel is broken >:]
Hi. Logs aren't needed. >:] ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: Unknown Bug description: If you don't use mousewheel or touchpad everything will be fast and responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+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 1835677] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1835677 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Unknown Bug description: If you don't use mousewheel or touchpad everything will be fast and responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+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 1835677] [NEW] Megal33t bug: touchpad with mousewheel is broken >:]
Public bug reported: If you don't use mousewheel or touchpad everything will be fast and responsive. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Fedora) Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1727563 https://bugzilla.redhat.com/show_bug.cgi?id=1727563 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1727563 Importance: Unknown Status: Unknown -- 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/1835677 Title: Megal33t bug: touchpad with mousewheel is broken >:] Status in linux package in Ubuntu: New Status in linux package in Fedora: Unknown Bug description: If you don't use mousewheel or touchpad everything will be fast and responsive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835677/+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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
In that case I'm keeping this as incomplete, especially since OP (ronso0) has failed to verify with suggestions given by kaihengfeng. I feel like there is some hardware commonality here, and would like to see some hardware specifics as previously requested to better triage this bug. -- 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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+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 988799]
KDE have problem too, same copy via CLI or via Ultracopier (GUI) have no problem. I note too KDE have UI more slow, plasma doing CPU usage in case I use the HDD... -- 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/988799 Title: Precise freezes under heavy i/o Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Whilst creating a VM with 20 GB persistent HD and my system froze until the disk was created. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gema 2526 F pulseaudio /dev/snd/controlC0: gema 2526 F pulseaudio /dev/snd/controlC1: gema 2526 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,104383c4,0010' Controls : 45 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:081d' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 16 Mono: Capture 12 [75%] [24.00dB] [on] Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Thu Apr 26 11:59:11 2012 HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IwConfig: lono wireless extensions. virbr0no wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago) dmi.bios.date: 03/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/988799/+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 988799]
Had this again 20 minutes ago. Was dopying 8.7GiB of data from one directory to another directory on the same filesystem (ext4 (rw,relatime,data=ordered)) on the same disk (Western Digital WDC WD30EZRX-00D8PB0 spinning metal disk). The KDE UI became unresponsive (Everything other than /home and user data in on a SSD), could not launch any new applications. Opening a new tab on Firefox to go to Youtube didnt load the page, and kept saying waiting for youtube.com in the status bar (network gets halted?). dmesg shows these, are they important? [25013.905943] INFO: task DOMCacheThread:17496 blocked for more than 120 seconds. [25013.905945] Tainted: P OE4.15.0-54-generic #58-Ubuntu [25013.905947] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25013.905949] DOMCacheThread D0 17496 2243 0x [25013.905951] Call Trace: [25013.905954] __schedule+0x291/0x8a0 [25013.905957] schedule+0x2c/0x80 [25013.905959] jbd2_log_wait_commit+0xb0/0x120 [25013.905962] ? wait_woken+0x80/0x80 [25013.905965] __jbd2_journal_force_commit+0x61/0xb0 [25013.905967] jbd2_journal_force_commit+0x21/0x30 [25013.905970] ext4_force_commit+0x29/0x2d [25013.905972] ext4_sync_file+0x14a/0x3b0 [25013.905975] vfs_fsync_range+0x51/0xb0 [25013.905977] do_fsync+0x3d/0x70 [25013.905980] SyS_fsync+0x10/0x20 [25013.905982] do_syscall_64+0x73/0x130 [25013.905985] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [25013.905987] RIP: 0033:0x7fc9cb839b07 [25013.905988] RSP: 002b:7fc9a7aeb200 EFLAGS: 0293 ORIG_RAX: 004a [25013.905990] RAX: ffda RBX: 00a0 RCX: 7fc9cb839b07 [25013.905992] RDX: RSI: 7fc9a7aeaff0 RDI: 00a0 [25013.905993] RBP: R08: R09: 72732f656d6f682f [25013.905994] R10: R11: 0293 R12: 01f6 [25013.905995] R13: 7fc97fc5d038 R14: 7fc9a7aeb340 R15: 7fc987523380 -- 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/988799 Title: Precise freezes under heavy i/o Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Whilst creating a VM with 20 GB persistent HD and my system froze until the disk was created. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gema 2526 F pulseaudio /dev/snd/controlC0: gema 2526 F pulseaudio /dev/snd/controlC1: gema 2526 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,104383c4,0010' Controls : 45 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:081d' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 16 Mono: Capture 12 [75%] [24.00dB] [on] Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Thu Apr 26 11:59:11 2012 HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IwConfig: lono wireless extensions. virbr0no wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days
[Kernel-packages] [Bug 1834675] Re: zfs-linux should be updated to 0.8.1
Now released. ** Changed in: zfs-linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1834675 Title: zfs-linux should be updated to 0.8.1 Status in zfs-linux package in Ubuntu: Fix Released Bug description: 0.8.1 is the latest stable version. Eoan should ideally include this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1834675/+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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Actually, happened also with lowlatency-5.0.0-20 on a subsequent boot. But again, after one reboot this did not reproduce. So it is not 10/10 systematical. -- 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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+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 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
Hi Andrea,
Thanks a lot for the test kernel.
https://kernel.ubuntu.com/~arighi/LP-1827884/
I tried it on Laptop ASUS X51 R.
Results:
1. It boots just fine (without nopti boot option.)
2. However, after boot Screen Resolution is fixed to 1024x768.
Native LCD-Resolution with working ATI Radeon Graphics would be 1280x800
(and adjustable)
This is the same effect to when I use my current kernel 4.15.0-51 in
recovery mode.
Boot with 4.15.0.51 using nopti-Kernel-Option results in graphics OK.
Thanks a lot,
Thomas
--
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/1827884
Title:
x86: mm: early boot problem on i386 with KPTI enabled
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
Confirmed
Bug description:
[Impact]
Commit d653420532d580156c8486686899ea6a9eeb7bf0 in bionic enabled
kernel page table isolation for x86_32, but also introduced
regressions. One of them ("BUG_ON() condition in vmalloc_sync_one()")
has been addressed by bug 1830433, but there are other issues reported
on i386.
Specifically on some i386 systems the kernel seems to fail in the
early stage of boot (black screen and frozen keyboard) with no error
reported on the console.
If the kernel is booted with "mitigations=off" and "nopti" the problem
doesn't happen (that is a clear indication of being a kernel page
table isolation issue).
However, users have been reported positive results with the following
upstream fixes applied (all clean cherry picks), even with mitigations
*and* kernel page table isolation enabled.
[Test Case]
Unfortuantely this problem is not easily reproducible, the kernel
simply fails to boot (black screen and frozen keyboard) after the GRUB
prompt, so we don't have a real test case (except asking the bug
reporters to boot the kernel and see if it works).
[Fix]
The following upstream fix seems to resolve (prevent) the problem:
1d8ca3be86ebc6a38dad8236f45c7a9c61681e78 x86/mm/fault: Allow stack access
below %rsp
aa37c51b9421d66f7931c5fdcb9ce80c450974be x86/mm: Break out user address space
handling
8fed6239058adfd8b663344e2f448aed1e7a x86/mm: Break out kernel address
space handling
164477c2331be75d9bd57fb76704e676b2bcd1cd x86/mm: Clarify hardware vs.
software "error_code"
0e664eee65337082be49fbbd2ee24aa0d111d0f2 Revert "perf/core: Make sure the
ring-buffer is mapped in all page-tables"
[Regression Potential]
All upstream fixes, tested on the affected platform, backport changes
are minimal.
[Original bug report]
NOTE: Boot problems on TWO different laptops after Software Updater
updated to kernel 4.15.0-48
Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
desktop. Both fresh installs from minimal CD in early April,
originally kernel 0.4.15.0-47, both working fine.
Bug report filed on THIS MACHINE:
HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel
integrated graphics controller GM965/GL960 (with kernel command line parameter
¨video=SVIDEO-1:d¨)
SYMPTOM:
4.15.0-48 requires a second ´recovery´ boot to get it up and running.
Will not boot properly after a normal shutdown - screen goes funny and it
hangs
Does boot successfully after a hard shutdown - detects improper shutdown,
loads grub menu, then boot successfully
Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots
normally after a normal shutdown)
OTHER MACHINE:
Even older!!! ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility
Radeon 9600 GPU. Running with command line parameter "forcepae".
SYMPTOM:
Won't boot at all.
Was working fine under 4.15.0-47 as originally installed, until software
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I
can't even get into the grub menu to try the older kernel.
More Info on what I've already tried for troubleshooting (on the
HP6710b) is outlined in
https://answers.launchpad.net/ubuntu/+question/680486
Happy to provide more info if needed, but I'm just an end user user
and new to Linux, so will be on a learning curve at this end. (and
apologies in advance if this a user problem, and not an actual bug).
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-48-generic 4.15.0-48.51
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic i686
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: michael1681 F pulseaudio
CurrentDesktop: XFCE
Date: Mon May 6 21:16:34 2019
MachineType: Hewlett-Packard HP Compaq 6710b
PccardctlIdent:
Socket 0:
no product
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: rtirq (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Lassi, thanks for the comment. If that's the case, I'm going to go ahead and mark this bug as "Invalid" for rtirq and "Fix Released" for linux, but I'd love to see more comments first to confirm this. -- 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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Incomplete Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+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 238208] Re: Need MemoryStick driver Ricoh R5C592 (part of R5C832/822chipset)
I have sony vaio vpcs111fm with SD and MS with Ubuntu ubuntu 19.04 64bits. My lspci is: 03:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller 03:00.1 System peripheral: Ricoh Co Ltd R5U2xx (R5U230 / R5U231 / R5U241) [Memory Stick Host Controller] 03:00.3 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 PCIe IEEE 1394 Controller 03:00.4 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller -- 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/238208 Title: Need MemoryStick driver Ricoh R5C592 (part of R5C832/822chipset) Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Status in linux source package in Precise: Fix Released Status in openSUSE: New Bug description: *** NOTE: this is a *wishlist* item - a request for new functionality. This issue is a request to have MemoryStick support added for a specific, and somewhat popular, chipset. Please do not add "me, too" items. We know that it doesn't work. If you want, please add yourself as a subscriber, and click on link to indicate that "This bug effects me, too" You are welcome to test the new developed drivers at http://gitorious.org/ricoh-kernel You can download them ether by doing (preferred): git clone git://gitorious.org/ricoh-kernel/ricoh-kernel.git Then you can receive updates using git pull or you can press on 'Source tree' and download a snapshot by pressing 'Download master as tar.gz' XD support is also done and merged in 2.6.35 (backport in above tree) Running 2.6.24-18, in Hardy 02:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) (prog-if 10 [OHCI]) Subsystem: Dell Unknown device 022f Flags: bus master, medium devsel, latency 64, IRQ 16 Memory at fe3ff800 (32-bit, non-prefetchable) [size=2K] Capabilities: 02:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) (prog-if 01) Subsystem: Dell Unknown device 022f Flags: medium devsel, IRQ 18 Memory at fe3ff400 (32-bit, non-prefetchable) [size=256] Capabilities: 02:09.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12) Subsystem: Dell Unknown device 022f Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at fe3ff500 (32-bit, non-prefetchable) [size=256] Capabilities: 02:09.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) Subsystem: Dell Unknown device 022f Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at fe3ff600 (32-bit, non-prefetchable) [size=256] Capabilities: 02:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff) (prog-if ff) !!! Unknown header type 7f SD cards are detected, but Memory Stick cards are not. Bugs have been posted for the lack of support for XD and MMC cards as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/238208/+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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
I saw this issue with fresh install of Ubuntu Studio 19.04, lowlatency-5.0.0-13 kernel. After upgrade to lowlatency-5.0.0-20 kernel I did not see the issue anymore. -- 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/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Confirmed Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+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 1829220] Re: Add in-kernel support for Realtek 8821CE WiFi device
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1829220 Title: Add in-kernel support for Realtek 8821CE WiFi device Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Confirmed Status in linux source package in Cosmic: Won't Fix Status in linux-oem source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux-oem source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-oem source package in Eoan: Won't Fix Bug description: [Impact] There's no in-kernel support for rtl8821ce. [Fix] Include the driver to kernel. [Test Case] The basic function like scan, connect and transmit packet works. [Regression Potential] None. It's a new driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1829220/+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
Re: [Kernel-packages] [Bug 1832435] Re: Lenovo miix 510 wifi adapter cannot be turned on
Jeremy It appears to have worked. Thank you. Miguel-=-= On Wednesday, July 3, 2019, 6:41:13 PM GMT+8, Jeremy <1832...@bugs.launchpad.net> wrote: See if it can be fixed in Synaptic Package Manager, click Edit, Fix Broken -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware 1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- 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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus
[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: === SRU Justification === [Impact] Screen flickers when using radeon.ko. It's a regression, it didn't happen on Trusty. [Fix] Quote the original commit log: "Instead of the closest reference divider prefer the lowest". [Test] Affected user confirms it fixes the issue. [Regression Potential] Low. Only affect radeaon, and it's in upstream stable tree. === Original Bug Report === my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1791312/+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 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
I've tested the kernel from http://at.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages linux-headers-4.15.0-55-generic Linux kernel headers for version 4.15.0 on 64 bit x86 SMP linux-image-4.15.0-55-generic Signed kernel image generic linux-modules-4.15.0-55-generic Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP linux-modules-extra-4.15.0-55-generic Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP and: NO flickering screen! So the problem seems to be solved! I don't have a cosmic / disco installation, so I can't test these versions. So I set the verification-done-bionic - tag. -- 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/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: === SRU Justification === [Impact] Screen flickers when using radeon.ko. It's a regression, it didn't happen on Trusty. [Fix] Quote the original commit log: "Instead of the closest reference divider prefer the lowest". [Test] Affected user confirms it fixes the issue. [Regression Potential] Low. Only affect radeaon, and it's in upstream stable tree. === Original Bug Report === my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1791312/+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 1827697] Re: Enroll key whiptail prompt blocks kernel header package upgrades
The fix here breaks installing custom kernels, at least on xenial (dkms
(2.2.0.3-2ubuntu11.7) xenial): the redirection of stdout was to there to
fix a problem with dkms output contaminating debconf's input - see
#292606 for details. To be specific, during package install (either via
dpkg or apt-get) I'm now getting the following error from /usr/sbin
/update-grub-legacy-ec2 which is run from /etc/kernel/postinst.d/x-grub-
legacy-ec2 (after running /etc/kernel/postinst.d/dkms):
20 Unsupported command "*" (full line was " * dkms: running auto
installation service for kernel ...") received from confmodule.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1827697
Title:
Enroll key whiptail prompt blocks kernel header package upgrades
Status in dkms package in Ubuntu:
Fix Released
Status in dkms source package in Xenial:
Fix Released
Status in dkms source package in Bionic:
Fix Released
Status in dkms source package in Cosmic:
Fix Released
Status in dkms source package in Disco:
Fix Released
Status in dkms source package in Eoan:
Fix Released
Bug description:
I noticed that sometimes the system upgrade is blocked in the kernel
header package's configure phase, in the process manager I found that
it is blocked by the "Configuring Secure Boot" whiptail prompt started
by `update-secureboot-policy --enroll-key` which doesn't surface to
the terminal and hence not interactable.
Refer the attached screenshot for the process status at the time.
[Test Case]
1. Install any out-of-tree dkms packages (like bbswitch-dkms)
2. Un-enroll keys from MOK, ensure `mokutil --test-key
/var/lib/shim-signed/mok/MOK.der` command returns
"/var/lib/shim-signed/mok/MOK.der is not enrolled"
3. Ensure SecureBoot is enabled
4. Install any linux-headers-${version}-generic packages that is currently
not installed, verify if it stucks at configurating state
[Regression potential]
Since this change will cause the output of dkms_autoinstaller to appear in
the output of the kernel installs, this may surprise consumers of the dpkg log
with its verbosity.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697/+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
