[Kernel-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
Confirm that by switch the mode from HSP/HFP to A2DP Sink solve the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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 1790253] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1790253 Title: ubuntu-bug causes GTK-message Status in linux package in Ubuntu: Confirmed Bug description: ~$ ubuntu-bug update-manager Gtk-Message: 11:31:48.137: GtkDialog mapped without a transient parent. This is discouraged. that appears with others as well: ~$ ubuntu-bug software-updater dpkg-query: no packages found matching software-updater Gtk-Message: 11:29:10.135: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:41:51 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790253/+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 1790254] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1790254 Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: installed linux-image-4.15.0-34-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Error from previous linux-image manual removal. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nls_utf8 qnx4 hfsplus hfs minix ntfs jfs usblp intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_usb_audio snd_hda_codec snd_usbmidi_lib snd_hda_core intel_cstate uvcvideo videobuf2_vmalloc videobuf2_memops intel_rapl_perf videobuf2_v4l2 videobuf2_core videodev media eeepc_wmi asus_wmi sparse_keymap wmi_bmof intel_wmi_thunderbolt mei_me mei shpchp mac_hid nouveau i915 mxm_wmi wmi ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sat Sep 1 13:51:45 2018 ErrorMessage: installed linux-image-4.15.0-34-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-07 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=317600af-4abe-4af4-8baf-c706a06f082f ro quiet splash pci=noaer vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: installed linux-image-4.15.0-34-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790254/+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 1790254] [NEW] package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: installed linux-image-4.15.0-34-generic package pre-removal script subprocess return
Public bug reported: Error from previous linux-image manual removal. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nls_utf8 qnx4 hfsplus hfs minix ntfs jfs usblp intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_usb_audio snd_hda_codec snd_usbmidi_lib snd_hda_core intel_cstate uvcvideo videobuf2_vmalloc videobuf2_memops intel_rapl_perf videobuf2_v4l2 videobuf2_core videodev media eeepc_wmi asus_wmi sparse_keymap wmi_bmof intel_wmi_thunderbolt mei_me mei shpchp mac_hid nouveau i915 mxm_wmi wmi ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sat Sep 1 13:51:45 2018 ErrorMessage: installed linux-image-4.15.0-34-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-07 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=317600af-4abe-4af4-8baf-c706a06f082f ro quiet splash pci=noaer vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: installed linux-image-4.15.0-34-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package bionic package-from-proposed -- 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/1790254 Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: installed linux-image-4.15.0-34-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Error from previous linux-image manual removal. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nls_utf8 qnx4 hfsplus hfs minix ntfs jfs usblp intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_usb_audio snd_hda_codec snd_usbmidi_lib snd_hda_core intel_cstate uvcvideo videobuf2_vmalloc videobuf2_memops intel_rapl_perf videobuf2_v4l2 videobuf2_core videodev media eeepc_wmi asus_wmi sparse_keymap wmi_bmof intel_wmi_thunderbolt mei_me mei shpchp mac_hid nouveau i915 mxm_wmi wmi ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sat Sep 1 13:51:45 2018 ErrorMessage: installed linux-image-4.15.0-34-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-07 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=317600af-4abe-4af4-8baf-c706a06f082f ro quiet splash pci=noaer vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as ses
[Kernel-packages] [Bug 1790253] [NEW] ubuntu-bug causes GTK-message
Public bug reported: ~$ ubuntu-bug update-manager Gtk-Message: 11:31:48.137: GtkDialog mapped without a transient parent. This is discouraged. that appears with others as well: ~$ ubuntu-bug software-updater dpkg-query: no packages found matching software-updater Gtk-Message: 11:29:10.135: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:41:51 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790253 Title: ubuntu-bug causes GTK-message Status in linux package in Ubuntu: New Bug description: ~$ ubuntu-bug update-manager Gtk-Message: 11:31:48.137: GtkDialog mapped without a transient parent. This is discouraged. that appears with others as well: ~$ ubuntu-bug software-updater dpkg-query: no packages found matching software-updater Gtk-Message: 11:29:10.135: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:41:51 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bv
[Kernel-packages] [Bug 1790249] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1790249 Title: desktop sharing won't start after upgrading to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: First time destop sharing was started the system detected a problem which was reported -- so there should be some info for you there already. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:17:29 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790249/+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 1790249] [NEW] desktop sharing won't start after upgrading to 18.04
Public bug reported: First time destop sharing was started the system detected a problem which was reported -- so there should be some info for you there already. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:17:29 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790249 Title: desktop sharing won't start after upgrading to 18.04 Status in linux package in Ubuntu: Confirmed Bug description: First time destop sharing was started the system detected a problem which was reported -- so there should be some info for you there already. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mat1234 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Sep 1 11:17:29 2018 HibernationDevice: RESUME=UUID=45a17e92-d3f6-4bfa-ae68-3c5ebfd44668 InstallationDate: Installed on 2017-02-12 (565 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3000 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c7e2141d-4822-4c3c-94ef-a60343aee094 ro nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-29 (2 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3000:pvr1.x:rvnGIGABYTE:rnMZBSWAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BACE-3000 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1
[Kernel-packages] [Bug 1785481] Re: amdgpu WQHD resolution(2560 × 1440) not available
Donk, to see if this is already resolved in ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Changed in: linux (Ubuntu) Status: Triaged => 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/1785481 Title: amdgpu WQHD resolution(2560 × 1440) not available Status in linux package in Ubuntu: Incomplete Bug description: Hello, I use ubuntu 16.04 with hwe stack and an Radeon R9 285. With kernel 4.13 and older, I can use a resolution of 2560x1440. But, since the upgrade to kernel 4.15, I'm limited to the 1920x1200. I have attached the output of xrandr on both kernel. My screen (Dell U2713HM) is plugged to the output DVI-1. With a kernel 4.13, the output is detected as a DVI-I. But with a kernel 4.15, the output is detected as a DVI-D. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 5 16:46:32 2018 SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to xenial on 2016-12-17 (595 days ago) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frederic 2366 F pulseaudio /dev/snd/controlC1: frederic 2366 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/Fred_SSD-Fred_Swap IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/Fred_SSD-Fred_Root ro quiet ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.157.20 RfKill: Tags: xenial Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-12-17 (596 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare scanner sudo video _MarkForUpload: True dmi.bios.date: 10/28/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3003 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3003:bd10/28/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIRANGER:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785481/+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 159356] Re: When DMA is disabled system freeze on high memory usage
** Summary changed: - System freeze on high memory usage when DMA is disabled + When DMA is disabled system freeze on high memory usage ** Tags removed: patch -- 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/159356 Title: When DMA is disabled system freeze on high memory usage Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 1788321] Re: swapon failed: invalid argument
>> Do you also have to re-run mkswap when switching back to the older, working kernel, or does simply using the other kernel let you run swapon on the same file that doesn't work with the newer kernel? Nope, same swap file / swap partition, without have to re-run mkswap. >> Also what does getconf PAGESIZE say under the broken kernel? Both kernel say 4096 . -- 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/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1790219] [NEW] Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting
Public bug reported: I was carrying out this testcase for proprietary Nvidia drivers testing: http://xorg.qa.ubuntu.com/qatracker/testcases/1704/info. After having installed Ubuntu 18.10 on a new partition on my PC, I switched to Nvidia-driver-390 proprietary driver from Additional Drivers tab of Software & Update and rebooted my PC. On reboot I got low resolution Ubuntu logo, pressing F1 I could read this message: (1 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 23s/ no limit). (2 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 25s/ no limit). I rebooted after waiting 15 minutes as I was tired of waiting. This is my display hardware: *-display description: VGA compatible controller product: GM206 [GeForce GTX 960] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:125 memory:de00-deff memory:c000-cfff memory:d000-d1ff ioport:e000(size=128) memory:c-d Link to the testcase revision Edit result My PC is a: product: XPS 8900 (06B8) vendor: Dell Inc. width: 64 bits ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Project changed: ubuntu-tf101 => nvidia-graphics-drivers-390 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1790219 Title: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I was carrying out this testcase for proprietary Nvidia drivers testing: http://xorg.qa.ubuntu.com/qatracker/testcases/1704/info. After having installed Ubuntu 18.10 on a new partition on my PC, I switched to Nvidia-driver-390 proprietary driver from Additional Drivers tab of Software & Update and rebooted my PC. On reboot I got low resolution Ubuntu logo, pressing F1 I could read this message: (1 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 23s/ no limit). (2 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 25s/ no limit). I rebooted after waiting 15 minutes as I was tired of waiting. This is my display hardware: *-display description: VGA compatible controller product: GM206 [GeForce GTX 960] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:125 memory:de00-deff memory:c000-cfff memory:d000-d1ff ioport:e000(size=128) memory:c-d Link to the testcase revision Edit result My PC is a: product: XPS 8900 (06B8) vendor: Dell Inc. width: 64 bits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790219/+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 1790219] [NEW] Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting
You have been subscribed to a public bug: I was carrying out this testcase for proprietary Nvidia drivers testing: http://xorg.qa.ubuntu.com/qatracker/testcases/1704/info. After having installed Ubuntu 18.10 on a new partition on my PC, I switched to Nvidia-driver-390 proprietary driver from Additional Drivers tab of Software & Update and rebooted my PC. On reboot I got low resolution Ubuntu logo, pressing F1 I could read this message: (1 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 23s/ no limit). (2 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 25s/ no limit). I rebooted after waiting 15 minutes as I was tired of waiting. This is my display hardware: *-display description: VGA compatible controller product: GM206 [GeForce GTX 960] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:125 memory:de00-deff memory:c000-cfff memory:d000-d1ff ioport:e000(size=128) memory:c-d Link to the testcase revision Edit result My PC is a: product: XPS 8900 (06B8) vendor: Dell Inc. width: 64 bits ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting https://bugs.launchpad.net/bugs/1790219 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 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 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
As observed on x86, disabling wayland also avoids the problem on ARM. -- 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/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+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 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
** Attachment added: "arm64-hisilicon-d05-18.04-blurry-syslog.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5183109/+files/arm64-hisilicon-d05-18.04-blurry-syslog.png -- 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/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+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 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
This issue also occurs on arm64. Attached is a screenshot from a HiSilicon D05 running 18.04. Why would hibmc_drm be arm64-specific? It is the same PCI device (19e5:1711), so shouldn't it use the same driver regardless of architecture? ** Attachment added: "arm64-hisilicon-d05-18.04-blurry-screenshot.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5183108/+files/arm64-hisilicon-d05-18.04-blurry-screenshot.png -- 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/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+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 1772467] Re: Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in kernel 4.15.0-20-generic
Tested with kernel 4.15.0-34-generic and for me this kernel solves this bug. Thank you! -- 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/1772467 Title: Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in kernel 4.15.0-20-generic Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Bug description: This is a hardware specific issue with Ubuntu 18.04 and kernel 4.15.0-20-generic. The driver for the Intel AC 9560 wireless chip causes the problem. Driver location: https://www.intel.com/content/www/us/en/support/articles/05511 /network-and-i-o/wireless-networking.html The wifi connection is very slow (1MB instead of 100MB possible download speed, upload speed is normal) and is also very unreliable. When installing the 4.16 kernel from mainline kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/ the described problem is solved. Sytem data: Description: Ubuntu 18.04 LTS Release: 18.04 Package: 4.15.0-20-generic driver=iwlwifi driverversion=4.15.0-20-generic firmware=34.0.0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1729 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-19 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Swift SF114-32 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=39ea17c1-4c91-45ac-81a7-401583763b21 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/02/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Sapporo_GL dmi.board.vendor: GLK dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 1 dmi.product.name: Swift SF114-32 dmi.product.version: V1.03 dmi.sys.vendor: Acer --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-19 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.15.18-041518-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772467/+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 1784172] Re: Touchscreen does not work anymore on dell venue 11 pro 7139 on kernels 4.13 and above
I have just found the issue also here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342 Can you explain why this bug was nominated against a series that is no longer supported? The model 7139 is still supported by Dell. -- 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/1784172 Title: Touchscreen does not work anymore on dell venue 11 pro 7139 on kernels 4.13 and above Status in linux package in Ubuntu: Confirmed Bug description: p@p-Venue-11-Pro-7139:~/$ $ cat ./dmesg_4.12.14.txt | grep i2c [1.953029] i2c /dev entries driver [2.230390] i2c_hid i2c-SMO91D0:00: i2c-SMO91D0:00 supply vdd not found, using dummy regulator [2.338340] i2c_hid i2c-SYNA7500:00: i2c-SYNA7500:00 supply vdd not found, using dummy regulator [4.836205] input: SYNA7500:00 06CB:6D6B Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7500:00/0018:06CB:6D6B.0002/input/input8 [4.836462] input: SYNA7500:00 06CB:6D6B as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7500:00/0018:06CB:6D6B.0002/input/input9 [4.836824] hid-multitouch 0018:06CB:6D6B.0002: input,hidraw2: I2C HID v1.00 Device [SYNA7500:00 06CB:6D6B] on i2c-SYNA7500:00 [4.962323] i2c_hid i2c-SMO91D0:00: failed to retrieve report from device. $ cat ./xinput_4.12.14.txt ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics T Pad V 01.31 Touchpadid=10 [slave pointer (2)] ⎜ ↳ SYNA7500:00 06CB:6D6B id=16 [slave pointer (2)] ⎜ ↳ A4tech Bluetooth 3.0 Mouse 630 id=19 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Webcam id=9[slave keyboard (3)] ↳ Synaptics T Pad V 01.31 id=11 [slave keyboard (3)] ↳ Synaptics T Pad V 01.31 id=12 [slave keyboard (3)] ↳ Integrated_Webcam_8Mid=13 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ SYNA7500:00 06CB:6D6B Pen id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] ↳ Dell WMI hotkeysid=18 [slave keyboard (3)] $ cat ./dmesg_4.13.1.txt | grep i2c [1.970899] i2c /dev entries driver [2.116106] i2c_hid i2c-SMO91D0:00: i2c-SMO91D0:00 supply vdd not found, using dummy regulator [5.060363] i2c_hid i2c-SMO91D0:00: failed to retrieve report from device. cat ./xinput_4.13.1.txt ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics T Pad V 01.31 Touchpadid=10 [slave pointer (2)] ⎜ ↳ A4tech Bluetooth 3.0 Mouse 630 id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Webcam: Integrated W id=9[slave keyboard (3)] ↳ Synaptics T Pad V 01.31 id=11 [slave keyboard (3)] ↳ Synaptics T Pad V 01.31 id=12 [slave keyboard (3)] ↳ Integrated_Webcam_8M: Rear Inte id=13 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Notice missing SYNA7500:00 06CB:6D6B and SYNA7500:00 06CB:6D6B Pen devices. Booting xubuntu 18.04.1 LTS with the old 4.12 kernel solves the issue by now for me. Please help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 Appo
[Kernel-packages] [Bug 1689408] Re: System hang when utilising OpenGL 4.5 features
Launchpad has imported 9 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=100995. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-05-11T02:52:45+00:00 Paul wrote: This is easily reproducible via unigine's heaven benchmark, simply running it with normal tessellation settings results in the screen flashing black a few times and then an eventual system hang before anything even starts to render. A power cycle is the only way out. Simply creating a 4.5 context will not trigger the bug, haven't been able to fully test what causes the hang specifically as accessible tools I've found are not compatible with mesa due to only creating a default context (which is currently 3.0), thus crashing on init. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/comments/6 On 2017-05-11T02:54:48+00:00 Michel Dänzer wrote: Please attach the output of glxinfo and dmesg and the Xorg log file. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/comments/8 On 2017-05-11T03:01:24+00:00 Paul wrote: Created attachment 131303 errors that appear to be related to the hang errors that appear to be related to the hang Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/comments/9 On 2017-05-11T03:03:47+00:00 Paul wrote: Created attachment 131304 glxinfo, should contain all the hardware and package info needed glxinfo, should contain all the hardware and package info needed Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/comments/10 On 2017-05-11T03:06:45+00:00 Paul wrote: Created attachment 131305 dmesg dmesg (In reply to Michel Dänzer from comment #1) > Please attach the output of glxinfo and dmesg and the Xorg log file. Already in the process of dumping files... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/comments/11 On 2017-05-11T03:09:17+00:00 Michel Dänzer wrote: Is this a regression from an older version of Mesa? If so, can you bisect? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/comments/12 On 2017-05-11T03:11:49+00:00 Paul wrote: Created attachment 131306 post-hang xorg log, may not be relevant post-hang xorg log, may not be relevant Xorg doesn't appear to keep old log files, or the log may have been lost as a result of the hang, not exactly willing to trigger the hang again at this particular time... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/comments/13 On 2017-05-11T03:16:05+00:00 Paul wrote: (In reply to Michel Dänzer from comment #5) > Is this a regression from an older version of Mesa? If so, can you bisect? Don't know, never had any working previous versions due to outdated kernel and drivers (kubuntu 16.10). This is as close as I've gotten > 3.0 to work on this machine by upgrading to 17.04 (4.10 kernel). Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/comments/14 On 2018-08-31T06:35:41+00:00 Timothy Arceri wrote: Is this working for you now? Unigine heaven is used regularly for benchmarking and there are no other reports of this type as far as I'm aware. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/comments/16 ** Changed in: mesa 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/1689408 Title: System hang when utilising OpenGL 4.5 features Status in Mesa: Incomplete Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: New Bug description: I've found this to be easily reproducible via unigine's heaven benchmark, which uses tessellation and other features extensively. Simply creating a OpenGL 4.5 context will not trigger the hang, and you must explicitly request an OGL 4+ context as the default will only be 3.0. On a successful trigger, the screen may flicker on and off a few times and eventually hang completely on a black screen, there's no way to recover the system from t
[Kernel-packages] [Bug 1788321] Re: swapon failed: invalid argument
This doesn't happen on amd64. Do you also have to re-run mkswap when switching back to the older, working kernel, or does simply using the other kernel let you run swapon on the same file that doesn't work with the newer kernel? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: util-linux (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/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1788321] Re: swapon failed: invalid argument
Also what does getconf PAGESIZE say under the broken kernel? -- 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/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1767322] Re: "Activation of network connection failed" popup shows incessantly
I have the same issue. Other wifi networks connect immediately but one. When I first installed Ubuntu 18.04 it worked completely fine for a couple of days but now it doesn't. Please help. -- 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/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767322/+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 1767322] Re: "Activation of network connection failed" popup shows incessantly
I think you're on to something Manfred. I removed my bluetooth connection and that solved the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767322/+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 1790181] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183063/+files/ProcCpuinfoMinimal.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] Re: /proc/diskstats shows weird values
apport information ** Tags added: apport-collected ** Description changed: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Aug 11 22:30 seq + crw-rw 1 root audio 116, 33 Aug 11 22:30 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e + InstallationDate: Installed on 2016-03-29 (885 days ago) + InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) + MachineType: Dell Inc. PowerEdge R530 + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 mgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M + ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-30-generic N/A + linux-backports-modules-4.15.0-30-generic N/A + linux-firmware 1.173.1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-30-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) + UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo + _MarkForUpload: False + dmi.bios.date: 10/05/2015 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.5.4 + dmi.board.name: 0HFG24 + dmi.board.vendor: Dell Inc. + dmi.board.version: A01 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: + dmi.product.name: PowerEdge R530 + dmi.sys.vendor: Dell Inc. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183058/+files/CRDA.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th v
[Kernel-packages] [Bug 1790181] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183062/+files/Lsusb.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1789934] Re: [18.10 FEAT] Add kernel config options for SMC-R/D
** Changed in: ubuntu-z-systems Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789934 Title: [18.10 FEAT] Add kernel config options for SMC-R/D Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Add folliowing options for SMC-R/D CONFIG_SMC=m CONFIG_SMC_DIAG=m CONFIG_ISM=m Already provided CONFIG_HAVE_PNETID with bugzilla https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1789934/+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 1790181] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183061/+files/Lspci.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183060/+files/IwConfig.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183064/+files/ProcEnviron.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183068/+files/WifiSyslog.txt ** 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183065/+files/ProcInterrupts.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183059/+files/CurrentDmesg.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183066/+files/ProcModules.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1790181/+attachment/5183067/+files/UdevDb.txt -- 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Confirmed Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 11 22:30 seq crw-rw 1 root audio 116, 33 Aug 11 22:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=719079af-279c-46cd-9438-01086a2cb16e InstallationDate: Installed on 2016-03-29 (885 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R530 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=9be44daa-0a66-486f-9fac-ff0814849ed3 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-08-11 (19 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 10/05/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.4 dmi.board.name: 0HFG24 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.4:bd10/05/2015:svnDellInc.:pnPowerEdgeR530:pvr:rvnDellInc.:rn0HFG24:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790188] [NEW] Bionic update: upstream stable patchset 2018-08-31
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2018-08-31 (ported from v4.14.50 and v4.16.16)
from git://git.kernel.org/
usb: gadget: udc: renesas_usb3: should fail if devm_phy_get() returns error
usb: gadget: udc: renesas_usb3: should call devm_phy_get() before add udc
usb: gadget: udc: renesas_usb3: should call pm_runtime_enable() before add udc
usb: gadget: udc: renesas_usb3: should remove debugfs
usb: gadget: udc: renesas_usb3: fix double phy_put()
usb: typec: wcove: Remove dependency on HW FSM
crypto: omap-sham - fix memleak
crypto: vmx - Remove overly verbose printk from AES XTS init
crypto: vmx - Remove overly verbose printk from AES init routines
crypto: caam - fix size of RSA prime factor q
crypto: caam/qi - fix IV DMA mapping and updating
crypto: caam - fix IV DMA mapping and updating
crypto: caam - fix DMA mapping dir for generated IV
crypto: caam - strip input zeros from RSA input buffer
Input: goodix - add new ACPI id for GPD Win 2 touch screen
kvm: x86: use correct privilege level for sgdt/sidt/fxsave/fxrstor access
tty: pl011: Avoid spuriously stuck-off interrupts
vmw_balloon: fixing double free when batching mode is off
serial: 8250: omap: Fix idling of clocks for unused uarts
serial: samsung: fix maxburst parameter for DMA transactions
tty/serial: atmel: use port->name as name in request_irq()
serial: sh-sci: Stop using printk format %pCr
usb: gadget: udc: renesas_usb3: disable the controller's irqs for reconnecting
usb: gadget: function: printer: avoid wrong list handling in printer_write()
phy: qcom-qusb2: Fix crash if nvmem cell not specified
Input: xpad - add GPD Win 2 Controller USB IDs
usb-storage: Add compatibility quirk flags for G-Technologies G-Drive
usb-storage: Add support for FL_ALWAYS_SYNC flag in the UAS driver
usbip: vhci_sysfs: fix potential Spectre v1
NFC: pn533: don't send USB data off of the stack
staging: android: ion: Switch to pr_warn_once in ion_buffer_destroy
KVM: x86: pass kvm_vcpu to kvm_read_guest_virt and kvm_write_guest_virt_system
KVM: x86: introduce linear_{read,write}_system
KVM: X86: Fix reserved bits check for MOV to CR3
gpio: No NULL owner
af_key: Always verify length of provided sadb_key
blkdev_report_zones_ioctl(): Use vmalloc() to allocate large buffers
netfilter: nf_tables: fix NULL pointer dereference on nft_ct_helper_obj_dump()
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2018-08-31 (ported from v4.14.50 and v4.16.16)
+ from git://git.kernel.org/
-upstream stable patchset 2018-08-31
-from git://git.kernel.org/
+ usb: gadget: udc: renesas_usb3: should fail if devm_phy_get() returns error
+ usb: gadget: udc: renesas_usb3: should call devm_phy_get() before add udc
+ usb: gadget: udc: renesas_usb3: should call pm_runtime_enable() before add udc
+ usb: gadget: udc: renesas_usb3: should remove debugfs
+ usb: gadget: udc: renesas_usb3: fix double phy_put()
+ usb: typec: wcove: Remove dependency on HW FSM
+ crypto: omap-sham - fix memleak
+ crypto: vmx - Remove overly verbose printk from AES XTS init
+ crypto: vmx - Remove overly verbose printk from AES init routines
+ crypto: caam - fix size of RSA prime factor q
+ crypto: caam/qi - fix IV DMA mapping and updating
+ crypto: caam
[Kernel-packages] [Bug 1788755] Re: linux-azure: 4.15.0-1023.24~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1788755 Title: linux-azure: 4.15.0-1023.24~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788755/+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 1790181] 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 1790181 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 ** Tags added: 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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: Incomplete Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] Re: /proc/diskstats shows weird values
** Package changed: munin (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/1790181 Title: /proc/diskstats shows weird values Status in linux package in Ubuntu: New Bug description: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real 0m8,132s user 0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description: Ubuntu 18.04.1 LTS Release: 18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790181/+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 1790181] [NEW] /proc/diskstats shows weird values
You have been subscribed to a public bug: For one block device on one of my servers munin shows abnormally high latency. When querying /proc/diskstats manually, the device in question shows: 8 32 sdc 973668 361965 64248290 10224376 755130 518162 22349256 1347171224 63 54302956 1357481880 Sanity check: If I divide the 7th value by the 4th value I get a avg read latency of about 10.5 ms. That is somewhat in line with the Avg. Read IO Wait Time of 11.35 ms that munin reports. The problem: If I divide the 11th value by the 8th value I get an avg write latency of 1789 ms. That is also close to the Avg. Write IO Wait Time of 1.60 s reported by munin. Now this is an SD card and it is slow, but not THAT slow.. To confirm unexpected values, I measured some activity: $ dd if=/dev/urandom of=testfile bs=1M count=100; time sync; cat /proc/diskstats 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 18,7652 s, 5,6 MB/s real0m8,132s user0m0,000s sys 0m0,007s The reported time spent writing went from 1353896856 before the test to 1356759112 after the test. The difference is 2862256 ms or about 2800 seconds that supposedly passed in just over 26 real time seconds. I repeated the test with count=1 and got 5780 ms IO write time reported in .7 s realtime. #1297522 describes a similar error but I have no idea if the cause is related. System information: Description:Ubuntu 18.04.1 LTS Release:18.04 Linux 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 GNU/Linux /dev/sdc is a Dell dual SD card module in RAID 1 mode with two Lexar 8GB U3 cards. The system is a Dell R530. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- /proc/diskstats shows weird values https://bugs.launchpad.net/bugs/1790181 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 159356] Re: System freeze on high memory usage when DMA is disabled
** Tags added: patch -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 1789474] Re: Unable to boot without radeon.dpm=0
Hi, I have attached the file. ** Attachment added: "previous_boot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1789474/+attachment/5183048/+files/previous_boot.txt -- 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/1789474 Title: Unable to boot without radeon.dpm=0 Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: After selecting Ubuntu in the grub menu, I am greeted with a black screen that flashes text and the computer reboots. This keeps happening until I edit the boot parameters and add radeon.dpm=0. I tried to fix the issue by installing a newer version of the kernel and installing the Oibaf's PPA, but the issue persisted. Created a new bug without the PPA as instructed here: https://bugs.launchpad.net/ubuntu/+bug/1786647 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 Uname: Linux 4.18.5-041805-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 19:59:25 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789474/+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 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
There are many nouveau commits that were introduced in v4.15-rc1, so we need to perform a bisect to identify the specific one that caused this regression. I started a kernel bisect between v4.14 final and v4.15-rc1. The kernel bisect will require testing of about 7-10 test kernels. I built the first test kernel, up to the following commit: 1be2172e96e33bfa22a5c7a651f768ef30ce3984 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1783957 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+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 1788762] Re: linux: 3.2.0-135.181 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.2.0-135.181 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788762 Title: linux: 3.2.0-135.181 -proposed tracker Status in Kernel SRU Workflow: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Precise: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: kernel-stable-phase-changed:Monday, 27. August 2018 21:32 UTC kernel-stable-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788762/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Is it already fix in proposed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Incomplete Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Can you try latest mainline kernel? -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745032/+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 159356] Re: System freeze on high memory usage when DMA is disabled
It is also possible, since we now know how the bug is triggered, should Marcus open a new report? -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 159356] Re: System freeze on high memory usage when DMA is disabled
This also explains the reason a person with a USB drive was seeing thrashing (constant blinking) when using the fedora live environment with many tabs open. -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 159356] Re: System freeze on high memory usage when DMA is disabled
Do you think this could eventually be merged into a kernel? Has anyone filed a kernel bugzilla with the patch so we can improve it, and get it merged to the kernel? -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 1713448] Re: Adobe Reader doesn't print on OKI C911
Hello Udippel, Thanks for running apport for us. :) G [Ubuntu Bug Squad volunteer triager] -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Nope. It doesn't work. -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745032/+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 1781049] Re: WiFI hard blocked after resuming laptop from suspend
** Summary changed: - WiFI hard blocked after resuming laptop (RTL 8723BE) + WiFI hard blocked after resuming laptop from suspend ** Summary changed: - WiFI hard blocked after resuming laptop from suspend + WiFi hard blocked after resuming laptop from suspend -- 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/1781049 Title: WiFi hard blocked after resuming laptop from suspend Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mythreya 1281 F pulseaudio /dev/snd/controlC1: mythreya 1281 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-26 (16 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion Notebook NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.87 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8096 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-06-30T14:39:45.608645 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2018-06-28T16:23:51.596655 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR71 1a9d81bf-e7f5-4f8a-956f-96180dc493e1 wifi 1531450229 Thu 12 Jul 2018 09:50:29 PM CDT yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlo1activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Ethernet 81087af0-5c8d-451f-84c0-1a95c6034098 ethernet 1530214661 Thu 28 Jun 2018 02:37:41 PM CDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- --
[Kernel-packages] [Bug 1773113] Re: nvidia-390 does not show GUI
Yes, it seems this bug does not happen any more on my PC. But the update alone does not resolve the issue. After I remove - install the drivers, lightdm and gdm several times, suddenly it works :)) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1773113 Title: nvidia-390 does not show GUI Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I know this bug is a duplicate, I am opening it because it seems that for # #1752053 it is marked as "Fix Released" although many people are still affected and complaining about it and nobody can or will change that status. So it is an attempt to raise more attention, as HDMI currently isn't usable for me on Ubuntu 18.04 (it affected me on 16.04 as well). Put in short, after Nvidia drivers are installed and I switch from Nvidia card to the intel one, the GUI can't be opened anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773113/+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 1788730] Re: TP-LINK TG-3468 network card not recognized correctly
Great, thanks a lot! -- 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/1788730 Title: TP-LINK TG-3468 network card not recognized correctly Status in linux package in Ubuntu: Confirmed Bug description: A few days ago purchased a couple of TP-LINK TG-3468 network cards (reviewed by Phoronix here: https://www.phoronix.com/scan.php?page=news_item&px=MTY2ODQ), both brand new, not reused. After installed them to a pc, to my surprise, one of them was correctly identified and the other was incorrectly identified as "NCube Device 8168 (rev 06)". After DuckDuckGoing for a while I found this kernel bud report for FreeBSD: https://forums.freebsd.org/threads/not-recognized-pci-e -network-card.57734/ IMHO is the same issue but I'm using Ubuntu 16.04.5 server i686. I wanted to report this so it can be fixed, please let me know wich logs/data should I provide. When ran lspci -nv this is shown for the correct nic: 03:00.0 0200: 10ec:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 27 I/O ports at e800 [size=256] Memory at febff000 (64-bit, non-prefetchable) [size=4K] Memory at fdffc000 (64-bit, prefetchable) [size=16K] Capabilities: Kernel driver in use: r8169 Kernel modules: r8169 And this for the incorrect one: 01:00.0 0200: 10ff:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c800 [size=256] Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K] Memory at fdefc000 (64-bit, prefetchable) [size=16K] Capabilities: 1) lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 2) In regard to the package I think this is related to the kernel itself? 3) Both cards should be identified as "Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" and the r8169 driver should be used. 4) The network card was erroneously detected as a different one and the driver was not loaded by the kernel. Best regards. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-133-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=652853e2-bd7e-44bb-9b13-f2c9c3823791 InstallationDate: Installed on 2017-12-06 (260 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic root=UUID=89ec3fdb-2ccd-497a-8657-bbe2b53393ed ro ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 RelatedPackageVersions: linux-restricted-modules-4.4.0-133-generic N/A linux-backports-modules-4.4.0-133-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-133-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/27/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-CM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.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.:bvr0702:bd08/27/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-CM:rvrx.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/ubuntu/+source/linux/+bug/1788730/+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 1785481] Re: amdgpu WQHD resolution(2560 × 1440) not available
With the kernel 4.15.0-34-generic #37~16.04.1 from the Proposed repository the bug is still present -- 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/1785481 Title: amdgpu WQHD resolution(2560 × 1440) not available Status in linux package in Ubuntu: Triaged Bug description: Hello, I use ubuntu 16.04 with hwe stack and an Radeon R9 285. With kernel 4.13 and older, I can use a resolution of 2560x1440. But, since the upgrade to kernel 4.15, I'm limited to the 1920x1200. I have attached the output of xrandr on both kernel. My screen (Dell U2713HM) is plugged to the output DVI-1. With a kernel 4.13, the output is detected as a DVI-I. But with a kernel 4.15, the output is detected as a DVI-D. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 5 16:46:32 2018 SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to xenial on 2016-12-17 (595 days ago) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frederic 2366 F pulseaudio /dev/snd/controlC1: frederic 2366 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/Fred_SSD-Fred_Swap IwConfig: lono wireless extensions. em1 no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/Fred_SSD-Fred_Root ro quiet ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.157.20 RfKill: Tags: xenial Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-12-17 (596 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare scanner sudo video _MarkForUpload: True dmi.bios.date: 10/28/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3003 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3003:bd10/28/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIRANGER:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785481/+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 1789772] Re: tlbie master timeout checkstop (using NVidia/GPU)
** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) => Khaled El Mously (kmously) ** Changed in: linux (Ubuntu Bionic) Assignee: Joseph Salisbury (jsalisbury) => Khaled El Mously (kmously) -- 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/1789772 Title: tlbie master timeout checkstop (using NVidia/GPU) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: A hung state machine in the chip's NMU logic can trigger a fatal condition that will be flagged by hardware through a checkstop. Hence, customers that have a Power 9 Whitherspoon (equipped with GPUs) will experience a crash on their server when using NVIDIA's toolkit. The server will crash with the following hardware failing message: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 19703), Resolved: 0 In this case, a `NCUFIR[10] tlbie master timeout` has been observed by only starting the NVIDIA ATS driver. This issue is being triggered because the NMU logic is getting stuck when a page is upgraded from RO -> RW without a following tlbie. This is addressed with the following patches: bd5050e38aec3055ff4257ade987d808ac93b582 powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang e4c1112c3fc503fc78379fa61450bfda3f0717fe powerpc/mm: Change function prototype 044003b52a78bcbda7103633c351da16505096cf powerpc/mm/radix: Move function from radix.h to pgtable-radix.c f069ff396d657ac7bdb5de866c3ec28b8d08d953 powerpc/mm/hugetlb: Update huge_ptep_set_access_flags to call __ptep_set_access_flags directly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1789772/+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 1788623] Re: regression: IPv6 PMTU discovery fails with source-specific routing
Thanks for testing. That implies that commit 35732d01fe31 is not the specific commit that introduced the regression. I built a second test kernel up to the commit f5bbe7ee79c2. This test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1788623 Can you test this kernel and see if it resolves 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/1788623 Title: regression: IPv6 PMTU discovery fails with source-specific routing Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: IPv6 PMTU discovery fails when using source-specific routing on Ubuntu 18.04. I have attached a test case called pmtu-sads.sh which is based on tools/testing/selftests/net/pmtu.sh in the linux source. I have verified that the test fails on: Ubuntu 18.04 with 4.15.0-30.32 Ubuntu 18.04 with 4.17.0-041700.201806041953 Ubuntu 18.04 with 4.18.3-041803.201808180530 The test succeeds on Ubuntu 16.04 with 4.4.0.131.137 which makes it a regression. System information: Ubuntu 4.15.0-30.32-generic 4.15.18 Description: Ubuntu 18.04.1 LTS Release: 18.04 See below for a patch which is working for me. I'm currently using linux kernel 4.15.0-32.35 built from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git with this patch. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-30-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=041f6e1e-4904-4760-8518-3a88dc288556 ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-30-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788623/+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 1784331] Re: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- 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/1784331 Title: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: With the introduction of KVM crypto virtualization the driver bound to an AP queue device is no longer unique determined. This feature provides a deterministic hot plugging semantics of AP queues that may be bound to multiple drivers. In particular it enables to configure an AP queue (APQN) as being bound to a particular driver even if the associate HW gets intermittently lost and reconnected. Is planned as part of kernel 4.19. Therefore a backport to kernel 4.18 will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784331/+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 1789653] Re: regression with EXT4 file systems and meta_bg flag
https://lists.ubuntu.com/archives/kernel-team/2018-August/095108.html
** Description changed:
+ == SRU Justification ==
+ A regression was introduced where ext4_check_descriptors() was getting
+ called before s_gdb_count was initialized. This regression was
+ introduced to Xenial in 4.4.0-134. This is fixed by mainline commit
+ 44de022c4382.
+
+ Commit 44de022c4382 was also cc'd to upstream stable. However, it has
+ not made it's way into Xenial via stable updates as of yet.
+
+ == Fix ==
+ 44de022c4382 ("ext4: fix false negatives *and* false positives in
ext4_check_descriptors()")
+
+ == Regression Potential ==
+ Low. This commit has been cc'd upstream stable, so it has had
+ additional upstream review.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+
+
Hello,
In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all partitions
in ext4 with flag meta_bg :
kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap
for group 0 overlaps block group descriptors
kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!
Go back with the kernel 4.4.0-133-generic and all partitions mount
correctly.
It looks like this:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd
The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
- ---
+ ---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
InstallationDate: Installed on 2017-04-28 (488 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
-
+
ProcEnviron:
- TERM=xterm
- PATH=(custom, no user)
- LANG=fr_FR.UTF-8
- SHELL=/bin/bash
+ TERM=xterm
+ PATH=(custom, no user)
+ LANG=fr_FR.UTF-8
+ SHELL=/bin/bash
ProcFB:
-
+
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
RelatedPackageVersions:
- linux-restricted-modules-4.4.0-134-generic N/A
- linux-backports-modules-4.4.0-134-generic N/A
- linux-firmware N/A
+ linux-restricted-modules-4.4.0-134-generic N/A
+ linux-backports-modules-4.4.0-134-generic N/A
+ linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.4.0-134-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
-
+
_MarkForUpload: True
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
- ---
+ ---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
InstallationDate: Installed on 2017-04-28 (488 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
-
+
ProcEnviron:
- TERM=xterm
- PATH=(custom, no user)
- LANG=fr_FR.UTF-8
- SHELL=/bin/bash
+ TERM=xterm
+ PATH=(custom, no user)
+ LANG=fr_FR.UTF-8
+ SHELL=/bin/bash
ProcFB:
-
+
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
Pro
[Kernel-packages] [Bug 1789131] Re: Probable regression with EXT3 file systems and CVE-2018-1093 patches
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-August/095106.html
** Description changed:
+
+ == SRU Justification ==
+ Mainline commit 7dac4a1726a9 introduced a regression in v4.17-rc1, which
+ made it's way into Trusty via upstream stable updates. This regression
+ is resolved by mainline commit 22be37acce25. This commit has been cc'd
+ to upstream stable, but has not made it's way into Trusty as of yet.
+
+ == Fix ==
+ 22be37acce25 ("ext4: fix bitmap position validation")
+
+ == Regression Potential ==
+ Low. This commit has been cc'd to upstream stable, so it has had
+ additional upstream review.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+
A customer reported on all of their ext3 and none of their ext4 systems
that the file system was in read-only mode, I believe after rebooting
into 3.13.0-157.207 from 3.13.0-156.206. Here is the output of tune2fs
-l for one of the file systems:
tune2fs 1.42.12 (29-Aug-2014)
Last mounted on: /
Filesystem UUID: 748f503a-443d-4769-8dd2-45ff46b48555
Filesystem magic number: 0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options:(none)
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1966080
Block count: 7863296
Reserved block count: 393164
Free blocks: 4568472
Free inodes: 1440187
First block: 0
Block size: 4096
Fragment size:4096
Reserved GDT blocks: 1022
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
RAID stride: 128
RAID stripe width:512
Filesystem created: Thu Feb 25 21:54:24 2016
Last mount time: Fri Aug 24 07:40:51 2018
Last write time: Fri Aug 24 07:40:51 2018
Mount count: 1
Maximum mount count: 25
Last checked: Fri Aug 24 07:38:54 2018
Check interval: 15552000 (6 months)
Next check after: Wed Feb 20 07:38:54 2019
Lifetime writes: 7381 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode:8
Default directory hash: half_md4
Directory Hash Seed: d6564a54-cd2a-4804-ad94-1e4e0e47933a
Journal backup: inode blocks
FS Error count: 210
First error time: Fri Aug 24 07:40:51 2018
First error function: ext4_validate_block_bitmap
First error line #: 376
First error inode #: 0
First error block #: 0
Last error time: Sun Aug 26 19:35:16 2018
Last error function: ext4_remount
Last error line #:4833
Last error inode #: 0
Last error block #: 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/1789131
Title:
Probable regression with EXT3 file systems and CVE-2018-1093 patches
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Bug description:
== SRU Justification ==
Mainline commit 7dac4a1726a9 introduced a regression in v4.17-rc1, which
made it's way into Trusty via upstream stable updates. This regression
is resolved by mainline commit 22be37acce25. This commit has been cc'd
to upstream stable, but has not made it's way into Trusty as of yet.
== Fix ==
22be37acce25 ("ext4: fix bitmap position validation")
== Regression Potential ==
Low. This commit has been cc'd to upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
A customer reported on all of their ext3 and none of their ext4
systems that the file system was in read-only mode, I believe after
rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output
of tune2fs -l for one of the file systems:
tune2fs 1.42.12 (29-Aug-2014)
Last mounted on: /
Filesystem UUID: 748f503a-443d-4769-8dd2-45ff46b48555
Filesystem magic number: 0xEF53
Filesystem revision #:1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
[Kernel-packages] [Bug 1789934] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-08-31 10:05 EDT--- @Seth The config option CONFIG_ISM=m is related to kernel 4.19. Due to the fact that we have already a backport via https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902 -> SMC-Direct we also need this set on kernel 4.18... Does that help? -- 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/1789934 Title: [18.10 FEAT] Add kernel config options for SMC-R/D Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Bug description: Add folliowing options for SMC-R/D CONFIG_SMC=m CONFIG_SMC_DIAG=m CONFIG_ISM=m Already provided CONFIG_HAVE_PNETID with bugzilla https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1789934/+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 159356] Re: System freeze on high memory usage when DMA is disabled
The attached kernel patch (applied on top of 4.18.5) that I've tried, almost completely eliminates the disk thrashing(the constant reading of executable(and .so) files on every context switch) associated with freezing the OS and so, with this patch, the OOM-killer is triggered within a maxium of 1 second when it is needed, rather than, without this patch, freeze the OS for minutes(or just a long time, it may even auto reboot depending on your kernel .config options set to panic(reboot) on hang after xx seconds) with constant disk reading well before OOM-killer gets triggered. More info as to why OS freezes with constant disk reading when running out of RAM, here: https://unix.stackexchange.com/a/463469/306023 The patch is from inside this question: https://stackoverflow.com/q/52067753/10239615 Note: I don't recommend using this patch in production, without actual programmers saying that it's ok first. I'm not a programmer. Maybe some programmer could improve it? I am using the patch currently inside a Qubes OS R4.0 Fedora 28 AppVM where I can easily reproduce freezing the VM's OS (+ the constant disk thrashing, seen from `sudo iotop` in dom0) without the patch, while attempting to compile firefox with 4000MB max RAM setting for the VM, and with the patch basically no freezing and little to no disk thrashing during the 1 second it takes for OOM-killer to kill the offending process(es). ** Patch added: "le9b.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+attachment/5183022/+files/le9b.patch -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 1785675] Re: Security fix: check if IOMMU page is contained in the pinned physical page
https://lists.ubuntu.com/archives/kernel-team/2018-August/095103.html
** Description changed:
+
+ == SRU Justification ==
+ IBM is requesting commit 76fa4975f3ed in powerpc as a security fix.
+ This commit Fixes: 121f80ba68f1. Commit 76fa4975f3ed also requires
+ mainline commit 1463edca6734 as a prereq.
+
+ Both these commits have already been cc'd to upstream stable, but they
+ have not landed in Bionic as of yet.
+
+ == Fixes ==
+ 1463edca6734 ("vfio/spapr: Use IOMMU pageshift rather than pagesize")
+ 76fa4975f3ed ("KVM: PPC: Check if IOMMU page is contained in the pinned
physical page")
+
+ == Regression Potential ==
+ Low. These commits have also been sent to upstream stable, so have had
+ additional upstream review.
+
+ == Test Case ==
+ A test kernel was built with these patches and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+
== Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-08-06
12:27:59 ==
Please, add the following security fix to the distro kernel:
76fa4975f3ed KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
Also already available in the 4.14 stable tree:
58113603a4ea KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
And in the 4.17 stable tree:
970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
--
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/1785675
Title:
Security fix: check if IOMMU page is contained in the pinned physical
page
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Bug description:
== SRU Justification ==
IBM is requesting commit 76fa4975f3ed in powerpc as a security fix.
This commit Fixes: 121f80ba68f1. Commit 76fa4975f3ed also requires
mainline commit 1463edca6734 as a prereq.
Both these commits have already been cc'd to upstream stable, but they
have not landed in Bionic as of yet.
== Fixes ==
1463edca6734 ("vfio/spapr: Use IOMMU pageshift rather than pagesize")
76fa4975f3ed ("KVM: PPC: Check if IOMMU page is contained in the pinned
physical page")
== Regression Potential ==
Low. These commits have also been sent to upstream stable, so have had
additional upstream review.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-08-06
12:27:59 ==
Please, add the following security fix to the distro kernel:
76fa4975f3ed KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
Also already available in the 4.14 stable tree:
58113603a4ea KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
And in the 4.17 stable tree:
970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785675/+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 1788755] Re: linux-azure: 4.15.0-1023.24~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1788755 Title: linux-azure: 4.15.0-1023.24~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788755/+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 1713448] PrintingPackages.txt
apport information ** Attachment added: "PrintingPackages.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183003/+files/PrintingPackages.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183004/+files/ProcCpuinfo.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183009/+files/UdevDb.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183005/+files/ProcCpuinfoMinimal.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183007/+files/ProcInterrupts.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183008/+files/ProcModules.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183006/+files/ProcEnviron.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183002/+files/Lsusb.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1784331] Re: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) -- 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/1784331 Title: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Committed Bug description: With the introduction of KVM crypto virtualization the driver bound to an AP queue device is no longer unique determined. This feature provides a deterministic hot plugging semantics of AP queues that may be bound to multiple drivers. In particular it enables to configure an AP queue (APQN) as being bound to a particular driver even if the associate HW gets intermittently lost and reconnected. Is planned as part of kernel 4.19. Therefore a backport to kernel 4.18 will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784331/+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 1783152] Re: Enable basic support for Solarflare 8000 series NIC
According to SRU it may be related to : https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1708245 cyphermox will need to be involve. -- 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/1783152 Title: Enable basic support for Solarflare 8000 series NIC Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in debian-installer source package in Trusty: Fix Committed Status in linux source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-lts-xenial source package in Xenial: Invalid Bug description: SRU Justification: [Impact] * Users cannot use Solarflare 8000 series NICs. * Servers with only this NIC cannot do netboot. * The patchset adds the PCI IDs and a basic fix. [Test Case] * Try to probe/netboot/use a Solarflare 8000 series NIC. * It does not probe on the original kernel, but it does probe/netboot/install/stress (i.e., basic fuctionality works) on the patched kernel. [Regression Potential] * Users with Solarflare 8000 series NIC might hit problems on device probe or due to a new network interface coming up, now that the NIC comes up. * More specific features of the NIC or advanced tuning/setup might not work as expected or run into issues. [Other Info] * There are known error messages on device probe. * These are benign/non-fatal and will be addressed on another SRU cycle. --- The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 series NIC. This prevents network installs on servers which only have that NIC. In order to get NIC detected, link up, and successful network install, only 2 commits are required: dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 93171b14a545 sfc: make TSO version a per-queue parameter This patchset is undergoing testing, and I will post the patches to the kernel-team mailing list. --- There are some kernel messages produced possibly due to additional commits missing, but are benign/non-fatal and allows the NIC probing and basic functionality to work. [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part Number : SFN8042 [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0 [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP support [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0 [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed to allocate PIO buffers (-1) ... [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 1500) The PTP (precision time protocol / ieee 1588) support is a feature to synchronize clocks over a computer network with high precision, and is not required for basic functionality nor for this particular user. The failure to allocate PIO buffers is non-fatal, see sfc/ef10.c/efx_ef10_dimension_resources() comments. The additional patches to resolve the error messages will be worked on another SRU cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1783152/+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 1783152] Re: Enable basic support for Solarflare 8000 series NIC
FTBFS on Trusty amd64 arch in investigation [Build #15318223] amd64 build of debian-installer 20101020ubuntu318.44 in ubuntu trusty PROPOSED -- 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/1783152 Title: Enable basic support for Solarflare 8000 series NIC Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in debian-installer source package in Trusty: Fix Committed Status in linux source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-lts-xenial source package in Xenial: Invalid Bug description: SRU Justification: [Impact] * Users cannot use Solarflare 8000 series NICs. * Servers with only this NIC cannot do netboot. * The patchset adds the PCI IDs and a basic fix. [Test Case] * Try to probe/netboot/use a Solarflare 8000 series NIC. * It does not probe on the original kernel, but it does probe/netboot/install/stress (i.e., basic fuctionality works) on the patched kernel. [Regression Potential] * Users with Solarflare 8000 series NIC might hit problems on device probe or due to a new network interface coming up, now that the NIC comes up. * More specific features of the NIC or advanced tuning/setup might not work as expected or run into issues. [Other Info] * There are known error messages on device probe. * These are benign/non-fatal and will be addressed on another SRU cycle. --- The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 series NIC. This prevents network installs on servers which only have that NIC. In order to get NIC detected, link up, and successful network install, only 2 commits are required: dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 93171b14a545 sfc: make TSO version a per-queue parameter This patchset is undergoing testing, and I will post the patches to the kernel-team mailing list. --- There are some kernel messages produced possibly due to additional commits missing, but are benign/non-fatal and allows the NIC probing and basic functionality to work. [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part Number : SFN8042 [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0 [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP support [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0 [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed to allocate PIO buffers (-1) ... [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 1500) The PTP (precision time protocol / ieee 1588) support is a feature to synchronize clocks over a computer network with high precision, and is not required for basic functionality nor for this particular user. The failure to allocate PIO buffers is non-fatal, see sfc/ef10.c/efx_ef10_dimension_resources() comments. The additional patches to resolve the error messages will be worked on another SRU cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1783152/+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 1713448] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183001/+files/Lspci.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] Locale.txt
apport information ** Attachment added: "Locale.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5183000/+files/Locale.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5182999/+files/KernLog.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1713448] Re: Adobe Reader doesn't print on OKI C911
apport information ** Tags added: apport-collected xenial ** Description changed: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + CupsErrorLog: + E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. + E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. + E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. + CurrentDesktop: KDE + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2015-04-01 (1247 days ago) + InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) + Lpstat: + device for BrotherColourMFC9970: socket://134.91.100.26:9100 + device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ + device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ + device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ + MachineType: LENOVO 2924WEG + Package: linux + PackageArchitecture: amd64 + Papersize: a4 + PpdFiles: + Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied + grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied + grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied + grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied + ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 + Tags: xenial + Uname: Linux 4.4.0-134-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/11/2012 + dmi.bios.vendor: LENOVO + dmi.bios.version: 6UET70WW (1.50 ) + dmi.board.name: 2924WEG + dmi.board.vendor: LENOVO + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 2924WEG + dmi.product.version: ThinkPad T410s + dmi.sys.vendor: LENOVO ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5182997/+files/CurrentDmesg.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cac
[Kernel-packages] [Bug 1713448] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1713448/+attachment/5182998/+files/Dependencies.txt -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1788097] Re: performance drop with ATS enabled
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1788097
Title:
performance drop with ATS enabled
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
In Progress
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-08-16
09:58:02 ==
Witherspoon cluster now has ATS enabled with driver 396.42, CUDA
version 9.2.148. They are running the CORAL benchmark LULESH with and
without ATS, and they see a significant performance drop with ATS
enabled.
Below is the run with ATS:
Run completed:
Problem size = 160
MPI tasks = 8
Iteration count = 100
Final Origin Energy = 1.605234e+09
Testing Plane 0 of Energy Array on rank 0:
MaxAbsDiff = 2.384186e-07
TotalAbsDiff = 5.300015e-07
MaxRelDiff = 1.631916e-12
Elapsed time = 153.00 (s)
Grind time (us/z/c) = 0.37352393 (per dom) (0.046690491 overall)
FOM = 21417.637 (z/s)
Here is the run without ATS:
Run completed:
Problem size = 160
MPI tasks = 8
Iteration count = 100
Final Origin Energy = 1.605234e+09
Testing Plane 0 of Energy Array on rank 0:
MaxAbsDiff = 2.384186e-07
TotalAbsDiff = 5.300015e-07
MaxRelDiff = 1.631916e-12
Elapsed time = 13.27 (s)
Grind time (us/z/c) = 0.032394027 (per dom) (0.0040492534 overall)
FOM = 246959.11 (z/s)
Using ATS on a single node slows down the OpenACC version more than 10
times, and for the version with OpenMP 4.5 and managed memory, they
observe a 2x slowdown.
Last comment from NVIDIA (Javier Cabezas - 07/29/2018 11:30 AM):
We think we have found where's the issue.
This behavior reproduces for any two concurrent processes that create
CUDA contexts on the GPUs and heavily unmap memory (no need to launch
any work on the GPUs). When the problem repros, perf shows that most
of the time is spent in mmio_invalidate. However, this only happens
when processes register GPUs attached to the same NPU. Thus, if
process A, initializes GPU 0 and/or 1, and process B, initializes GPU
2 and/or 3, we don't see the slowdown. This makes sense, because ATSDs
on different NPUs are issued independently.
After some code inspection in npu-dma.c (powerpc backend in the Linux
kernel), Mark noticed that the problem could be in the utilization of
test_and_set_bit_lock in get_mmio_atsd_reg. The implementation of
test_and_set_bit_lock in powerpc relies on the ldarx/stdcx
instructions (PPC_LLARX/PPC_STLCX in the snippet below):
#define DEFINE_TESTOP(fn, op, prefix, postfix, eh)\
static __inline__ unsigned long fn( \
unsigned long mask, \
volatile unsigned long *_p) \
{ \
unsigned long old, t; \
unsigned long *p = (unsigned long *)_p; \
__asm__ __volatile__ (\
prefix\
"1:"PPC_LLARX(%0,0,%3,eh) "\n"\
stringify_in_c(op) "%1,%0,%2\n" \
PPC405_ERR77(0,%3)\
PPC_STLCX "%1,0,%3\n" \
"bne- 1b\n" \
postfix \
: "=&r" (old), "=&r" (t) \
: "r" (mask), "r" (p) \
: "cc", "memory");\
return (old & mask); \
}
According to the PowerPC manual, ldarx creates a memory reservation
and a subsequent stwcx instruction from the same processor ensures an
atomic read-modify-write operation. However, the reservation can be
lost if a different processor executes any store instruction on the
same address. That's why "bne- 1b" checks wether stwcx was successful
and jumps back to retry, otherwise. Since DEFINE_TESTOP doesn't
implement any back-off mechanism, two different processors trying to
get an ATSD register can starve each other.
Mark compiled a custom kernel which surrounds the calls to
test_and_set_bit_lock in get_mmio_atsd_reg with a spinlock and I
verified that it solves the issue. These are the execution times for
LULESH:
ATS OFF
Elapsed time = 16.87 (s)
ATS ON
Elapsed time = 215.56 (s)
ATS ON + Spinlock
Elapsed time = 18.14 (s)
Fixed with the following patch in the powerpc tree:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=9eab9901b015
== Comment: #1 - Michael Ranweiler - 2018-08-20
14:56:52 ==
This is now in mainline,
[Kernel-packages] [Bug 1789934] Re: [18.10 FEAT] Add kernel config options for SMC-R/D
We already have: CONFIG_SMC=m CONFIG_SMC_DIAG=m Looking at 4.18, there is no CONFIG_ISM. Marking this as fixed, please re-open if you find something is missing. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789934 Title: [18.10 FEAT] Add kernel config options for SMC-R/D Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Bug description: Add folliowing options for SMC-R/D CONFIG_SMC=m CONFIG_SMC_DIAG=m CONFIG_ISM=m Already provided CONFIG_HAVE_PNETID with bugzilla https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1789934/+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 1713448] 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 1713448 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1783152] Re: Enable basic support for Solarflare 8000 series NIC
Hello Mauricio, or anyone else affected, Accepted debian-installer into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu318.44 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: debian-installer (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-trusty ** Changed in: linux-lts-xenial (Ubuntu) Status: New => Invalid ** Changed in: linux (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/1783152 Title: Enable basic support for Solarflare 8000 series NIC Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in debian-installer source package in Trusty: Fix Committed Status in linux source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-lts-xenial source package in Xenial: Invalid Bug description: SRU Justification: [Impact] * Users cannot use Solarflare 8000 series NICs. * Servers with only this NIC cannot do netboot. * The patchset adds the PCI IDs and a basic fix. [Test Case] * Try to probe/netboot/use a Solarflare 8000 series NIC. * It does not probe on the original kernel, but it does probe/netboot/install/stress (i.e., basic fuctionality works) on the patched kernel. [Regression Potential] * Users with Solarflare 8000 series NIC might hit problems on device probe or due to a new network interface coming up, now that the NIC comes up. * More specific features of the NIC or advanced tuning/setup might not work as expected or run into issues. [Other Info] * There are known error messages on device probe. * These are benign/non-fatal and will be addressed on another SRU cycle. --- The Trusty HWE kernel from Xenial lacks the PCI ID for the Solarflare 8000 series NIC. This prevents network installs on servers which only have that NIC. In order to get NIC detected, link up, and successful network install, only 2 commits are required: dd248f1bc65b sfc: Add PCI ID for Solarflare 8000 series 10/40G NIC 93171b14a545 sfc: make TSO version a per-queue parameter This patchset is undergoing testing, and I will post the patches to the kernel-team mailing list. --- There are some kernel messages produced possibly due to additional commits missing, but are benign/non-fatal and allows the NIC probing and basic functionality to work. [2.803941] sfc :37:00.0 (unnamed net_device) (uninitialized): Solarflare NIC detected [2.806336] sfc :37:00.0 (unnamed net_device) (uninitialized): Part Number : SFN8042 [2.807366] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x4a inlen 8 failed rc=-2 (raw=2) arg=0 [2.808052] sfc :37:00.0 (unnamed net_device) (uninitialized): no PTP support [2.808488] sfc :37:00.0 (unnamed net_device) (uninitialized): MC command 0x8f inlen 0 failed rc=-1 (raw=1) arg=0 [2.808605] sfc :37:00.0 (unnamed net_device) (uninitialized): failed to allocate PIO buffers (-1) ... [4.037694] sfc :37:00.0 p2p1: link up at 4Mbps full-duplex (MTU 1500) The PTP (precision time protocol / ieee 1588) support is a feature to synchronize clocks over a computer network with high precision, and is not required for basic functionality nor for this particular user. The failure to allocate PIO buffers is non-fatal, see sfc/ef10.c/efx_ef10_dimension_resources() comments. The additional patches to resolve the error messages will be worked on another SRU cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1783152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel
[Kernel-packages] [Bug 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1788758 Title: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788758/+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 1713448] Re: Adobe Reader doesn't print on OKI C911
Hi Udippel. Thanks for the update. I will change the status back to “new” and will look at next steps. Take care :) G ** Changed in: cups (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1789638] Re: azure 4.15 kernel: reading sysfs file causing oops
https://lists.ubuntu.com/archives/kernel-team/2018-August/095100.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/1789638 Title: azure 4.15 kernel: reading sysfs file causing oops Status in linux package in Ubuntu: Incomplete Bug description: Kernel: 4.15.0-1021-azure, in Xenial VM on Azure. How to reproduce: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make ./stress-ng --sysfs 0 -t 120 One gets the following: [ 22.451885] BUG: unable to handle kernel NULL pointer dereference at 0004 [ 22.455286] IP: read_avail_show+0x1c/0x40 [ 22.455286] PGD 80042d59e067 P4D 80042d59e067 PUD 42eb8c067 PMD 0 [ 22.455286] Oops: [#1] SMP PTI [ 22.455286] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_security ip_tables x_tables serio_raw joydev hv_balloon ib_iser iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd hyperv_fb hid_hyperv pata_acpi cfbfillrect hyperv_keyboard cfbimgblt hid cfbcopyarea hv_netvsc hv_utils [ 22.455286] CPU: 1 PID: 1670 Comm: cat Not tainted 4.15.0-1021-azure #21~16.04.1-Ubuntu [ 22.455286] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 22.455286] RIP: 0010:read_avail_show+0x1c/0x40 [ 22.455286] RSP: 0018:afa4c4eafdb0 EFLAGS: 00010286 [ 22.455286] RAX: RBX: 9db36c93e880 RCX: 9db36f136908 [ 22.860062] RDX: RSI: 9db364548000 RDI: 9db364548000 [ 22.888042] RBP: afa4c4eafdb0 R08: 9db364548000 R09: 9db36c049840 [ 22.920041] R10: 9db364548000 R11: R12: 92ae9440 [ 22.948058] R13: 9db36c22d200 R14: 0001 R15: 9db36c93e880 [ 22.972043] FS: 7f67eeec6700() GS:9db37fd0() knlGS: [ 23.004046] CS: 0010 DS: ES: CR0: 80050033 [ 23.024016] CR2: 0004 CR3: 00042c37a003 CR4: 001606e0 [ 23.048014] Call Trace: [ 23.060019] vmbus_chan_attr_show+0x21/0x30 [ 23.076018] sysfs_kf_seq_show+0xa2/0x130 [ 23.088030] kernfs_seq_show+0x27/0x30 [ 23.100020] seq_read+0xb7/0x480 [ 23.112014] kernfs_fop_read+0x111/0x190 [ 23.128017] ? security_file_permission+0xa1/0xc0 [ 23.144013] __vfs_read+0x1b/0x40 [ 23.156019] vfs_read+0x93/0x130 [ 23.168013] SyS_read+0x55/0xc0 [ 23.180021] do_syscall_64+0x73/0x130 [ 23.192014] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 23.212022] RIP: 0033:0x7f67ee9d8260 [ 23.224016] RSP: 002b:7fffdc193ff8 EFLAGS: 0246 ORIG_RAX: [ 23.252022] RAX: ffda RBX: 0002 RCX: 7f67ee9d8260 [ 23.276019] RDX: 0002 RSI: 7f67eed0c000 RDI: 0003 [ 23.300020] RBP: 0002 R08: R09: [ 23.328025] R10: 037b R11: 0246 R12: 7f67eed0c000 [ 23.352036] R13: 0003 R14: R15: 0002 [ 23.376678] Code: fb 3a 17 00 48 98 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 8b 87 38 01 00 00 49 89 f0 8b 97 48 01 00 00 4c 89 c7 48 89 e5 <8b> 48 04 8b 00 29 ca 89 c6 29 ce 01 c2 39 c1 0f 46 d6 48 c7 c6 [ 23.444022] RIP: read_avail_show+0x1c/0x40 RSP: afa4c4eafdb0 [ 23.468021] CR2: 0004 [ 23.481135] ---[ end trace 348a4b7d5a6747d1 ]--- Cornered this down to just reading: cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/99221fa0 -24ad-11e2-be98-001aa01bbf6e/channels/4/read_avail There are various /sysfs VMBUS files that trigger this, see a fix on comment #5 below that addresses all the ones I could find. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789638/+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 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
OK, thanks for the info so far, apologies for being slow to get back to you. -- 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/1788432 Title: 4.15 s390x kernel BUG at /build/linux- Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: uname -a Linux ckingvm1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux and same for 4.15.0-29-generic and 4.17.0-8-generic Steps to reproduce this bug: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean make And run with: ./stress-ng --sysfs 0 -t 60 .. wait a few seconds and then: [ 119.445891] [ cut here ] [ 119.445898] kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! [ 119.446093] illegal operation: 0001 ilc:1 [#3] SMP [ 119.446100] Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic vfio_ccw sha512_s390 sha256_s390 vfio_mdev sha1_s390 sha_common mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net crc32_vx_s390 virtio_blk [ 119.446166] CPU: 1 PID: 5420 Comm: stress-ng-sysfs Tainted: P DO 4.15.0-33-generic #36-Ubuntu [ 119.446168] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 119.446170] Krnl PSW : 12d313d3 405835bc (virtblk_cache_type_show+0x82/0x88 [virtio_blk]) [ 119.446177]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [ 119.446194] Krnl GPRS: de6dc5c2779af7d7 7ffaba20 0040 6545 [ 119.446196]03ff800058da 6546 6bf537c0 6b60a100 [ 119.446198] 00690648 7cc3de40 7a74b000 [ 119.446202]03ff80008210 03ff800058da 7ac1bce8 [ 119.446210] Krnl Code: 03ff80005912: ebbff0a80004 lmg %r11,%r15,168(%r15) [ 119.446210]03ff80005918: c0f40560 brcl 15,3ff800063d8 [ 119.446210] #03ff8000591e: a7f40001 brc 15,3ff80005920 [ 119.446210] >03ff80005922: 0707 bcr 0,%r7 [ 119.446210]03ff80005924: 0707 bcr 0,%r7 [ 119.446210]03ff80005926: 0707 bcr 0,%r7 [ 119.446210]03ff80005928: c004 brcl 0,3ff80005928 [ 119.446210]03ff8000592e: eb6ff0480024 stmg %r6,%r15,72(%r15) [ 119.446226] Call Trace: [ 119.446229] ([<03ff800058da>] virtblk_cache_type_show+0x3a/0x88 [virtio_blk]) [ 119.446234] [<00690684>] dev_attr_show+0x3c/0x80 [ 119.446240] [<00424ab4>] sysfs_kf_seq_show+0xbc/0x1a8 [ 119.446259] [<003b048c>] seq_read+0xec/0x4c8 [ 119.446262] [<003821ea>] vfs_read+0x8a/0x150 [ 119.446274] [<00382786>] SyS_read+0x66/0xe0 [ 119.446278] [<008e3028>] system_call+0xdc/0x2c8 [ 119.446279] Last Breaking-Event-Address: [ 119.446281] [<03ff8000591e>] virtblk_cache_type_show+0x7e/0x88 [virtio_blk] [ 119.446283] [ 119.446284] ---[ end trace 2c2403d726047e4a ]--- For 4.17.0-8-generic: [ 25.170715] kernel BUG at drivers/block/virtio_blk.c:574! [ 25.170795] illegal operation: 0001 ilc:1 [#1] SMP [ 25.170797] Modules linked in: lttng_statedump(OE) lttng_clock(OE) lttng_lib_ring_buffer(OE) binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) isofs zcommon(PO) znvpair(PO) spl(O) ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm nfsd ib_core auth_rpcgss iscsi_tcp nfs_acl lockd grace libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear virtio_net virtio_blk crc32_vx_s390 [ 25.170835] CPU: 0 PID: 5590 Comm: stress-ng-sysfs Tainted: P OE 4.17.0-8-generic #9-Ubuntu [ 25.170837] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 25.170839] Krnl PSW : 05f0c968 26542d57 (virtblk_cache_type_show+0x7c/0x80 [virtio_blk]) [ 25.170846]R:0 T:1 IO:1 EX:1
[Kernel-packages] [Bug 1787904] Re: [radeon] machine crash after GPU reset
Today's freeze has a new message: Aug 31 14:30:38 winters kernel: [160881.141603] DMAR: DRHD: handling fault status reg 2 Aug 31 14:30:38 winters kernel: [160881.141614] DMAR: [INTR-REMAP] Request device [00:00.1] fault index 1e [fault reason 38] Blocked an interrupt request due to source-id verification failure Aug 31 14:30:38 winters kernel: [160881.141620] DMAR: [INTR-REMAP] Request device [00:00.0] fault index 1a [fault reason 38] Blocked an interrupt request due to source-id verification failure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787904 Title: [radeon] machine crash after GPU reset Status in linux package in Ubuntu: Incomplete Bug description: I showed up to work today (after being away for a couple of weeks) and my machine had crashed. I'm not sure why it happened this morning at 7am. My only guess is that a janitor came in and touched the mouse which woke the screen up after a couple of weeks of sleep. (I have been using the machine remotely for computations, which had finished yesterday, but the building was closed so I'm guessing this is the first time the screen has come on in a while). The first unusual entries in my kern.log are: Aug 20 07:02:43 winters kernel: [2218007.668454] radeon :03:00.0: ring 0 stalled for more than 10248msec Aug 20 07:02:43 winters kernel: [2218007.668465] radeon :03:00.0: GPU lockup (current fence id 0x000799d4 last fence id 0x000799d6 on ring 0) They are plentiful, and are mixed with other messages (see attached log file) such as: Aug 20 07:03:00 winters kernel: [2218025.438173] radeon :03:00.0: failed VCE resume (-110). Aug 20 07:03:01 winters kernel: [2218025.721068] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) Aug 20 07:03:01 winters kernel: [2218025.721085] [drm:si_resume [radeon]] *ERROR* si startup failed on resume Aug 20 07:03:01 winters kernel: [2218025.722887] WARNING: CPU: 18 PID: 3715 at /build/linux-60XibS/linux-4.15.0/drivers/gpu/drm/radeon/radeon_object.c:84 radeon_ttm_bo_destroy+0xfb/0x100 [radeon] . . . Aug 20 07:03:38 winters kernel: [2218062.876285] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting Aug 20 07:03:38 winters kernel: [2218062.876298] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BBC8 (len 237, WS 0, PS 4) @ 0xBBD6 Aug 20 07:03:38 winters kernel: [2218062.876309] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B3EE (len 78, WS 12, PS 8) @ 0xB427 The last message before death appears to be: Aug 20 07:10:02 winters kernel: [2218447.006362] radeon :03:00.0: GPU reset succeeded, trying to resume ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-radeon 1:18.0.1-1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 20 10:18:42 2018 DistUpgraded: 2018-05-02 12:54:58,714 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-30-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland GL [FirePro W2100] [1002:6608] (prog-if 00 [VGA controller]) Subsystem: Dell Oland GL [FirePro W2100] [1028:2120] InstallationDate: Installed on 2018-01-05 (226 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Precision Tower 7810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to bionic on 2018-05-02 (109 days ago) dmi.bios.date: 06/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A27 dmi.board.name: 0KJCC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 7810 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubunt
[Kernel-packages] [Bug 1789634] Re: computer does not reemerge from hibernate
Do you have swap? Is the resume device correct? $ sudo blkid | grep swap $ grep RESUME -r /etc/initramfs-tools/ ** Changed in: systemd (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/1789634 Title: computer does not reemerge from hibernate Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: I put the computer in hibernate I came back and pressed start button to reawake machine. No response. Black screen. Had to force hard reboot to get machine back to functional status. lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 posting this to systemd as that is power management package (as I understand) apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 29 14:31:57 2018 InstallationDate: Installed on 2018-08-24 (4 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Studio 1737 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0P792H dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09: dmi.product.name: Studio 1737 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789634/+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 1790098] Re: vlan created on bond fails auto activation on updating parent network bond
** Package changed: linux (Ubuntu) => network-manager (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/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: New Status in network-manager package in Ubuntu: New Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not get activated Now, if manually I make vlan connection up, it gets activated: root@S36MANDAR:~# nmcli con up vlanbond.100 NAMEUUID TYP
[Kernel-packages] [Bug 1609143] Re: "lsluns" does not display ds8k lun information and unable to activate ds8k storage luns in host
** Tags removed: severity-medium ** Tags added: severity-low -- 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/1609143 Title: "lsluns" does not display ds8k lun information and unable to activate ds8k storage luns in host Status in Ubuntu on IBM z Systems: Expired Status in linux package in Ubuntu: Expired Bug description: == Comment: #2 - Steffen Maier - 2016-08-01 09:54:09 == While LTC bug 139096 - LP1567602 : FCP devices are not detected correctly nor deterministically did successfully fix the attachment of "regular" LUNs of (peripheral device) type disk, it seems the attachment of the (report luns) WLUN 0xc101 (49409) still shows issues with the ALUA device handler: [ 105.049479] scsi 0:0:7:49409: Well-known LUNIBM 2107900 .470 PQ: 0 ANSI: 5 [ 105.050109] scsi 0:0:7:49409: alua: disable for non-disk devices [ 105.050112] scsi 0:0:7:49409: alua: Attach failed (-22) [ 105.050114] scsi 0:0:7:49409: failed to add device handler: -22 After this failed attempt to attach such LUN (here triggered by the "lsluns" tool from s390-tools to discover LUNs from out of user space), the corresponding SCSI device is INvisible from user space, but still exists in-kernel in some broken state. In our case here, the attachment should have been successful (or the scsi_device been unregistered completely in maybe other cases). On the next attempt to run lsluns against the same target remote port and thus the same WLUN SCSI device, we get the following kernel warning as a follow-on error: [ 572.079588] scsi 0:0:7:49409: Well-known LUNIBM 2107900 .470 PQ: 0 ANSI: 5 [ 572.080354] sysfs: cannot create duplicate filename '/bus/scsi/devices/0:0:7:49409' [ 572.080380] [ cut here ] [ 572.080381] WARNING: at /build/linux-0ECIDW/linux-4.4.0/fs/sysfs/dir.c:31 [ 572.080381] Modules linked in: qeth_l3 chsc_sch eadm_sch qeth ccwgroup ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc btrfs zlib_deflate raid10 raid456 async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_round_robin ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common dasd_eckd_mod dasd_mod zfcp qdio scsi_transport_fc scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 572.080404] CPU: 1 PID: 8494 Comm: sh Not tainted 4.4.0-31-generic #50-Ubuntu [ 572.080405] task: 0001d7740af0 ti: 0001d8144000 task.ti: 0001d8144000 [ 572.080406] Krnl PSW : 0704c0018000 003a35fc (sysfs_warn_dup+0x7c/0x98) [ 572.080415]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 EA:3 Krnl GPRS: 00cf7034 0006 0047 [ 572.080417]003a35f8 02c6 0001da805400 0001d8f2f178 [ 572.080417]00c1d0e0 0001e8cd3ab8 0001 0001e8cd3ab8 [ 572.080418]0001d8cac4b0 7b7c8000 003a35f8 0001d81479b8 [ 572.080425] Krnl Code: 003a35ec: c020002f33f3larl %r2,989dd2 003a35f2: c0e5fff6bf0bbrasl %r14,27b408 #003a35f8: a7f40001brc 15,3a35fa >003a35fc: b904002dlgr %r2,%r13 003a3600: ebbff0a4lmg %r11,%r15,160(%r15) 003a3606: c0f4fffa5999brcl 15,2ee938 003a360c: a739lghi%r3,0 003a3610: a7f4ffecbrc 15,3a35e8 [ 572.080438] Call Trace: [ 572.080440] ([<003a35f8>] sysfs_warn_dup+0x78/0x98) [ 572.080443] [<003a3b10>] sysfs_do_create_link_sd.isra.0+0xf8/0x108 [ 572.080447] [<005c4004>] bus_add_device+0x13c/0x230 [ 572.080448] [<005c1718>] device_add+0x398/0x680 [ 572.080453] [<005f79bc>] scsi_sysfs_add_sdev+0xcc/0x2a8 [ 572.080456] [<005f4198>] scsi_probe_and_add_lun+0xcc0/0xe18 [ 572.080457] [<005f4be2>] __scsi_scan_target+0xba/0x268 [ 572.080458] [<005f4e92>] scsi_scan_target+0x102/0x120 [ 572.080468] [<03ff800765f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp] [ 572.080471] [<03ff80076948>] zfcp_unit_add+0x168/0x1f0 [zfcp] [ 572.080474] [<03ff80075564>] zfcp_sysfs_unit_add_store+0x54/0x70 [zfcp] [ 572.080476] [<003a1d7a>] kernfs_fop_write+0x13a/0x190 [ 572.080480] [<0030fc94>] vfs_write+0x94/0x1a0 [ 572.080482] [<003109a6>
[Kernel-packages] [Bug 1790006] Re: Update firmware udebs for 4.18
** Changed in: linux-firmware (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1790006 Title: Update firmware udebs for 4.18 Status in linux-firmware package in Ubuntu: Fix Committed Bug description: Update the linux firmware udeb file lists in cosmic for the 4.18 kernel in cosmic-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1790006/+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 1763774] Re: nvidia-driver-390 GDM black screen / hang after login
I am also affected by this since the latest upgrade which included among
others libX11, libmutter, mutter and libvulkan (full list attached). I
am using the Nvidia binary 396 drivers and everything was runnning fine
before. I could however circumvent the problem by ssh'ing into the
machine and simply stoping the gdm3.service and then restarting it.
However I could not switch to another TTY as suggested in the first
post. Hope this helps a bit to solve the issue.
** Attachment added: "upgraded.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1763774/+attachment/5182978/+files/upgraded.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1763774
Title:
nvidia-driver-390 GDM black screen / hang after login
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Confirmed
Bug description:
Ubuntu 18.04 x64 / gdm
AMD 1800x
Aorus Gaming K7 (x370 chipset) motherboard
NVidia GTX 1080Ti w/ DisplayPort attached 4k monitor
USB keyboard / mouse
I've recently upgraded from Ubuntu 17.10 x64 to 18.04 x64 via
`do-release-upgrade -d` and uninstalled / purged / reinstalled my NVidia
native drivers using the `ubuntu-drivers autoinstall` approach.
I am able to boot the system and it displays the X login shell at native
resolution with a functioning keyboard and mouse, but I cannot
ctrl+alt+F{1,2,3,4,...} to a non-graphical terminal.
When I click "Sign in" using gnome 3, gnome classic, or Unity, I get a
black screen and my input devices hang (keyboard caps lock key no longer
functions.) If I unplug and replug my input devices, they remain
hanging, with a stuck-on capslock indicator. The mouse is also
illuminated.
I am able to SSH into the machine, and it is still usable. systemctl
status gdm.service indicates that gdm is "running" and does not show an
error, but it shows that the login session opened and closed very quickly.
I rebooted and SSH'd into the machine before the hang, halted GDM via
`systemctl stop gdm.service` and was able to ctrl+alt+F1 into another
shell on the attached keyboard. I then executed `systemctl restart
gdm.service` and got the expected X login shell. I was then able to log
into the desktop environment normally.
My Xorg.0.log is here for the successful login:
https://paste.ubuntu.com/p/SNqJPxV938/
I'll reproduce the behavior and attach an xorg log for the unexpected
behavior.
Bodie
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-driver-390 390.48-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Fri Apr 13 12:43:48 2018
InstallationDate: Installed on 2017-10-30 (165 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: nvidia-graphics-drivers-390
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1763774/+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 1788730] Re: TP-LINK TG-3468 network card not recognized correctly
** Changed in: linux (Ubuntu) Status: In Progress => 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/1788730 Title: TP-LINK TG-3468 network card not recognized correctly Status in linux package in Ubuntu: Confirmed Bug description: A few days ago purchased a couple of TP-LINK TG-3468 network cards (reviewed by Phoronix here: https://www.phoronix.com/scan.php?page=news_item&px=MTY2ODQ), both brand new, not reused. After installed them to a pc, to my surprise, one of them was correctly identified and the other was incorrectly identified as "NCube Device 8168 (rev 06)". After DuckDuckGoing for a while I found this kernel bud report for FreeBSD: https://forums.freebsd.org/threads/not-recognized-pci-e -network-card.57734/ IMHO is the same issue but I'm using Ubuntu 16.04.5 server i686. I wanted to report this so it can be fixed, please let me know wich logs/data should I provide. When ran lspci -nv this is shown for the correct nic: 03:00.0 0200: 10ec:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 27 I/O ports at e800 [size=256] Memory at febff000 (64-bit, non-prefetchable) [size=4K] Memory at fdffc000 (64-bit, prefetchable) [size=16K] Capabilities: Kernel driver in use: r8169 Kernel modules: r8169 And this for the incorrect one: 01:00.0 0200: 10ff:8168 (rev 06) Subsystem: 7470:3468 Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c800 [size=256] Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K] Memory at fdefc000 (64-bit, prefetchable) [size=16K] Capabilities: 1) lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 2) In regard to the package I think this is related to the kernel itself? 3) Both cards should be identified as "Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" and the r8169 driver should be used. 4) The network card was erroneously detected as a different one and the driver was not loaded by the kernel. Best regards. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-133-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=652853e2-bd7e-44bb-9b13-f2c9c3823791 InstallationDate: Installed on 2017-12-06 (260 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic root=UUID=89ec3fdb-2ccd-497a-8657-bbe2b53393ed ro ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 RelatedPackageVersions: linux-restricted-modules-4.4.0-133-generic N/A linux-backports-modules-4.4.0-133-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-133-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/27/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-CM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.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.:bvr0702:bd08/27/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-CM:rvrx.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/ubuntu/+source/linux/+bug/1788730/+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 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1788758 Title: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788758/+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 1780067] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-08-31 07:51 EDT---
IBM bugzilla status -> closed, Fix Released by Canonical
--
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/1780067
Title:
zfcp: fix infinite iteration on ERP ready list
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
Please backport:
commit fa89adba1941e4f3b213399b81732a5c12fd9131
scsi: zfcp: fix infinite iteration on ERP ready list
zfcp_erp_adapter_reopen() schedules blocking of all of the adapter's
rports via zfcp_scsi_schedule_rports_block() and enqueues a reopen
adapter ERP action via zfcp_erp_action_enqueue(). Both are separately
processed asynchronously and concurrently.
Blocking of rports is done in a kworker by zfcp_scsi_rport_work(). It
calls zfcp_scsi_rport_block(), which then traces a DBF REC "scpdely" via
zfcp_dbf_rec_trig(). zfcp_dbf_rec_trig() acquires the DBF REC spin lock
and then iterates with list_for_each() over the adapter's ERP ready list
without holding the ERP lock. This opens a race window in which the
current list entry can be moved to another list, causing list_for_each()
to iterate forever on the wrong list, as the erp_ready_head is never
encountered as terminal condition.
Meanwhile the ERP action can be processed in the ERP thread by
zfcp_erp_thread(). It calls zfcp_erp_strategy(), which acquires the ERP
lock and then calls zfcp_erp_action_to_running() to move the ERP action
from the ready to the running list. zfcp_erp_action_to_running() can
move the ERP action using list_move() just during the aforementioned
race window. It then traces a REC RUN "erator1" via zfcp_dbf_rec_run().
zfcp_dbf_rec_run() tries to acquire the DBF REC spin lock. If this is
held by the infinitely looping kworker, it effectively spins forever.
Example Sequence Diagram:
ProcessERP Thread rport_work
---------
zfcp_erp_adapter_reopen()
zfcp_erp_adapter_block()
zfcp_scsi_schedule_rports_block()
lock ERP zfcp_scsi_rport_work()
zfcp_erp_action_enqueue(ZFCP_ERP_ACTION_REOPEN_ADAPTER)
list_add_tail() on ready !(rport_task==RPORT_ADD)
wake_up() ERP thread zfcp_scsi_rport_block()
zfcp_dbf_rec_trig()zfcp_erp_strategy()zfcp_dbf_rec_trig()
unlock ERPlock DBF REC
zfcp_erp_wait()lock ERP
| zfcp_erp_action_to_running()
| list_for_each() ready
| list_move() current entry
|ready to running
| zfcp_dbf_rec_run() endless loop over running
| zfcp_dbf_rec_run_lvl()
| lock DBF REC spins forever
Any adapter recovery can trigger this, such as setting the device offline
or reboot.
V4.9 commit 4eeaa4f3f1d6 ("zfcp: close window with unblocked rport
during rport gone") introduced additional tracing of (un)blocking of
rports. It missed that the adapter->erp_lock must be held when calling
zfcp_dbf_rec_trig().
This fix uses the approach formerly introduced by commit aa0fec62391c
("[SCSI] zfcp: Fix sparse warning by providing new entry in dbf") that got
later removed by commit ae0904f60fab ("[SCSI] zfcp: Redesign of the debug
tracing for recovery actions.").
Introduce zfcp_dbf_rec_trig_lock(), a wrapper for zfcp_dbf_rec_trig() that
acquires and releases the adapter->erp_lock for read.
Reported-by: Sebastian Ott
Signed-off-by: Jens Remus
Fixes: 4eeaa4f3f1d6 ("zfcp: close window with unblocked rport during
rport gone")
Cc: # 2.6.32+
Reviewed-by: Benjamin Block
Signed-off-by: Steffen Maier
Signed-off-by: Martin K. Petersen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1780067/+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 1788769] Re: linux-aws: 4.4.0-1067.77 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788769 Title: linux-aws: 4.4.0-1067.77 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788766 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788769/+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 1780067] Re: zfcp: fix infinite iteration on ERP ready list
Since we are on 4.15.0.33.35 with bionic, I'm marking bionic as Fix
Released and close the ticket.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1780067
Title:
zfcp: fix infinite iteration on ERP ready list
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
Please backport:
commit fa89adba1941e4f3b213399b81732a5c12fd9131
scsi: zfcp: fix infinite iteration on ERP ready list
zfcp_erp_adapter_reopen() schedules blocking of all of the adapter's
rports via zfcp_scsi_schedule_rports_block() and enqueues a reopen
adapter ERP action via zfcp_erp_action_enqueue(). Both are separately
processed asynchronously and concurrently.
Blocking of rports is done in a kworker by zfcp_scsi_rport_work(). It
calls zfcp_scsi_rport_block(), which then traces a DBF REC "scpdely" via
zfcp_dbf_rec_trig(). zfcp_dbf_rec_trig() acquires the DBF REC spin lock
and then iterates with list_for_each() over the adapter's ERP ready list
without holding the ERP lock. This opens a race window in which the
current list entry can be moved to another list, causing list_for_each()
to iterate forever on the wrong list, as the erp_ready_head is never
encountered as terminal condition.
Meanwhile the ERP action can be processed in the ERP thread by
zfcp_erp_thread(). It calls zfcp_erp_strategy(), which acquires the ERP
lock and then calls zfcp_erp_action_to_running() to move the ERP action
from the ready to the running list. zfcp_erp_action_to_running() can
move the ERP action using list_move() just during the aforementioned
race window. It then traces a REC RUN "erator1" via zfcp_dbf_rec_run().
zfcp_dbf_rec_run() tries to acquire the DBF REC spin lock. If this is
held by the infinitely looping kworker, it effectively spins forever.
Example Sequence Diagram:
ProcessERP Thread rport_work
---------
zfcp_erp_adapter_reopen()
zfcp_erp_adapter_block()
zfcp_scsi_schedule_rports_block()
lock ERP zfcp_scsi_rport_work()
zfcp_erp_action_enqueue(ZFCP_ERP_ACTION_REOPEN_ADAPTER)
list_add_tail() on ready !(rport_task==RPORT_ADD)
wake_up() ERP thread zfcp_scsi_rport_block()
zfcp_dbf_rec_trig()zfcp_erp_strategy()zfcp_dbf_rec_trig()
unlock ERPlock DBF REC
zfcp_erp_wait()lock ERP
| zfcp_erp_action_to_running()
| list_for_each() ready
| list_move() current entry
|ready to running
| zfcp_dbf_rec_run() endless loop over running
| zfcp_dbf_rec_run_lvl()
| lock DBF REC spins forever
Any adapter recovery can trigger this, such as setting the device offline
or reboot.
V4.9 commit 4eeaa4f3f1d6 ("zfcp: close window with unblocked rport
during rport gone") introduced additional tracing of (un)blocking of
rports. It missed that the adapter->erp_lock must be held when calling
zfcp_dbf_rec_trig().
This fix uses the approach formerly introduced by commit aa0fec62391c
("[SCSI] zfcp: Fix sparse warning by providing new entry in dbf") that got
later removed by commit ae0904f60fab ("[SCSI] zfcp: Redesign of the debug
tracing for recovery actions.").
Introduce zfcp_dbf_rec_trig_lock(), a wrapper for zfcp_dbf_rec_trig() that
acquires and releases the adapter->erp_lock for read.
Reported-by: Sebastian Ott
Signed-off-by: Jens Remus
Fixes: 4eeaa4f3f1d6 ("zfcp: close window with unblocked rport during
rport gone")
Cc: # 2.6.32+
Reviewed-by: Benjamin Block
Signed-off-by: Steffen Maier
Signed-off-by: Martin K. Petersen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1780067/+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 1788750] Re: linux-aws: 4.15.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1788750 Title: linux-aws: 4.15.0-1021.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1788744 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788750/+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 1790125] Re: Ubuntu18.10 - Bring ocxl driver in 18.10 to same level as 18.04.1
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: ubuntu-power-systems Importance: Undecided => Medium ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g -- 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/1790125 Title: Ubuntu18.10 - Bring ocxl driver in 18.10 to same level as 18.04.1 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Frederic Barrat - 2018-08-31 02:41:58 == ---Problem Description--- bring ocxl driver in 18.10 to same level as in 18.04.1 ---uname output--- Linux zaiuslp14 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:43:33 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- opencapi adapter needed to use ocxl driver Machine Type = power9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Contact Information = frederic.bar...@fr.ibm.com Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for frederic.bar...@fr.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #1 - Frederic Barrat - 2018-08-31 02:48:24 == An important fix for the ocxl driver (opencapi driver for POWER9) is missing in kernel 4.18. It was merged during the 4.19 merge window. The fix is already in 18.04.1, so it needs to be added to the 18.10 kernel to avoid regression. The commit ID is: d497ebf5fb3a026c0817f8c96cde578787f24093 ocxl: Fix page fault handler in case of fault on dying process Could you add it to the kernel for 18.10? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790125/+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
