[Kernel-packages] [Bug 2017308] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: o subprocesso instalado, do pacote linux-headers-6.2.0-20-generic, o script post-ins
Public bug reported: o subprocesso instalado, do pacote linux-headers-6.2.0-20-generic, o script post-installation retornou erro do status de saída 1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1294 F wireplumber /dev/snd/seq:roberto1278 F pipewire CasperMD5CheckResult: unknown Date: Fri Apr 21 15:55:07 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 ErrorMessage: o subprocesso instalado, do pacote linux-headers-6.2.0-20-generic, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2021-03-01 (781 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3480 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=f6463611-f1d7-4b66-9d57-1cefb858b774 ro mem_sleep_default=deep usbcore.quirks=2386:3119:k quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: o subprocesso instalado, do pacote linux-headers-6.2.0-20-generic, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 12/19/2022 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.1 dmi.board.name: 06256N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.1:bd12/19/2022:br1.22:svnDellInc.:pnInspiron3480:pvr:rvnDellInc.:rn06256N:rvrA00:cvnDellInc.:ct10:cvr:sku08C7: dmi.product.family: Inspiron dmi.product.name: Inspiron 3480 dmi.product.sku: 08C7 dmi.sys.vendor: Dell Inc. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- 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/2017308 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: o subprocesso instalado, do pacote linux- headers-6.2.0-20-generic, o script post-installation retornou erro do status de saída 1 Status in linux package in Ubuntu: New Bug description: o subprocesso instalado, do pacote linux-headers-6.2.0-20-generic, o script post-installation retornou erro do status de saída 1 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1294 F wireplumber /dev/snd/seq: roberto1278 F pipewire CasperMD5CheckResult: unknown Date: Fri Apr 21 15:55:07 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 ErrorMessage: o subprocesso instalado, do pacote linux-headers-6.2.0-20-generic, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2021-03-01 (781 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560
[Kernel-packages] [Bug 2003779] [NEW] linux-oem-22.04 should point to the latest of the linux-oem-22.04* kernels and not the first
Public bug reported: The description of this package says: "This package will always depend on the latest complete OEM Linux kernel and headers." but, despite Ubuntu 22.04 having 3 different versions of the oem kernels (linux- oem-22.04a, linux-oem-22.04b and linux-oem-22.04c), this meta package points to the first (linux-oem-22.04a) instead of the last (linux- oem-22.04c). There should be a way to install a meta package pointing always to the latest complete OEM Linux kernel and headers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04 (not installed) ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 24 12:09:18 2023 InstallationDate: Installed on 2021-12-14 (405 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-meta-oem-5.17 UpgradeStatus: Upgraded to jammy on 2022-04-28 (270 days ago) ** Affects: linux-meta-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2003779 Title: linux-oem-22.04 should point to the latest of the linux-oem-22.04* kernels and not the first Status in linux-meta-oem-5.17 package in Ubuntu: New Bug description: The description of this package says: "This package will always depend on the latest complete OEM Linux kernel and headers." but, despite Ubuntu 22.04 having 3 different versions of the oem kernels (linux- oem-22.04a, linux-oem-22.04b and linux-oem-22.04c), this meta package points to the first (linux-oem-22.04a) instead of the last (linux- oem-22.04c). There should be a way to install a meta package pointing always to the latest complete OEM Linux kernel and headers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04 (not installed) ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 24 12:09:18 2023 InstallationDate: Installed on 2021-12-14 (405 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-meta-oem-5.17 UpgradeStatus: Upgraded to jammy on 2022-04-28 (270 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.17/+bug/2003779/+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 1928691] [NEW] package linux-headers-5.8.0-53 5.8.0-53.60 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/
Public bug reported: Getting error message after log in or after any package update. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-headers-5.8.0-53 5.8.0-53.60 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun May 16 21:07:11 2021 ErrorMessage: não pode copiar dados extráidos para './usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile' para '/usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile.dpkg-new': falhou a escrita (Sem espaço livre no dispositivo) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PackageArchitecture: all ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=63c32f9f-5681-43ab-a344-9453024dffd5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-5.8.0-53 5.8.0-53.60 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile' para '/usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile.dpkg-new': falhou a escrita (Sem espaço livre no dispositivo) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 7152-2433-7923-1971-9356-1586-36 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package groovy -- 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/1928691 Title: package linux-headers-5.8.0-53 5.8.0-53.60 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux- headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile' para '/usr/src/linux- headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile .dpkg-new': falhou a escrita (Sem espaço livre no dispositivo) Status in linux package in Ubuntu: Confirmed Bug description: Getting error message after log in or after any package update. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-headers-5.8.0-53 5.8.0-53.60 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun May 16 21:07:11 2021 ErrorMessage: não pode copiar dados extráidos para './usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile' para '/usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile.dpkg-new': falhou a escrita (Sem espaço livre no dispositivo) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PackageArchitecture: all ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=63c32f9f-5681-43ab-a344-9453024dffd5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd',
[Kernel-packages] [Bug 1901025] [NEW] rtl8723ae wireless card doesn't work
Public bug reported: rtl8723ae wireless card is detected with included kernel module and it loads without errors, but it doesn't detect or show any available wireless network. /lib/modules/5.4.0-52-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723ae/rtl8723ae.ko ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: roberto1515 F pulseaudio /dev/snd/controlC0: roberto1515 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 09:14:29 2020 InstallationDate: Installed on 2020-08-31 (51 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ' ' ' ' ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/DISCO-ROOT ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IIA.20I dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ' ' dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IIA.20I:bd07/01/2014:svn'':pn'':pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvn'':ct10:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: ' ' dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: ' ' ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal wayland-session -- 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/1901025 Title: rtl8723ae wireless card doesn't work Status in linux package in Ubuntu: Confirmed Bug description: rtl8723ae wireless card is detected with included kernel module and it loads without errors, but it doesn't detect or show any available wireless network. /lib/modules/5.4.0-52-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8723ae/rtl8723ae.ko ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: roberto1515 F pulseaudio /dev/snd/controlC0: roberto1515 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 09:14:29 2020 InstallationDate: Installed on 2020-08-31 (51 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ' ' ' ' ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/DISCO-ROOT ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IIA.20I dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ' ' dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IIA.20I:bd07/01/2014:svn'':pn'':pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvn'':ct10:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: ' ' dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: ' ' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901025/+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 1855619] [NEW] Touchpad not working Eoan
Public bug reported: My laptop is an Acer Aspire F5-571. It doesn't detect my touchpad when I decided to install Ubuntu 19.10. I have disabled advanced functions of the touchpad (because I think it had issues with I2C). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: barrosorbf 1326 F pulseaudio /dev/snd/controlC0: barrosorbf 1326 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:10:38 2019 InstallationDate: Installed on 2019-12-08 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire F5-571 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=53242bb9-2591-4fba-b598-04911527760d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireF5-571:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire F5-571 dmi.product.sku: Aspire F5-571_098A_1_37 dmi.product.version: V3.72 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1855619/+attachment/5310862/+files/devices -- 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/1855619 Title: Touchpad not working Eoan Status in linux package in Ubuntu: New Bug description: My laptop is an Acer Aspire F5-571. It doesn't detect my touchpad when I decided to install Ubuntu 19.10. I have disabled advanced functions of the touchpad (because I think it had issues with I2C). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: barrosorbf 1326 F pulseaudio /dev/snd/controlC0: barrosorbf 1326 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 11:10:38 2019 InstallationDate: Installed on 2019-12-08 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire F5-571 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=53242bb9-2591-4fba-b598-04911527760d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireF5-571:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire F5-571 dmi.product.sku: Aspire F5-571_098A_1_37 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855619/+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 1827314] Re: Ubuntu 19.04 Background and lockscreen image turns into white noise after sleep and wakeup
** Also affects: gnome-desktop (Ubuntu) Importance: Undecided Status: 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/1827314 Title: Ubuntu 19.04 Background and lockscreen image turns into white noise after sleep and wakeup Status in gnome-desktop package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 Background and lockscreen image turns into white noise after sleep and wakeup the lock screen is Disco Dingo default image and bg is custom but both turn into a noisy broken image my laptop is MSI CX627QL Core i5 7th gen Ram 12 gb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1827314/+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 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
Hello, I was affected, I just now tried to re-install nvidia-390 (I purged everything about nvidia) "sudo apt-get install nvidia-390", and after that and reboot everything works fine with 18.04 hwe kernel 390.87 nvidia driver installed (the link in the posts above is about 390.77 version), I don't know if my box get it from main repository or from nvidia-ppa, maybe second one for me bug is closed -- 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/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04
[Kernel-packages] [Bug 1765105] Re: HP Smart Array driver fails to load, kernel panics boot process
*** This bug is a duplicate of bug 1765232 *** https://bugs.launchpad.net/bugs/1765232 Bug can be closed, it's a problem about fw card and hpsa, please update fw of your p400 card and it will works at 100% -- 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/1765105 Title: HP Smart Array driver fails to load, kernel panics boot process Status in linux package in Ubuntu: Confirmed Bug description: Hi I have an HP ProLiant G6 with a Smart Array controller on Bionic, Kernel 4.15.0-15, that fails to load the hpsa driver for the Smart Array, (occasionally) drops to the initramfs shell, as it cannot find a root device in a reasonable amount of time, and then finally kernel panics with the stack trace leading to the hpsa driver. Occasionally it will complain about resetting the logical volume scsi bus. Downgrading to the previous kernel 4.15.0-13 works just fine. Attached is a screenshot showing the kernel panic, and below is a link to a YouTube video of the whole boot process, a video recording from ILO. To save you the time of watching the whole thing, 39 seconds is the bus reset error, then it hangs around waiting for a root device, and the kernel panics at 4:16. The relevant information are separate below Video: https://youtu.be/45ka2Btgiqk lsb_release: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765105/+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 1779458] [NEW] zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build
Public bug reported: Mesmo de Wifi ligado ele não se conecta a rede e tem que botar senha. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu24 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-130-generic (i686) Sex Jun 29 22:37:31 -03 2018 make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. DKMSKernelVersion: 4.4.0-130-generic Date: Fri Jun 29 22:38:59 2018 InstallationDate: Installed on 2016-07-16 (714 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageVersion: 0.6.5.6-0ubuntu24 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-from-proposed xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1779458 Title: zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: Mesmo de Wifi ligado ele não se conecta a rede e tem que botar senha. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu24 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-130-generic (i686) Sex Jun 29 22:37:31 -03 2018 make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. DKMSKernelVersion: 4.4.0-130-generic Date: Fri Jun 29 22:38:59 2018 InstallationDate: Installed on 2016-07-16 (714 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageVersion: 0.6.5.6-0ubuntu24 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1779458/+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 1765105] Re: HP Smart Array driver fails to load, kernel panics boot process
*** This bug is a duplicate of bug 1765232 *** https://bugs.launchpad.net/bugs/1765232 without P400 card : https://www.youtube.com/watch?v=d05vwUg5WtI tested also to pass at grub parameters to disable spectre and meltdown, 100% HPSA issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765105 Title: HP Smart Array driver fails to load, kernel panics boot process Status in linux package in Ubuntu: Confirmed Bug description: Hi I have an HP ProLiant G6 with a Smart Array controller on Bionic, Kernel 4.15.0-15, that fails to load the hpsa driver for the Smart Array, (occasionally) drops to the initramfs shell, as it cannot find a root device in a reasonable amount of time, and then finally kernel panics with the stack trace leading to the hpsa driver. Occasionally it will complain about resetting the logical volume scsi bus. Downgrading to the previous kernel 4.15.0-13 works just fine. Attached is a screenshot showing the kernel panic, and below is a link to a YouTube video of the whole boot process, a video recording from ILO. To save you the time of watching the whole thing, 39 seconds is the bus reset error, then it hangs around waiting for a root device, and the kernel panics at 4:16. The relevant information are separate below Video: https://youtu.be/45ka2Btgiqk lsb_release: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765105/+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 1765105] Re: HP Smart Array driver fails to load, kernel panics boot process
*** This bug is a duplicate of bug 1765232 *** https://bugs.launchpad.net/bugs/1765232 I have same problem on HP Proliant ML350 G5 on P400 smart array board, it's a kernel issue, last working kernel from ubuntu ppa or kernel.org is 4.13.16 >From kernel 4.14.1, no boot Tested also other live distrobutions with kernel 4.15 or 4.14 same issue, I opened a bug on bugzilla.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/1765105 Title: HP Smart Array driver fails to load, kernel panics boot process Status in linux package in Ubuntu: Confirmed Bug description: Hi I have an HP ProLiant G6 with a Smart Array controller on Bionic, Kernel 4.15.0-15, that fails to load the hpsa driver for the Smart Array, (occasionally) drops to the initramfs shell, as it cannot find a root device in a reasonable amount of time, and then finally kernel panics with the stack trace leading to the hpsa driver. Occasionally it will complain about resetting the logical volume scsi bus. Downgrading to the previous kernel 4.15.0-13 works just fine. Attached is a screenshot showing the kernel panic, and below is a link to a YouTube video of the whole boot process, a video recording from ILO. To save you the time of watching the whole thing, 39 seconds is the bus reset error, then it hangs around waiting for a root device, and the kernel panics at 4:16. The relevant information are separate below Video: https://youtu.be/45ka2Btgiqk lsb_release: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765105/+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 1771535] Re: synaptics trackpad not detected by libinput
** Attachment added: "/proc/bus/input/devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+attachment/5140272/+files/devices -- 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/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Confirmed Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+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 1771535] Re: synaptics trackpad not detected by libinput
** Attachment added: "lspci -vnvn" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+attachment/5140273/+files/lspci-vnvn.log -- 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/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Confirmed Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+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 1771535] Re: synaptics trackpad not detected by libinput
On the other hand, it was working perfectly during installation from the live CD menu. -- 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/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Confirmed Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+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 1771535] [NEW] synaptics trackpad not detected by libinput
Public bug reported: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Attachment added: "dmesg output" https://bugs.launchpad.net/bugs/1771535/+attachment/5140256/+files/dmesg -- 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/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Confirmed Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware
Re: [Kernel-packages] [Bug 1760141] Re: zfs-dkms 0.6.5.6-0ubuntu20: zfs kernel module failed to build
Boa Tarde, Leo Barbosa Por favor, escreva em nossa língua. Língua por língua futuramente o inglês será trocado por Esperanto ou Mandarim. É por que seria mais fácil... Abraços, José Roberto Catão Miranda 2018-04-02 12:23 GMT-03:00 Leonidas S. Barbosa <1760...@bugs.launchpad.net>: > Hi Jose Roberto, > > Thanks for taking the time to report this bug and helping to make Ubuntu > better. We appreciate the difficulties you are facing, but this appears > to be a "regular" (non-security) bug. I have unmarked it as a security > issue since this bug does not show evidence of allowing attackers to > cross privilege boundaries nor directly cause loss of data/privacy. > Please feel free to report any other bugs you may find. > > ** Information type changed from Private Security to Public > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1760141 > > Title: > zfs-dkms 0.6.5.6-0ubuntu20: zfs kernel module failed to build > > Status in zfs-linux package in Ubuntu: > Confirmed > > Bug description: > Erro ao rodar zfs-dkms 0.6.5.6-0ubuntu20: > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: zfs-dkms 0.6.5.6-0ubuntu20 > ProcVersionSignature: Ubuntu 4.4.0-118.142-generic 4.4.114 > Uname: Linux 4.4.0-118-generic i686 > NonfreeKernelModules: zfs zunicode zcommon znvpair zavl > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: i386 > DKMSBuildLog: >DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-118-generic (i686) >Sex Mar 30 11:52:36 -03 2018 >make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. > DKMSKernelVersion: 4.4.0-118-generic > Date: Fri Mar 30 11:54:00 2018 > InstallationDate: Installed on 2016-07-16 (622 days ago) > InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 > (20160420.1) > PackageVersion: 0.6.5.6-0ubuntu20 > RelatedPackageVersions: >dpkg 1.18.4ubuntu1.4 >apt 1.2.26 > SourcePackage: zfs-linux > Title: zfs-dkms 0.6.5.6-0ubuntu20: zfs kernel module failed to build > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/ > 1760141/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1760141 Title: zfs-dkms 0.6.5.6-0ubuntu20: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: Erro ao rodar zfs-dkms 0.6.5.6-0ubuntu20: ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu20 ProcVersionSignature: Ubuntu 4.4.0-118.142-generic 4.4.114 Uname: Linux 4.4.0-118-generic i686 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-118-generic (i686) Sex Mar 30 11:52:36 -03 2018 make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. DKMSKernelVersion: 4.4.0-118-generic Date: Fri Mar 30 11:54:00 2018 InstallationDate: Installed on 2016-07-16 (622 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageVersion: 0.6.5.6-0ubuntu20 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu20: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1760141/+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 1701158] [NEW] package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1701085 *** https://bugs.launchpad.net/bugs/1701085 Public bug reported: Tried to do the update. It was installing OS updates and a Gnome File Manager. Got stuck on the inatalling - progress bar was about 2/3. Waited about 2 hrs, no change so I rebooted the machine and got this error message about failure to install this package... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rrenzetti 1957 F pulseaudio /dev/snd/controlC0: rrenzetti 1957 F pulseaudio Date: Wed Jun 28 21:15:20 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=bfa7d3a4-b058-482f-ba58-a1675e59ecfc InstallationDate: Installed on 2016-11-26 (215 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: LENOVO 4352H1U ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-81-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: A2KT34AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA2KT34AUS:bd12/05/2013:svnLENOVO:pn4352H1U:pvrThinkStationS30:rvnLENOVO:rnLENOVO:rvr0B98401PRO:cvnLENOVO:ct7:cvrNONE: dmi.product.name: 4352H1U dmi.product.version: ThinkStation S30 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package xenial -- 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/1701158 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Tried to do the update. It was installing OS updates and a Gnome File Manager. Got stuck on the inatalling - progress bar was about 2/3. Waited about 2 hrs, no change so I rebooted the machine and got this error message about failure to install this package... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rrenzetti 1957 F pulseaudio /dev/snd/controlC0: rrenzetti 1957 F pulseaudio Date: Wed Jun 28 21:15:20 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=bfa7d3a4-b058-482f-ba58-a1675e59ecfc InstallationDate: Installed on 2016-11-26 (215 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: LENOVO 4352H1U ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-81-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: A2KT34AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA2KT34AUS:bd12/05/2013:svnLENOVO:pn4352H1U:pvrThinkStationS30:rvnLENOVO:rnLENOVO:rvr0B98401PRO:cvnLENOVO:ct7:cvrNONE: dmi.product.name: 4352H1U dmi.product.version:
[Kernel-packages] [Bug 1696275] [NEW] package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: >From the software OS update the install button freeze. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1497 F pulseaudio Date: Tue Jun 6 20:37:23 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-21 (46 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard Compaq Presario CQ40 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=c18f4347-46ed-41bf-9cbb-8aac62426e5a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.51 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3607 dmi.board.vendor: Compal dmi.board.version: 99.B4 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.51:bd08/17/2009:svnHewlett-Packard:pnCompaqPresarioCQ40NotebookPC:pvr039212200D101:rvnCompal:rn3607:rvr99.B4:cvnCompal:ct10:cvrN/A: dmi.product.name: Compaq Presario CQ40 Notebook PC dmi.product.version: 039212200D101 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- 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/1696275 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: From the software OS update the install button freeze. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1497 F pulseaudio Date: Tue Jun 6 20:37:23 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-21 (46 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard Compaq Presario CQ40 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic root=UUID=c18f4347-46ed-41bf-9cbb-8aac62426e5a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.51 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3607 dmi.board.vendor: Compal dmi.board.version: 99.B4 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.51:bd08/17/2009:svnHewlett-Packard:pnCompaqPresarioCQ40NotebookPC:pvr039212200D101:rvnCompal:rn3607:rvr99.B4:cvnCompal:ct10:cvrN/A: dmi.product.name: Compaq Presario CQ40 Notebook PC dmi.product.version: 039212200D101 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696275/+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 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
Glad it works for you too. It would be interesting to investigate what has this distribution that prevents the bug to show up. May be the desktop environment, Budgie, which is unique? There's a Budgie version for Arch: https://www.archlinux.org/packages/community/x86_64/budgie-desktop/ which may be worth trying to this means. -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
Just wanted to report that I no longer have this issue since I installed the Solus distribution: https://solus-project.com/ I was also affected by the fan bug just cited in the previous comment, which also seems to have been solved with Solus: https://bugzilla.kernel.org/show_bug.cgi?id=153281 I had tried the latest Fedora 25 just before Solus, but couldn't even complete the installation wizard: it hanged with "soft lockup - CPU#0 stuck for 22s!". I've been running the Solus distribution for some days now and didn't get fans or NMI watchdog issues anymore. Also no boot options have been required. My machine is an Asus K550V laptop, Intel Core i7-6700HQ with NVidia Geforce GTX 950M. Hope this helps. -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I am affected with 16.04, kernel 4.4.0-51-generic. The only way I could make my system work has been to install initial Ubuntu 16.04 and not upgrade any single package since installation. I used to have hangs even before login, so I enabled auto-login without password and things got better. I still have lockups during shutdown, so I need to hard-shutdown the PC every time, but at least the working sessions go smooth. My system is an ASUS K550V, Intel Core i7-6700HQ, NVIDIA Geforce GTX 950M. -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [
[Kernel-packages] [Bug 1449910] Re: System hangs apparently randomly when disconnecting iScsi volumes
It's been a full year now, without any problem. Definitely, the 4.1 kernel works well (and also the 4.0.1, which I'm running on one of the machines). Tomorrow I will start the software upgrade of these machines to the latest LTS distribution (16.04.1), which runs the 4.4 kernel, which I trust should be running well. Are there any news about 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/1449910 Title: System hangs apparently randomly when disconnecting iScsi volumes Status in linux package in Ubuntu: Triaged Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace: /0x70 Apr 21 23:02:56 server-name kernel: [654840.108419] [] reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108426] [] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108437] [] do_journal_begin_r+0xe1/0x3e0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108443] [] ? __enqueue_entity+0x78/0x80 Apr 21 23:02:56 server-name kernel: [654840.108454] [] journal_begin+0x8a/0x160 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108464] [] reiserfs_release_dquot+0x4c/0xd0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108470] [] ? __percpu_counter_add+0x51/0x70 Apr 21 23:02:56 server-name kernel: [654840.108476] [] dqput+0x9d/0x200 Apr 21 23:02:56 server-name kernel: [654840.108480] [] __dquot_drop+0x5d/0x70 Apr 21 23:02:56 server-name kernel: [654840.108485] [] dquot_drop+0x2d/0x40 Apr 21 23:02:56 server-name kernel: [654840.108494] [] reiserfs_evic t_inode+0xa0/0x180 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108501] [] ? inode_wait_for_writeback+0x2e/0x40 Apr 21 23:02:56 server-name kernel: [654840.108507] [] evict+0xb4/0x180 Apr 21 23:02:56 server-name kernel: [654840.108511] [] dispose_list+0x39/0x50 Apr 21 23:02:56 server-name kernel: [654840.108515] [] prune_icache_sb+0x47/0x60 Apr 21 23:02:56 server-name kernel: [654840.108520] [] super_cache_scan+0x105/0x170 Apr 21 23:02:56 server-name kernel: [654840.108526] [] shrink_slab_node+0x138/0x290 Apr 21 23:02:56 server-name kernel: [654840.108532] [] ? css_next_descendant_pre+0x3b/0x40 Apr 21 23:02:56 server-name kernel: [654840.108536] [] shrink_slab+0x8b/0x160 Apr 21 23:02:56 server-name kernel: [654840.108540] [] balance_pgdat+0x3f2/0x620 Apr 21 23:02:56 server-name kernel: [654840.108544] [] kswapd+0x15b/0x3f0 Apr 21 23:02:56 server-name kernel: [654840.108549] [] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108552] [] ? balance_pgdat+0x620/0x620 Apr 21 23:02:56 server-name kernel: [654840.108558] [] kthread+0xd2/0xf0 Apr 21 23:02:56 server-name kernel: [654840.108562] [] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108567] [] ret_from_fork+0x7c/0xb0 Apr 21 23:02:56 server-name kernel: [654840.108571] [] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108595] INFO: task kworker/1:1:25606 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108709] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108809] "echo 0 >
[Kernel-packages] [Bug 1613359] Re: Xrandr gamma and brightness problem on 4.4.0-34 kernel
I have an update, after my post above, I checked manually if there were any updates. sudo apt update apt list --upgradable I noticed that there was a new version of the kernel to be updated. 4.4.0-36-generic I have updated: sudo apt upgrade Restarted the computer the problem with brightness and gamma has disappeared. This behavior is normal. -- 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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Confirmed Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] Re: Xrandr gamma and brightness problem on 4.4.0-34 kernel
Sorry but I'm a low-level user and the distribution I am using is that of daily productivity. I risk to mix packages that I can not recover. I am sorry not to be able to deepen my 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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Confirmed Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] Re: Xrandr gamma and brightness problem on 4.4.0-34 kernel
kernel-unable-to-test-upstream I have installed the package that you have shown me, as explained in the wiki but with errors, missing dependency. I am unable to boot the mainline kernel. Sorry. -- 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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721368/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721367/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721372/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721371/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721370/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721380/+files/WifiSyslog.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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721369/+files/JournalErrors.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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721376/+files/PulseList.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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721366/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721377/+files/RfKill.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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721374/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721373/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721379/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721375/+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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80E5 dmi.board.vendor: HP dmi.board.version: 87.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613359/+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 1613359] Re: Xrandr gamma and brightness problem on 4.4.0-34 kernel
apport information ** Tags added: apport-collected xenial ** Description changed: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: robby 3691 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a + InstallationDate: Installed on 2016-07-01 (44 days ago) + InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + MachineType: HP HP ENVY Notebook + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-34-generic N/A + linux-backports-modules-4.4.0-34-generic N/A + linux-firmware1.157.3 + Tags: xenial + Uname: Linux 4.4.0-34-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/19/2016 + dmi.bios.vendor: Insyde + dmi.bios.version: F.32 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: 80E5 + dmi.board.vendor: HP + dmi.board.version: 87.57 + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnInsyde:bvrF.32:bd01/19/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80E5:rvr87.57:cvnHP:ct10:cvrChassisVersion: + dmi.product.name: HP ENVY Notebook + dmi.product.version: Type1ProductConfigId + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1613359/+attachment/4721365/+files/AlsaInfo.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/1613359 Title: Xrandr gamma and brightness problem on 4.4.0-34 kernel Status in linux package in Ubuntu: Incomplete Bug description: Situation Xubuntu 16.04 after the automatic update of the kernel, from 4.4.0-31 to 4.4.0-34. If I give a xrandr command that does not change the resolution or the output monitor, but only the gamma and brightness xrandr --output eDP1 --mode 1368x768 --rate 60 --gamma 1.25: 1.25: 1.25 --brightness 1:25 In eDP1 already 60 hertz and already 1368x768 Nothing is happening. The change in brightness occurs if you change the resolution: xrandr --output eDP1 --mode 1024x768 The screen is considerably brighter. After the command: xrandr --output eDP1 --mode 1024x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Nothing happens, but the change of brightness occurs to the resolution change. for example xrandr --output eDP1 --mode 1360x768 or xrandr --output eDP1 --mode 1360x768 --rate 60 --gamma 1: 1: 1 --brightness 1 Loading the previous kernel 4.4.0-31 the brightness and gamma change immediately. Is my first report, I hope it is clear. Thank you. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robby 3691 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=40af1a02-6e4a-4c2a-8ffb-4f2cf48bc95a InstallationDate: Installed on 2016-07-01 (44 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP ENVY Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=b3c35f62-3284-4572-a839-8926f4cae17d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
[Kernel-packages] [Bug 1583437] Re: Directly after boot there is no network
I have the same problem. I added "systemctl restart NetworkManager.service¨ to "/etc/rc.local" to solv it temporarily -- 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/1583437 Title: Directly after boot there is no network Status in linux package in Ubuntu: Confirmed Bug description: When doing a cold boot from a full power off, or a soft reboot, after gnome loads, I have no Internet connections. This happens without fail after every cold boot and intermittently after a soft reboot. It has occurred since ubuntu desktop 14.04 all the way up to 16.04. I only use kernels that is provided by unbuntu and only when the system tells me there is an update to them. I have no custom drivers installed, all drivers are from the kernel minus the nivida drivers, but it does this even when i dont use the proprietary drivers from nvidia. The fix for the problem is to soft reboot multiple times until it corrects itself. I have done many search's and tried several options, none have corrected the problem. Im currently using ubuntu desktop 16.04 (gnome) below is a copy of dmesg from one of the network failed boots. Let me know if there is anything else I can provide to assist. http://pastebin.com/84mqSUuW ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sysx 1813 F pulseaudio /dev/snd/controlC0: sysx 1813 F pulseaudio CurrentDesktop: GNOME Date: Thu May 19 00:09:47 2016 HibernationDevice: RESUME=UUID=73058683-1e8a-4e97-9b1b-e34e7f4a5511 MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=ede95eeb-fd81-4883-bfe1-6d2cb0567e66 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1583437/+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 1577284] Re: Black screen after wake
Hi, I actually started testing the latest v4.6 for another issue I was having with screen flickers after trying to test 4.5.2. So far it seems to be working, but I will have to continue testing since this issue happens daily but at random times. -- 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/1577284 Title: Black screen after wake Status in linux package in Ubuntu: Incomplete Bug description: I got this issue once a day or so when I close the lid of my laptop to suspend, and when I try to wake it up I get a blank screen where often the only thing that shows up is the mouse cursor. I can't use the mouse nor keyboard, and I can't access virtual consoles (ctrl+alt+f1). I'm forced to shutdown the machine by pressing and holding the machine's power button. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rburgosnavas 2004 F pulseaudio CurrentDesktop: KDE Date: Sun May 1 22:28:15 2016 HibernationDevice: RESUME=UUID=b53db5b2-4b01-4892-b626-fe449689bdbc InstallationDate: Installed on 2016-02-26 (65 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20ENCTO1WW ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=889bb61f-7562-4d1e-9461-4f73a6ab4192 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-29 (2 days ago) dmi.bios.date: 12/31/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET41W(1.15):bd12/31/2015:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577284/+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 1552304] Re: screen flicker on Dell XPS 13 9350 after kernel upgrade
*** This bug is a duplicate of bug 1554613 *** https://bugs.launchpad.net/bugs/1554613 I just installed v4.6-rc6-wily and the flickering seems to have stopped, but I believe it is still too early to tell. For the record, after I upgraded to 16.04 I was having suspend issues where closing the laptop lid did not suspend the machine. I tried a number of kernels until I settled with 4.5.2, but that's when the flickering problem started. It sort of felt like it only happened when the laptop was running on batteries and discharging, and running on power and charging with a battery percentage of less than 100%. -- 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/1552304 Title: screen flicker on Dell XPS 13 9350 after kernel upgrade Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to this version of the linux kernel (Linux xps 4.4.0-9-generic #24-Ubuntu SMP Mon Feb 29 19:33:19 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux) and the screen now flickers ramdomly. flicker every few seconds for a fraction of the second. Not related to application install or system load. WORKAROUND: I discovered that if you have tlp installed and running, you will get screen flicker. If you disable it, or remove it, the flicker goes away. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-9-generic 4.4.0-9.24 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anmar 1810 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 2 11:11:37 2016 HibernationDevice: RESUME=UUID=94adb22b-7cde-416d-a17f-c3e5d40718da InstallationDate: Installed on 2016-03-02 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160301) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic.efi.signed root=UUID=9945d9bf-9e44-4308-a4ec-c1f92f9b330c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-9-generic N/A linux-backports-modules-4.4.0-9-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd12/18/2015:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552304/+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 1577284] [NEW] Black screen after wake
Public bug reported: I got this issue once a day or so when I close the lid of my laptop to suspend, and when I try to wake it up I get a blank screen where often the only thing that shows up is the mouse cursor. I can't use the mouse nor keyboard, and I can't access virtual consoles (ctrl+alt+f1). I'm forced to shutdown the machine by pressing and holding the machine's power button. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rburgosnavas 2004 F pulseaudio CurrentDesktop: KDE Date: Sun May 1 22:28:15 2016 HibernationDevice: RESUME=UUID=b53db5b2-4b01-4892-b626-fe449689bdbc InstallationDate: Installed on 2016-02-26 (65 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20ENCTO1WW ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=889bb61f-7562-4d1e-9461-4f73a6ab4192 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-29 (2 days ago) dmi.bios.date: 12/31/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET41W(1.15):bd12/31/2015:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "wakeup" https://bugs.launchpad.net/bugs/1577284/+attachment/4653204/+files/wakeup -- 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/1577284 Title: Black screen after wake Status in linux package in Ubuntu: New Bug description: I got this issue once a day or so when I close the lid of my laptop to suspend, and when I try to wake it up I get a blank screen where often the only thing that shows up is the mouse cursor. I can't use the mouse nor keyboard, and I can't access virtual consoles (ctrl+alt+f1). I'm forced to shutdown the machine by pressing and holding the machine's power button. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rburgosnavas 2004 F pulseaudio CurrentDesktop: KDE Date: Sun May 1 22:28:15 2016 HibernationDevice: RESUME=UUID=b53db5b2-4b01-4892-b626-fe449689bdbc InstallationDate: Installed on 2016-02-26 (65 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20ENCTO1WW ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=889bb61f-7562-4d1e-9461-4f73a6ab4192 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-29 (2 days ago) dmi.bios.date: 12/31/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET41W(1.15):bd12/31/2015:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577284/+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 1569831] Re: Laptop does not resume after suspend (blackscreen).
I am having the same problem running kernel 4.4.8 and Linux Mint 17.3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1569831 Title: Laptop does not resume after suspend (blackscreen). Status in bcmwl package in Ubuntu: Incomplete Bug description: I have installed OS multiple times. I have to manually install the BCM driver. After installing the bcmwl-kernal-source the laptop will suspend, but not resume after. If I disable the external driver, the suspend resume works again. I have tried with a variety of different configs. Network card is BCM4352 [14e4-43b1](rev03) When I try to resume the laptop turns on, but screen never turns on. I've tried to the shortuts to turn the screen back on. I'm using NVIDIA drivers, but even if I use the generic drivers the laptop will not resume. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 13 11:05:08 2016 InstallationDate: Installed on 2016-03-05 (39 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1569831/+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 1449910] Re: System hangs apparently randomly when disconnecting iScsi volumes
After another month of testing, the mainline kernel never failed. So, is this bug fixed in some release version of 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/1449910 Title: System hangs apparently randomly when disconnecting iScsi volumes Status in linux package in Ubuntu: Triaged Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace: /0x70 Apr 21 23:02:56 server-name kernel: [654840.108419] [] reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108426] [] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108437] [] do_journal_begin_r+0xe1/0x3e0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108443] [] ? __enqueue_entity+0x78/0x80 Apr 21 23:02:56 server-name kernel: [654840.108454] [] journal_begin+0x8a/0x160 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108464] [] reiserfs_release_dquot+0x4c/0xd0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108470] [] ? __percpu_counter_add+0x51/0x70 Apr 21 23:02:56 server-name kernel: [654840.108476] [] dqput+0x9d/0x200 Apr 21 23:02:56 server-name kernel: [654840.108480] [] __dquot_drop+0x5d/0x70 Apr 21 23:02:56 server-name kernel: [654840.108485] [] dquot_drop+0x2d/0x40 Apr 21 23:02:56 server-name kernel: [654840.108494] [] reiserfs_evic t_inode+0xa0/0x180 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108501] [] ? inode_wait_for_writeback+0x2e/0x40 Apr 21 23:02:56 server-name kernel: [654840.108507] [] evict+0xb4/0x180 Apr 21 23:02:56 server-name kernel: [654840.108511] [] dispose_list+0x39/0x50 Apr 21 23:02:56 server-name kernel: [654840.108515] [] prune_icache_sb+0x47/0x60 Apr 21 23:02:56 server-name kernel: [654840.108520] [] super_cache_scan+0x105/0x170 Apr 21 23:02:56 server-name kernel: [654840.108526] [] shrink_slab_node+0x138/0x290 Apr 21 23:02:56 server-name kernel: [654840.108532] [] ? css_next_descendant_pre+0x3b/0x40 Apr 21 23:02:56 server-name kernel: [654840.108536] [] shrink_slab+0x8b/0x160 Apr 21 23:02:56 server-name kernel: [654840.108540] [] balance_pgdat+0x3f2/0x620 Apr 21 23:02:56 server-name kernel: [654840.108544] [] kswapd+0x15b/0x3f0 Apr 21 23:02:56 server-name kernel: [654840.108549] [] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108552] [] ? balance_pgdat+0x620/0x620 Apr 21 23:02:56 server-name kernel: [654840.108558] [] kthread+0xd2/0xf0 Apr 21 23:02:56 server-name kernel: [654840.108562] [] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108567] [] ret_from_fork+0x7c/0xb0 Apr 21 23:02:56 server-name kernel: [654840.108571] [] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108595] INFO: task kworker/1:1:25606 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108709] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108809] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 21 23:02:56 server-name kernel: [654840.108923] kworker/1:1 D 88007fc530c0 0 25606 2 0x Apr 21 23:02:56 server-name kernel:
[Kernel-packages] [Bug 1506626] [NEW] package dkms 2.2.0.3-1.1ubuntu5.14.04.5 failed to install/upgrade: package dkms is already installed and configured
Public bug reported: I haven't details: warning arise but I wasn't checking computer activities ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dkms 2.2.0.3-1.1ubuntu5.14.04.5 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 ApportVersion: 2.14.1-0ubuntu3.15 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: i386 Date: Thu Oct 15 21:25:23 2015 DuplicateSignature: package:dkms:2.2.0.3-1.1ubuntu5.14.04.5:package dkms is already installed and configured ErrorMessage: package dkms is already installed and configured InstallationDate: Installed on 2013-09-15 (760 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: dkms Title: package dkms 2.2.0.3-1.1ubuntu5.14.04.5 failed to install/upgrade: package dkms is already installed and configured UpgradeStatus: Upgraded to trusty on 2014-08-29 (412 days ago) ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 need-duplicate-check trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1506626 Title: package dkms 2.2.0.3-1.1ubuntu5.14.04.5 failed to install/upgrade: package dkms is already installed and configured Status in dkms package in Ubuntu: New Bug description: I haven't details: warning arise but I wasn't checking computer activities ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dkms 2.2.0.3-1.1ubuntu5.14.04.5 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic i686 ApportVersion: 2.14.1-0ubuntu3.15 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: i386 Date: Thu Oct 15 21:25:23 2015 DuplicateSignature: package:dkms:2.2.0.3-1.1ubuntu5.14.04.5:package dkms is already installed and configured ErrorMessage: package dkms is already installed and configured InstallationDate: Installed on 2013-09-15 (760 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: dkms Title: package dkms 2.2.0.3-1.1ubuntu5.14.04.5 failed to install/upgrade: package dkms is already installed and configured UpgradeStatus: Upgraded to trusty on 2014-08-29 (412 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1506626/+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 1449910] Re: System hangs apparently randomly when disconnecting iScsi volumes
After the installation of the mainline kernel on the remaining machine, the problem hasn't appeared anymore for more than one month, then unfortunately I couldn't test this anymore, because of other unrelated hardware problems. I plan to start again in the next days, still I think the problem is solved with the mainline kernel. So, what can we do now? Will the new release kernel be free of 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/1449910 Title: System hangs apparently randomly when disconnecting iScsi volumes Status in linux package in Ubuntu: Triaged Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace: /0x70 Apr 21 23:02:56 server-name kernel: [654840.108419] [] reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108426] [] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108437] [] do_journal_begin_r+0xe1/0x3e0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108443] [] ? __enqueue_entity+0x78/0x80 Apr 21 23:02:56 server-name kernel: [654840.108454] [] journal_begin+0x8a/0x160 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108464] [] reiserfs_release_dquot+0x4c/0xd0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108470] [] ? __percpu_counter_add+0x51/0x70 Apr 21 23:02:56 server-name kernel: [654840.108476] [] dqput+0x9d/0x200 Apr 21 23:02:56 server-name kernel: [654840.108480] [] __dquot_drop+0x5d/0x70 Apr 21 23:02:56 server-name kernel: [654840.108485] [] dquot_drop+0x2d/0x40 Apr 21 23:02:56 server-name kernel: [654840.108494] [] reiserfs_evic t_inode+0xa0/0x180 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108501] [] ? inode_wait_for_writeback+0x2e/0x40 Apr 21 23:02:56 server-name kernel: [654840.108507] [] evict+0xb4/0x180 Apr 21 23:02:56 server-name kernel: [654840.108511] [] dispose_list+0x39/0x50 Apr 21 23:02:56 server-name kernel: [654840.108515] [] prune_icache_sb+0x47/0x60 Apr 21 23:02:56 server-name kernel: [654840.108520] [] super_cache_scan+0x105/0x170 Apr 21 23:02:56 server-name kernel: [654840.108526] [] shrink_slab_node+0x138/0x290 Apr 21 23:02:56 server-name kernel: [654840.108532] [] ? css_next_descendant_pre+0x3b/0x40 Apr 21 23:02:56 server-name kernel: [654840.108536] [] shrink_slab+0x8b/0x160 Apr 21 23:02:56 server-name kernel: [654840.108540] [] balance_pgdat+0x3f2/0x620 Apr 21 23:02:56 server-name kernel: [654840.108544] [] kswapd+0x15b/0x3f0 Apr 21 23:02:56 server-name kernel: [654840.108549] [] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108552] [] ? balance_pgdat+0x620/0x620 Apr 21 23:02:56 server-name kernel: [654840.108558] [] kthread+0xd2/0xf0 Apr 21 23:02:56 server-name kernel: [654840.108562] [] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108567] [] ret_from_fork+0x7c/0xb0 Apr 21 23:02:56 server-name kernel: [654840.108571] [] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108595] INFO: task kworker/1:1:25606 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108709] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56
[Kernel-packages] [Bug 1449910] Re: System hangs apparently randomly when disconnecting iScsi volumes
2 nights ago something happened. I have a 5th server which doesn't use LVM snapshots, but still it's backed up every night. I didn't install the mainline kernel on this machine, because we thought the problem was due to snapshots. And it crashed two nights ago, in the same way the other machines crashed, without using snapshots. It crashed after finishing the backup. I think the problem lies in the disconnection of the iscsi volume on which the machines do the backup. On the first reboot, I had the following in the kernel log: [ 209.312097] [ cut here ] [ 209.312106] WARNING: CPU: 0 PID: 1808 at /build/buildd/linux-3.13.0/drivers/pci/pci.c:1444 pci_disable_device+0x9c/0xb0() [ 209.312108] ipmi_si :01:04.6: disabling already-disabled device [ 209.312110] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sit tunnel4 ip_tunnel dm_crypt gpio_ich coretemp kvm joydev serio_raw hpilo lpc_ich ipmi_si(-) i3200_edac shpchp edac_core mac_hid lp parport reiserfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic radeon i2c_algo_bit ttm drm_kms_helper psmouse drm pata_acpi tg3 usbhid hid ptp pps_core [ 209.312151] CPU: 0 PID: 1808 Comm: modprobe Not tainted 3.13.0-53-generic #89-Ubuntu [ 209.312153] Hardware name: HP ProLiant DL320 G5p, BIOS W05 04/03/2008 [ 209.312154] 0009 88007abb3d40 81722e1e 88007abb3d88 [ 209.312158] 88007abb3d78 810677fd 88007c311000 88007c2c5580 [ 209.312161] 88007c311000 7f459c5473f0 7ffd2b319338 88007abb3dd8 [ 209.312164] Call Trace: [ 209.312170] [81722e1e] dump_stack+0x45/0x56 [ 209.312175] [810677fd] warn_slowpath_common+0x7d/0xa0 [ 209.312177] [8106786c] warn_slowpath_fmt+0x4c/0x50 [ 209.312182] [811a259d] ? kfree+0xfd/0x140 [ 209.312186] [813a9c7c] pci_disable_device+0x9c/0xb0 [ 209.312192] [a0398059] ipmi_pci_remove+0x29/0x30 [ipmi_si] [ 209.312195] [813ac68b] pci_device_remove+0x3b/0xb0 [ 209.312200] [81498c3f] __device_release_driver+0x7f/0xf0 [ 209.312203] [81499608] driver_detach+0xb8/0xc0 [ 209.312207] [81498875] bus_remove_driver+0x55/0xd0 [ 209.312210] [81499c7c] driver_unregister+0x2c/0x50 [ 209.312213] [813ab179] pci_unregister_driver+0x29/0x90 [ 209.312218] [a03984c4] cleanup_ipmi_si+0xd4/0xf0 [ipmi_si] [ 209.31] [810e05d2] SyS_delete_module+0x162/0x200 [ 209.312227] [81013ed7] ? do_notify_resume+0x97/0xb0 [ 209.312231] [8173391d] system_call_fastpath+0x1a/0x1f [ 209.312233] ---[ end trace f6143eeb3c0e8dba ]--- I don't know if this is related, anyway it happened only on this particular reboot. I now installed the mainline kernel also on this machine. I changed the title of this bug to reflect the additional information I got. ** Summary changed: - System hangs apparently randomly when creating LVM snapshots + System hangs apparently randomly when disconnecting iScsi volumes -- 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/1449910 Title: System hangs apparently randomly when disconnecting iScsi volumes Status in linux package in Ubuntu: Triaged Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8
[Kernel-packages] [Bug 1449910] Re: System hangs apparently randomly when creating LVM snapshots
So, all the systems have been up and running for 35 nights as of now. The upstream kernel is doing good. What can we do from here? Thank you for your 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/1449910 Title: System hangs apparently randomly when creating LVM snapshots Status in linux package in Ubuntu: Confirmed Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace: /0x70 Apr 21 23:02:56 server-name kernel: [654840.108419] [c0707aad] reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108426] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108437] [c0709271] do_journal_begin_r+0xe1/0x3e0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108443] [810a5fa8] ? __enqueue_entity+0x78/0x80 Apr 21 23:02:56 server-name kernel: [654840.108454] [c070967a] journal_begin+0x8a/0x160 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108464] [c06f67fc] reiserfs_release_dquot+0x4c/0xd0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108470] [813ab4f1] ? __percpu_counter_add+0x51/0x70 Apr 21 23:02:56 server-name kernel: [654840.108476] [8123003d] dqput+0x9d/0x200 Apr 21 23:02:56 server-name kernel: [654840.108480] [8123166d] __dquot_drop+0x5d/0x70 Apr 21 23:02:56 server-name kernel: [654840.108485] [812316ad] dquot_drop+0x2d/0x40 Apr 21 23:02:56 server-name kernel: [654840.108494] [c06ec7a0] reiserfs_evic t_inode+0xa0/0x180 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108501] [811ff7de] ? inode_wait_for_writeback+0x2e/0x40 Apr 21 23:02:56 server-name kernel: [654840.108507] [811eef34] evict+0xb4/0x180 Apr 21 23:02:56 server-name kernel: [654840.108511] [811ef039] dispose_list+0x39/0x50 Apr 21 23:02:56 server-name kernel: [654840.108515] [811eff47] prune_icache_sb+0x47/0x60 Apr 21 23:02:56 server-name kernel: [654840.108520] [811d78f5] super_cache_scan+0x105/0x170 Apr 21 23:02:56 server-name kernel: [654840.108526] [81171b78] shrink_slab_node+0x138/0x290 Apr 21 23:02:56 server-name kernel: [654840.108532] [810f8ccb] ? css_next_descendant_pre+0x3b/0x40 Apr 21 23:02:56 server-name kernel: [654840.108536] [8117367b] shrink_slab+0x8b/0x160 Apr 21 23:02:56 server-name kernel: [654840.108540] [811770e2] balance_pgdat+0x3f2/0x620 Apr 21 23:02:56 server-name kernel: [654840.108544] [8117746b] kswapd+0x15b/0x3f0 Apr 21 23:02:56 server-name kernel: [654840.108549] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108552] [81177310] ? balance_pgdat+0x620/0x620 Apr 21 23:02:56 server-name kernel: [654840.108558] [81091332] kthread+0xd2/0xf0 Apr 21 23:02:56 server-name kernel: [654840.108562] [81091260] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108567] [8176c9bc] ret_from_fork+0x7c/0xb0 Apr 21 23:02:56 server-name kernel: [654840.108571] [81091260] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108595] INFO: task
[Kernel-packages] [Bug 1449910] Re: System hangs apparently randomly when creating LVM snapshots
OK, I've just installed the latest mainline kernel (4.1.0-040100rc1-generic), let's see if this happens again. By the way, this last kernel doesn't contain the firmware file bnx2-mips-06-6.2.3.fw, which I needed on 2 of the 4 servers I'm testing this on. It's a network driver, I fixed the problem copying manually the requested file from /lib/firmware/3.13.0-51-generic/ , so from the old kernel set of firmware files. I'll report back here if something happens, or if the problem seems fixed. I'll test this every night for at least one month, as I said in the previous comment. -- 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/1449910 Title: System hangs apparently randomly when creating LVM snapshots Status in linux package in Ubuntu: Confirmed Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace: /0x70 Apr 21 23:02:56 server-name kernel: [654840.108419] [c0707aad] reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108426] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108437] [c0709271] do_journal_begin_r+0xe1/0x3e0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108443] [810a5fa8] ? __enqueue_entity+0x78/0x80 Apr 21 23:02:56 server-name kernel: [654840.108454] [c070967a] journal_begin+0x8a/0x160 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108464] [c06f67fc] reiserfs_release_dquot+0x4c/0xd0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108470] [813ab4f1] ? __percpu_counter_add+0x51/0x70 Apr 21 23:02:56 server-name kernel: [654840.108476] [8123003d] dqput+0x9d/0x200 Apr 21 23:02:56 server-name kernel: [654840.108480] [8123166d] __dquot_drop+0x5d/0x70 Apr 21 23:02:56 server-name kernel: [654840.108485] [812316ad] dquot_drop+0x2d/0x40 Apr 21 23:02:56 server-name kernel: [654840.108494] [c06ec7a0] reiserfs_evic t_inode+0xa0/0x180 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108501] [811ff7de] ? inode_wait_for_writeback+0x2e/0x40 Apr 21 23:02:56 server-name kernel: [654840.108507] [811eef34] evict+0xb4/0x180 Apr 21 23:02:56 server-name kernel: [654840.108511] [811ef039] dispose_list+0x39/0x50 Apr 21 23:02:56 server-name kernel: [654840.108515] [811eff47] prune_icache_sb+0x47/0x60 Apr 21 23:02:56 server-name kernel: [654840.108520] [811d78f5] super_cache_scan+0x105/0x170 Apr 21 23:02:56 server-name kernel: [654840.108526] [81171b78] shrink_slab_node+0x138/0x290 Apr 21 23:02:56 server-name kernel: [654840.108532] [810f8ccb] ? css_next_descendant_pre+0x3b/0x40 Apr 21 23:02:56 server-name kernel: [654840.108536] [8117367b] shrink_slab+0x8b/0x160 Apr 21 23:02:56 server-name kernel: [654840.108540] [811770e2] balance_pgdat+0x3f2/0x620 Apr 21 23:02:56 server-name kernel: [654840.108544] [8117746b] kswapd+0x15b/0x3f0 Apr 21 23:02:56 server-name kernel: [654840.108549] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108552] [81177310] ? balance_pgdat+0x620/0x620 Apr 21 23:02:56 server-name kernel: [654840.108558]
[Kernel-packages] [Bug 1449910] Re: System hangs apparently randomly when creating LVM snapshots
Thank you Joseph for your answer. I guess I should test the 4.1 kernel which can be found at the link you provided. I'll do this next Monday, just keep in mind that, being the problem apparently random, one should wait some time before drawing conclusions (I'll say one month without hangs, doing snapshots every night, to be sufficiently sure). -- 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/1449910 Title: System hangs apparently randomly when creating LVM snapshots Status in linux package in Ubuntu: Confirmed Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace: /0x70 Apr 21 23:02:56 server-name kernel: [654840.108419] [c0707aad] reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108426] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108437] [c0709271] do_journal_begin_r+0xe1/0x3e0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108443] [810a5fa8] ? __enqueue_entity+0x78/0x80 Apr 21 23:02:56 server-name kernel: [654840.108454] [c070967a] journal_begin+0x8a/0x160 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108464] [c06f67fc] reiserfs_release_dquot+0x4c/0xd0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108470] [813ab4f1] ? __percpu_counter_add+0x51/0x70 Apr 21 23:02:56 server-name kernel: [654840.108476] [8123003d] dqput+0x9d/0x200 Apr 21 23:02:56 server-name kernel: [654840.108480] [8123166d] __dquot_drop+0x5d/0x70 Apr 21 23:02:56 server-name kernel: [654840.108485] [812316ad] dquot_drop+0x2d/0x40 Apr 21 23:02:56 server-name kernel: [654840.108494] [c06ec7a0] reiserfs_evic t_inode+0xa0/0x180 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108501] [811ff7de] ? inode_wait_for_writeback+0x2e/0x40 Apr 21 23:02:56 server-name kernel: [654840.108507] [811eef34] evict+0xb4/0x180 Apr 21 23:02:56 server-name kernel: [654840.108511] [811ef039] dispose_list+0x39/0x50 Apr 21 23:02:56 server-name kernel: [654840.108515] [811eff47] prune_icache_sb+0x47/0x60 Apr 21 23:02:56 server-name kernel: [654840.108520] [811d78f5] super_cache_scan+0x105/0x170 Apr 21 23:02:56 server-name kernel: [654840.108526] [81171b78] shrink_slab_node+0x138/0x290 Apr 21 23:02:56 server-name kernel: [654840.108532] [810f8ccb] ? css_next_descendant_pre+0x3b/0x40 Apr 21 23:02:56 server-name kernel: [654840.108536] [8117367b] shrink_slab+0x8b/0x160 Apr 21 23:02:56 server-name kernel: [654840.108540] [811770e2] balance_pgdat+0x3f2/0x620 Apr 21 23:02:56 server-name kernel: [654840.108544] [8117746b] kswapd+0x15b/0x3f0 Apr 21 23:02:56 server-name kernel: [654840.108549] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108552] [81177310] ? balance_pgdat+0x620/0x620 Apr 21 23:02:56 server-name kernel: [654840.108558] [81091332] kthread+0xd2/0xf0 Apr 21 23:02:56 server-name kernel: [654840.108562] [81091260] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108567] [8176c9bc]
[Kernel-packages] [Bug 1449910] [NEW] System hangs apparently randomly when creating LVM snapshots
Public bug reported: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace: /0x70 Apr 21 23:02:56 server-name kernel: [654840.108419] [c0707aad] reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108426] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108437] [c0709271] do_journal_begin_r+0xe1/0x3e0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108443] [810a5fa8] ? __enqueue_entity+0x78/0x80 Apr 21 23:02:56 server-name kernel: [654840.108454] [c070967a] journal_begin+0x8a/0x160 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108464] [c06f67fc] reiserfs_release_dquot+0x4c/0xd0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108470] [813ab4f1] ? __percpu_counter_add+0x51/0x70 Apr 21 23:02:56 server-name kernel: [654840.108476] [8123003d] dqput+0x9d/0x200 Apr 21 23:02:56 server-name kernel: [654840.108480] [8123166d] __dquot_drop+0x5d/0x70 Apr 21 23:02:56 server-name kernel: [654840.108485] [812316ad] dquot_drop+0x2d/0x40 Apr 21 23:02:56 server-name kernel: [654840.108494] [c06ec7a0] reiserfs_evic t_inode+0xa0/0x180 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108501] [811ff7de] ? inode_wait_for_writeback+0x2e/0x40 Apr 21 23:02:56 server-name kernel: [654840.108507] [811eef34] evict+0xb4/0x180 Apr 21 23:02:56 server-name kernel: [654840.108511] [811ef039] dispose_list+0x39/0x50 Apr 21 23:02:56 server-name kernel: [654840.108515] [811eff47] prune_icache_sb+0x47/0x60 Apr 21 23:02:56 server-name kernel: [654840.108520] [811d78f5] super_cache_scan+0x105/0x170 Apr 21 23:02:56 server-name kernel: [654840.108526] [81171b78] shrink_slab_node+0x138/0x290 Apr 21 23:02:56 server-name kernel: [654840.108532] [810f8ccb] ? css_next_descendant_pre+0x3b/0x40 Apr 21 23:02:56 server-name kernel: [654840.108536] [8117367b] shrink_slab+0x8b/0x160 Apr 21 23:02:56 server-name kernel: [654840.108540] [811770e2] balance_pgdat+0x3f2/0x620 Apr 21 23:02:56 server-name kernel: [654840.108544] [8117746b] kswapd+0x15b/0x3f0 Apr 21 23:02:56 server-name kernel: [654840.108549] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108552] [81177310] ? balance_pgdat+0x620/0x620 Apr 21 23:02:56 server-name kernel: [654840.108558] [81091332] kthread+0xd2/0xf0 Apr 21 23:02:56 server-name kernel: [654840.108562] [81091260] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108567] [8176c9bc] ret_from_fork+0x7c/0xb0 Apr 21 23:02:56 server-name kernel: [654840.108571] [81091260] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108595] INFO: task kworker/1:1:25606 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108709] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108809] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 21 23:02:56 server-name kernel: [654840.108923] kworker/1:1 D 88007fc530c0 0 25606 2 0x Apr 21 23:02:56 server-name kernel: [654840.108936] Workqueue: events_long flush_old_commits [reiserfs] Apr 21
[Kernel-packages] [Bug 1449910] Re: System hangs apparently randomly when creating LVM snapshots
I installed this apport thing, but it doesn't seem to work, it tries to open the webiste via links, but the website thinks I'm a bot. ** 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/1449910 Title: System hangs apparently randomly when creating LVM snapshots Status in linux package in Ubuntu: Confirmed Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace: /0x70 Apr 21 23:02:56 server-name kernel: [654840.108419] [c0707aad] reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108426] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108437] [c0709271] do_journal_begin_r+0xe1/0x3e0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108443] [810a5fa8] ? __enqueue_entity+0x78/0x80 Apr 21 23:02:56 server-name kernel: [654840.108454] [c070967a] journal_begin+0x8a/0x160 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108464] [c06f67fc] reiserfs_release_dquot+0x4c/0xd0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108470] [813ab4f1] ? __percpu_counter_add+0x51/0x70 Apr 21 23:02:56 server-name kernel: [654840.108476] [8123003d] dqput+0x9d/0x200 Apr 21 23:02:56 server-name kernel: [654840.108480] [8123166d] __dquot_drop+0x5d/0x70 Apr 21 23:02:56 server-name kernel: [654840.108485] [812316ad] dquot_drop+0x2d/0x40 Apr 21 23:02:56 server-name kernel: [654840.108494] [c06ec7a0] reiserfs_evic t_inode+0xa0/0x180 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108501] [811ff7de] ? inode_wait_for_writeback+0x2e/0x40 Apr 21 23:02:56 server-name kernel: [654840.108507] [811eef34] evict+0xb4/0x180 Apr 21 23:02:56 server-name kernel: [654840.108511] [811ef039] dispose_list+0x39/0x50 Apr 21 23:02:56 server-name kernel: [654840.108515] [811eff47] prune_icache_sb+0x47/0x60 Apr 21 23:02:56 server-name kernel: [654840.108520] [811d78f5] super_cache_scan+0x105/0x170 Apr 21 23:02:56 server-name kernel: [654840.108526] [81171b78] shrink_slab_node+0x138/0x290 Apr 21 23:02:56 server-name kernel: [654840.108532] [810f8ccb] ? css_next_descendant_pre+0x3b/0x40 Apr 21 23:02:56 server-name kernel: [654840.108536] [8117367b] shrink_slab+0x8b/0x160 Apr 21 23:02:56 server-name kernel: [654840.108540] [811770e2] balance_pgdat+0x3f2/0x620 Apr 21 23:02:56 server-name kernel: [654840.108544] [8117746b] kswapd+0x15b/0x3f0 Apr 21 23:02:56 server-name kernel: [654840.108549] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108552] [81177310] ? balance_pgdat+0x620/0x620 Apr 21 23:02:56 server-name kernel: [654840.108558] [81091332] kthread+0xd2/0xf0 Apr 21 23:02:56 server-name kernel: [654840.108562] [81091260] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108567] [8176c9bc] ret_from_fork+0x7c/0xb0 Apr 21 23:02:56 server-name kernel: [654840.108571] [81091260] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56
[Kernel-packages] [Bug 1449910] Re: System hangs apparently randomly when creating LVM snapshots
The automated script did tags: added: utopic , but it's actually a Trusty (LTS) bug. ** Tags removed: utopic ** Tags added: trusty -- 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/1449910 Title: System hangs apparently randomly when creating LVM snapshots Status in linux package in Ubuntu: Confirmed Bug description: We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use LVM snapshots to do backups during the night. Randomly (witha rate of 1 event every 10-12 days) the LVM snapshot creation runs in some problem. The server hangs and it must be rebooted hardly. No shell, no even any screen output, just a black screen, no ping, nothing. And Magic SysRq key doesn't help. No logs are written either (I also tried redirect logs to another machine, just in case). This happens with different hardware, and different backup software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something logged: Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 blocked for more than 120 seconds. Apr 21 23:02:56 server-name kernel: [654840.108145] Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu Apr 21 23:02:56 server-name kernel: [654840.108245] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 88007fc130c0 050 2 0x Apr 21 23:02:56 server-name kernel: [654840.108367] 880077bcf998 0046 880077bd 880077bcffd8 Apr 21 23:02:56 server-name kernel: [654840.108372] 000130c0 000130c0 88007bdef010 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108377] c90010d3c0d8 c90010d3c000 Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace: /0x70 Apr 21 23:02:56 server-name kernel: [654840.108419] [c0707aad] reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108426] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108437] [c0709271] do_journal_begin_r+0xe1/0x3e0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108443] [810a5fa8] ? __enqueue_entity+0x78/0x80 Apr 21 23:02:56 server-name kernel: [654840.108454] [c070967a] journal_begin+0x8a/0x160 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108464] [c06f67fc] reiserfs_release_dquot+0x4c/0xd0 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108470] [813ab4f1] ? __percpu_counter_add+0x51/0x70 Apr 21 23:02:56 server-name kernel: [654840.108476] [8123003d] dqput+0x9d/0x200 Apr 21 23:02:56 server-name kernel: [654840.108480] [8123166d] __dquot_drop+0x5d/0x70 Apr 21 23:02:56 server-name kernel: [654840.108485] [812316ad] dquot_drop+0x2d/0x40 Apr 21 23:02:56 server-name kernel: [654840.108494] [c06ec7a0] reiserfs_evic t_inode+0xa0/0x180 [reiserfs] Apr 21 23:02:56 server-name kernel: [654840.108501] [811ff7de] ? inode_wait_for_writeback+0x2e/0x40 Apr 21 23:02:56 server-name kernel: [654840.108507] [811eef34] evict+0xb4/0x180 Apr 21 23:02:56 server-name kernel: [654840.108511] [811ef039] dispose_list+0x39/0x50 Apr 21 23:02:56 server-name kernel: [654840.108515] [811eff47] prune_icache_sb+0x47/0x60 Apr 21 23:02:56 server-name kernel: [654840.108520] [811d78f5] super_cache_scan+0x105/0x170 Apr 21 23:02:56 server-name kernel: [654840.108526] [81171b78] shrink_slab_node+0x138/0x290 Apr 21 23:02:56 server-name kernel: [654840.108532] [810f8ccb] ? css_next_descendant_pre+0x3b/0x40 Apr 21 23:02:56 server-name kernel: [654840.108536] [8117367b] shrink_slab+0x8b/0x160 Apr 21 23:02:56 server-name kernel: [654840.108540] [811770e2] balance_pgdat+0x3f2/0x620 Apr 21 23:02:56 server-name kernel: [654840.108544] [8117746b] kswapd+0x15b/0x3f0 Apr 21 23:02:56 server-name kernel: [654840.108549] [810b4d70] ? prepare_to_wait_event+0x100/0x100 Apr 21 23:02:56 server-name kernel: [654840.108552] [81177310] ? balance_pgdat+0x620/0x620 Apr 21 23:02:56 server-name kernel: [654840.108558] [81091332] kthread+0xd2/0xf0 Apr 21 23:02:56 server-name kernel: [654840.108562] [81091260] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108567] [8176c9bc] ret_from_fork+0x7c/0xb0 Apr 21 23:02:56 server-name kernel: [654840.108571] [81091260] ? kthread_create_on_node+0x1c0/0x1c0 Apr 21 23:02:56 server-name kernel: [654840.108595] INFO: task kworker/1:1:25606
[Kernel-packages] [Bug 1397487] [NEW] Philips GoGear Vibe MP3 Player is not properly recoginized on Ubuntu 14.04
Public bug reported: I have a Philips GoGear Vibe Mp3 player that worked fine on Ubuntu 12.04. Recently, I installed Ubuntu 14.04 LTS (64 bits) on the same machine and my deviced didn't work properly anymore: when I open it, I see an icon named 'Internal Storage' inside. If I right-click outside the icon (but inside the GoGear Vibe folder) to see GoGear properties, Nautilus says it only has 1 element, with a size of 0 bytes. Also, if I ask for GoGear's permissions, Nautilus says they couldn't be determined. If I open 'Internal Storage', nautilus only shows an empty folder (no files inside, see the attached screenshots for details). On Ubuntu 12.04, I opened my device and all it's content was shown directly without any problem. Also, there wasn't any 'Internal Storage' icon. This is probably related to bug 1214765, and question 228269. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rfg1905 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 28 23:24:24 2014 HibernationDevice: RESUME=UUID=291b3f8a-4d92-4e7f-8286-775f98ccf271 InstallationDate: Installed on 2014-11-22 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0bbaee34-88b2-46e9-9fd2-9d7efa698bdc ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: K8M800-M2 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/18/2005:svn:pn:pvr:rvn:rnK8M800-M2:rvr:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: This is what I see inside my device https://bugs.launchpad.net/bugs/1397487/+attachment/4270496/+files/Screenshots.zip -- 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/1397487 Title: Philips GoGear Vibe MP3 Player is not properly recoginized on Ubuntu 14.04 Status in linux package in Ubuntu: New Bug description: I have a Philips GoGear Vibe Mp3 player that worked fine on Ubuntu 12.04. Recently, I installed Ubuntu 14.04 LTS (64 bits) on the same machine and my deviced didn't work properly anymore: when I open it, I see an icon named 'Internal Storage' inside. If I right-click outside the icon (but inside the GoGear Vibe folder) to see GoGear properties, Nautilus says it only has 1 element, with a size of 0 bytes. Also, if I ask for GoGear's permissions, Nautilus says they couldn't be determined. If I open 'Internal Storage', nautilus only shows an empty folder (no files inside, see the attached screenshots for details). On Ubuntu 12.04, I opened my device and all it's content was shown directly without any problem. Also, there wasn't any 'Internal Storage' icon. This is probably related to bug 1214765, and question 228269. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rfg1905 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 28 23:24:24 2014 HibernationDevice: RESUME=UUID=291b3f8a-4d92-4e7f-8286-775f98ccf271 InstallationDate: Installed on 2014-11-22 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0bbaee34-88b2-46e9-9fd2-9d7efa698bdc ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 RfKill: SourcePackage: linux
[Kernel-packages] [Bug 1214765] Re: Philips GoGear Vibe MP3 Player is not properly recoginized
Cristopher: I can confirm that this issue is currently affecting Trusty (64 bits) too. I'm going to open a new report by this weekend. Should I suscribe you to it when I get this done? Regards. -- 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/1214765 Title: Philips GoGear Vibe MP3 Player is not properly recoginized Status in “linux” package in Ubuntu: Incomplete Bug description: just did an update to 13.04 from version 12 and now my Philips GoGear Vibe MP3 Player is not properly recoginized. In version 12 the folders were visible and music could be copied to the player. In 13.04 when I select the GoGear, the only icon is for Internal Storage - with no folders listed. Is there a driver that is needed so the player can be recognized? thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214765/+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 1388430] Re: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied
1) As Nvidia Customer Care team suggested, I manually installed driver 304.123 (instructions at http://askubuntu.com/questions/451221/ubuntu-14-04-install-nvidia-driver, answer nº 23). 2) Running gksudo nvidia-settings enabled me to change my screen resolution, but my nettings were not being preserved after rebooting my machine. 3) I went to System Settings -- Monitors, and changed my screen resolution from there. My new settings were preserved after rebooting this time. It seems driver 304.123 solves the issue, but it's not available for Trusty yet. -- 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/1388430 Title: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied Status in “nvidia-settings” package in Ubuntu: New Bug description: 1. I recently did a fresh install of Ubuntu 14.04 (64 bits) on my machine, which has an Nvidia GeForce 6200 graphics card. When I try to change the screen resolution, changes are not being applied and nvidia-settings is closing when I press the 'Apply' button. 2. I run nvidia-settings in a terminal, and I got the following error message after pressing the 'Apply' button (see the attached file): The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 528 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 3. This seems to be a duplicate of Bug #1273652. 4. I contacted Nvidia custom care support, and they suggested me to try the latest driver version (304.123). Unfortunately, when I checked nvidia-graphics-drivers-304 at Launchpad, I found it's only available for Utopic, Precise, and Vivid (indeed, it doesn't appear in my Additional Drivers wizard). If you help me to install version 304.123 on my system, I'll give Nvidia Linux maintainers all the feedback they are requesting from me, and I'll be in a better condition to colaborate with you to solve this issue (installation instructions provided by Nvidia website are hard for me to follow). Feel free to e-mail me if you think I can help in any way. 5. You can find additional information about similar issues in the following links: http://askubuntu.com/questions/412181/nvidia-settings-received-an-x-window-system-error-error-was-badvalue-intege http://askubuntu.com/questions/452030/nvidia-settings-does-not-work-since-upgrade-to-14-04 http://www.nvnews.net/vbulletin/showthread.php?t=76073 6. System settings: OS version: Ubuntu 14.04 LTS (64 bits) Nvidia driver version: 304.117 nvidia-settings version: 331.20-0ubuntu8 P.S: apparently, this is not the first time a bug like this affects nvidia-settings on Ubuntu. If you read the comments at the second and third links in point 5 (above), there is people who solved the issue after they installed an nvidia-settings package which version number matches the driver one (or vice-versa). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 1 14:33:26 2014 InstallationDate: Installed on 2014-11-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1388430/+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 1273652] Re: apply of multi-monitor setting results in crash
Regarding the issue I commented above, I could fix it by manually installing driver 304.123. Please, refer to Bug #1388430 for details. I hope this can help you. -- 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/1273652 Title: apply of multi-monitor setting results in crash Status in “nvidia-settings” package in Ubuntu: Confirmed Bug description: After the recent update of nvidia settings, I am not able to apply new monitor setting via nvidia settings anymore. After configuration of X Server Display Configuration hit hit the apply button and then the program simply quit. A workaround is to click on Save to X Configuration file and restart the computer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings 331.20-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Jan 28 12:51:27 2014 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1273652/+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 1388430] Re: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied
1) I have installed driver 304.123 from Nvidia following the instructions provided at http://askubuntu.com/questions/451221/ubuntu-14-04-install-nvidia-driver 2) I got the following error message: The distribution-provided pre-install script failed! Continue installation anyway? I chose 'Yes' and the installation process continued and finished, apparently, successfully. 3) I sent the log file (same file I attach here) to Nvidia Customer Care support team, and I'm waiting for their feedback now. 4) I was able to change my screen resolution (run gksudo nvidia- settings, because changing my screen resolution requires root privileges), so 304.123 seems to solve the issue. If Nvidia technicians confirm that everything is ok, I think 304.123 should be made available for Trusty, so any user who need it could install it with the 'Additional Drivers' wizard. It's all for now. ** Attachment added: nvidia-installer.log https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1388430/+attachment/4252313/+files/nvidia-installer.log -- 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/1388430 Title: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied Status in “nvidia-settings” package in Ubuntu: New Bug description: 1. I recently did a fresh install of Ubuntu 14.04 (64 bits) on my machine, which has an Nvidia GeForce 6200 graphics card. When I try to change the screen resolution, changes are not being applied and nvidia-settings is closing when I press the 'Apply' button. 2. I run nvidia-settings in a terminal, and I got the following error message after pressing the 'Apply' button (see the attached file): The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 528 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 3. This seems to be a duplicate of Bug #1273652. 4. I contacted Nvidia custom care support, and they suggested me to try the latest driver version (304.123). Unfortunately, when I checked nvidia-graphics-drivers-304 at Launchpad, I found it's only available for Utopic, Precise, and Vivid (indeed, it doesn't appear in my Additional Drivers wizard). If you help me to install version 304.123 on my system, I'll give Nvidia Linux maintainers all the feedback they are requesting from me, and I'll be in a better condition to colaborate with you to solve this issue (installation instructions provided by Nvidia website are hard for me to follow). Feel free to e-mail me if you think I can help in any way. 5. You can find additional information about similar issues in the following links: http://askubuntu.com/questions/412181/nvidia-settings-received-an-x-window-system-error-error-was-badvalue-intege http://askubuntu.com/questions/452030/nvidia-settings-does-not-work-since-upgrade-to-14-04 http://www.nvnews.net/vbulletin/showthread.php?t=76073 6. System settings: OS version: Ubuntu 14.04 LTS (64 bits) Nvidia driver version: 304.117 nvidia-settings version: 331.20-0ubuntu8 P.S: apparently, this is not the first time a bug like this affects nvidia-settings on Ubuntu. If you read the comments at the second and third links in point 5 (above), there is people who solved the issue after they installed an nvidia-settings package which version number matches the driver one (or vice-versa). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 1 14:33:26 2014 InstallationDate: Installed on 2014-11-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1388430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1273652] Re: apply of multi-monitor setting results in crash
I have a similar issue with Ubuntu 14.04 (64 bits) and Nvidia driver 304.117 (please, refer to Bug #1388430 for details). I spoke to Nvidia Customer Care support and they are requesting me to install another driver version (304.123) from Nvidia web site. Unfortunately, installation instructions are hard for me to follow, so I would need some help in order to test this driver version and give the technicians a proper feedback. If someone thinks that this could help to solve the issue, please feel free to e-mail me and I'll do my best to colaborate. -- 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/1273652 Title: apply of multi-monitor setting results in crash Status in “nvidia-settings” package in Ubuntu: Confirmed Bug description: After the recent update of nvidia settings, I am not able to apply new monitor setting via nvidia settings anymore. After configuration of X Server Display Configuration hit hit the apply button and then the program simply quit. A workaround is to click on Save to X Configuration file and restart the computer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings 331.20-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Jan 28 12:51:27 2014 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1273652/+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 1388430] [NEW] nvidia-settings closes when pressing 'Apply' button, but changes aren't applied
Public bug reported: 1. I recently did a fresh install of Ubuntu 14.04 (64 bits) on my machine, which has an Nvidia GeForce 6200 graphics card. When I try to change the screen resolution, changes are not being applied and nvidia-settings is closing when I press the 'Apply' button. 2. I run nvidia-settings in a terminal, and I got the following error message after pressing the 'Apply' button (see the attached file): The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 528 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 3. This seems to be a duplicate of Bug #1273652. 4. I contacted Nvidia custom care support, and they suggested me to try the latest driver version (304.123). Unfortunately, when I checked nvidia-graphics-drivers-304 at Launchpad, I found it's only available for Utopic, Precise, and Vivid (indeed, it doesn't appear in my Additional Drivers wizard). If you help me to install version 304.123 on my system, I'll give Nvidia Linux maintainers all the feedback they are requesting from me, and I'll be in a better condition to colaborate with you to solve this issue (installation instructions provided by Nvidia website are hard for me to follow). Feel free to e-mail me if you think I can help in any way. 5. You can find additional information about similar issues in the following links: http://askubuntu.com/questions/412181/nvidia-settings-received-an-x-window-system-error-error-was-badvalue-intege http://askubuntu.com/questions/452030/nvidia-settings-does-not-work-since-upgrade-to-14-04 http://www.nvnews.net/vbulletin/showthread.php?t=76073 6. System settings: OS version: Ubuntu 14.04 LTS (64 bits) Nvidia driver version: 304.117 nvidia-settings version: 331.20-0ubuntu8 P.S: apparently, this is not the first time a bug like this affects nvidia-settings on Ubuntu. If you read the comments at the second and third links in point 5 (above), there is people who solved the issue after they installed an nvidia-settings package which version number matches the driver one (or vice-versa). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 1 14:33:26 2014 InstallationDate: Installed on 2014-11-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Terminal Output from nvidia-settings https://bugs.launchpad.net/bugs/1388430/+attachment/4250915/+files/Terminal%20Output%20from%20nvidia-settings -- 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/1388430 Title: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied Status in “nvidia-settings” package in Ubuntu: New Bug description: 1. I recently did a fresh install of Ubuntu 14.04 (64 bits) on my machine, which has an Nvidia GeForce 6200 graphics card. When I try to change the screen resolution, changes are not being applied and nvidia-settings is closing when I press the 'Apply' button. 2. I run nvidia-settings in a terminal, and I got the following error message after pressing the 'Apply' button (see the attached file): The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 528 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 3. This seems to be a duplicate of Bug #1273652. 4. I contacted Nvidia custom care support, and they suggested me to try the latest driver version (304.123).
[Kernel-packages] [Bug 1354046] Re: no 3d acceleration with error [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
This also happens in utopic. I also tried using the Kernel 3.17.1 from the kernel-ppa and the latest xserver from xorg-edgers ppa and I can see the same problem. I using an Dell XPS 12 (Ultrabook) -- 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/1354046 Title: no 3d acceleration with error [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Status in “linux” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: Description: 3D games, video (especially flash) makes computer unresponsive. The problem has been present since upgrade to Utopic, but have recently become worse, maybe because of error message [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up which appears in all terminals. How to reproduce: Start a 1080p video. e.g. Note that the video is not run from an encrypted folder. Or watch a video on youtube. Reproducable for new users as well, so not related to /home/$USER What happens: Usage on all four CPUs on my DELL XPS 13 DEVELOPER EDITION will be between 30% and 100%. What I expected: Expected same 3D performance as on Thrusty. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 BootLog: Scanning for Btrfs filesystems * Setting up X socket directories... [240G [234G[ OK ] CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Aug 7 17:03:51 2014 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.12, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.12, 3.13.0-27-generic, x86_64: installed vboxhost, 4.3.12, 3.13.0-29-generic, x86_64: installed vboxhost, 4.3.12, 3.16.0-5-generic, x86_64: installed vboxhost, 4.3.12, 3.16.0-6-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2013-08-27 (345 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=221de9c1-f10a-4be4-9273-5c12864c8680 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1b1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 10.0.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Aug 7 16:54:59 2014 xserver.configfile: default xserver.errors: intel: Failed to load module dri3 (module does not exist, 0) intel: Failed to load module present (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN
[Kernel-packages] [Bug 1326725] Re: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic
@salisbury, I tested 3.13.11-03131104-generic, last available from http://kernel.ubuntu.com/~kernel-ppa/mainline/ for trusty. It works: Jun 21 14:55:29 bebop kernel: [ 365.133571] usb 3-3: USB disconnect, device number 3 Jun 21 14:55:34 bebop kernel: [ 370.168060] usb 3-3: new full-speed USB device number 4 using xhci_hcd Jun 21 14:55:34 bebop kernel: [ 370.202363] usb 3-3: New USB device found, idVendor=054c, idProduct=0268 Jun 21 14:55:34 bebop kernel: [ 370.202366] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 21 14:55:34 bebop kernel: [ 370.202367] usb 3-3: Product: PLAYSTATION(R)3 Controller Jun 21 14:55:34 bebop kernel: [ 370.202369] usb 3-3: Manufacturer: Sony Jun 21 14:55:34 bebop kernel: [ 370.214032] sony 0003:054C:0268.0003: Fixing up Sony Sixaxis report descriptor Jun 21 14:55:34 bebop kernel: [ 370.239601] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input18 Jun 21 14:55:34 bebop kernel: [ 370.239804] sony 0003:054C:0268.0003: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:14.0-3/input0 Jun 21 14:55:34 bebop mtp-probe: checking bus 3, device 4: /sys/devices/pci:00/:00:14.0/usb3/3-3 Jun 21 14:55:34 bebop mtp-probe: bus: 3, device: 4 was not an MTP device -- 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/1326725 Title: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic Status in “linux” package in Ubuntu: Confirmed Bug description: After applying upgrades to my 14.04 installations and rebooting, suddenly the sony sixaxis usb joystick/controller input device which I use a lot will now no longer appear as a joystick device. It happens on at least two machines with the newest 14.04 updates as of a couple of days ago. See below for kernel messages. I believe the actual kernel error message for this bug is: Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode After looking at the kernel sources I believe this is a problem with the hid_sony kernel module. The changelog for linux-image- extra-3.13.0-27-generic, which contains this module, has many hid related changes. The same bug/regression, it appears, was reported on askubuntu.com some days ago, see this link: http://askubuntu.com/questions/474199/my-ps3-controller-stopped- working-2-days-ago Version information: $ lsb_release -d Description:Ubuntu 14.04 LTS $ uname -a Linux valley 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # dpkg -S /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko linux-image-extra-3.13.0-27-generic: /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko dmesg: Jun 5 11:36:50 machine kernel: [47062.360175] usb 2-1.1.3.1: new full-speed USB device number 19 using ehci-pci Jun 5 11:36:51 machine kernel: [47062.486789] usb 2-1.1.3.1: New USB device found, idVendor=054c, idProduct=0268 Jun 5 11:36:51 machine kernel: [47062.486797] usb 2-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 5 11:36:51 machine kernel: [47062.486802] usb 2-1.1.3.1: Product: PLAYSTATION(R)3 Controller Jun 5 11:36:51 machine kernel: [47062.486806] usb 2-1.1.3.1: Manufacturer: Sony Jun 5 11:36:51 machine kernel: [47062.498624] sony 0003:054C:0268.000E: Fixing up Sony Sixaxis report descriptor Jun 5 11:36:51 machine kernel: [47062.524383] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1/2-1.1.3.1:1.0/input/input22 Jun 5 11:36:51 machine kernel: [47062.524563] sony 0003:054C:0268.000E: input,hiddev0,hidraw4: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:1d.0-1.1.3.1/input0 Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode Jun 5 11:36:51 machine kernel: [47062.556374] sony: probe of 0003:054C:0268.000E failed with error -38 Jun 5 11:36:51 machine mtp-probe: checking bus 2, device 19: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1 Jun 5 11:36:51 machine mtp-probe: bus: 2, device: 19 was not an MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326725/+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 1326725] Re: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic
Kernel Version: 3.13.0-29.53 Jun 15 01:48:48 bebop kernel: [644505.504141] usb 3-3: new full-speed USB device number 11 using xhci_hcd Jun 15 01:48:48 bebop kernel: [644505.538650] usb 3-3: New USB device found, idVendor=054c, idProduct=0268 Jun 15 01:48:48 bebop kernel: [644505.538660] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 15 01:48:48 bebop kernel: [644505.538665] usb 3-3: Product: PLAYSTATION(R)3 Controller Jun 15 01:48:48 bebop kernel: [644505.538669] usb 3-3: Manufacturer: Sony Jun 15 01:48:48 bebop kernel: [644505.550542] sony 0003:054C:0268.0008: Fixing up Sony Sixaxis report descriptor Jun 15 01:48:48 bebop kernel: [644505.576407] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input25 Jun 15 01:48:48 bebop kernel: [644505.576940] sony 0003:054C:0268.0008: input,hiddev0,hidraw1: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:14.0-3/input0 Jun 15 01:48:48 bebop kernel: [644505.576945] sony 0003:054C:0268.0008: can't set operational mode Jun 15 01:48:48 bebop kernel: [644505.592553] sony: probe of 0003:054C:0268.0008 failed with error -38 Bug still present ** 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/1326725 Title: PS3 Sixaxis controller/joystick usb stopped working, regression in linux-image-extra-3.13.0-27-generic Status in “linux” package in Ubuntu: Confirmed Bug description: After applying upgrades to my 14.04 installations and rebooting, suddenly the sony sixaxis usb joystick/controller input device which I use a lot will now no longer appear as a joystick device. It happens on at least two machines with the newest 14.04 updates as of a couple of days ago. See below for kernel messages. I believe the actual kernel error message for this bug is: Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode After looking at the kernel sources I believe this is a problem with the hid_sony kernel module. The changelog for linux-image- extra-3.13.0-27-generic, which contains this module, has many hid related changes. The same bug/regression, it appears, was reported on askubuntu.com some days ago, see this link: http://askubuntu.com/questions/474199/my-ps3-controller-stopped- working-2-days-ago Version information: $ lsb_release -d Description:Ubuntu 14.04 LTS $ uname -a Linux valley 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # dpkg -S /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko linux-image-extra-3.13.0-27-generic: /lib/modules/3.13.0-27-generic/kernel/drivers/hid/hid-sony.ko dmesg: Jun 5 11:36:50 machine kernel: [47062.360175] usb 2-1.1.3.1: new full-speed USB device number 19 using ehci-pci Jun 5 11:36:51 machine kernel: [47062.486789] usb 2-1.1.3.1: New USB device found, idVendor=054c, idProduct=0268 Jun 5 11:36:51 machine kernel: [47062.486797] usb 2-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 5 11:36:51 machine kernel: [47062.486802] usb 2-1.1.3.1: Product: PLAYSTATION(R)3 Controller Jun 5 11:36:51 machine kernel: [47062.486806] usb 2-1.1.3.1: Manufacturer: Sony Jun 5 11:36:51 machine kernel: [47062.498624] sony 0003:054C:0268.000E: Fixing up Sony Sixaxis report descriptor Jun 5 11:36:51 machine kernel: [47062.524383] input: Sony PLAYSTATION(R)3 Controller as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1/2-1.1.3.1:1.0/input/input22 Jun 5 11:36:51 machine kernel: [47062.524563] sony 0003:054C:0268.000E: input,hiddev0,hidraw4: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-:00:1d.0-1.1.3.1/input0 Jun 5 11:36:51 machine kernel: [47062.524566] sony 0003:054C:0268.000E: can't set operational mode Jun 5 11:36:51 machine kernel: [47062.556374] sony: probe of 0003:054C:0268.000E failed with error -38 Jun 5 11:36:51 machine mtp-probe: checking bus 2, device 19: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3.1 Jun 5 11:36:51 machine mtp-probe: bus: 2, device: 19 was not an MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 291760] Re: network-manager roams to (none) ((none)) - background scanning
noo not agai! On Oct 17, 2013 12:26 PM, Max Waterman davidmaxwaterman+launch...@fastmail.co.uk wrote: Just getting this starting today (or perhaps yesterday), after a bunch of s/w was upgrade (so that's what I blame). Quite irritating since my other devices on the network are fine - it's just Ubuntu. - 13.04 in this case. Perhaps I'll try 13.10, since it was released today (iinm), but something makes me thing this problem will be in that too :/ Using a Lenovo X1 Carbon - not sure what h/w it has, but it seems to be unrelated to specific h/w. -- You received this bug notification because you are subscribed to a duplicate bug report (278800). https://bugs.launchpad.net/bugs/291760 Title: network-manager roams to (none) ((none)) - background scanning To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/291760/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/291760 Title: network-manager roams to (none) ((none)) - background scanning Status in The Linux Kernel: Fix Released Status in NetworkManager: Incomplete Status in “linux” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Fix Released Status in “linux” source package in Maverick: Invalid Status in “network-manager” source package in Maverick: Fix Released Bug description: Binary package hint: network-manager The network manager roames to a none bssid and back, this happens in more or less two minute intervalls. During this time i get: Oct 31 03:44:17 Oct 31 03:44:17 coppelius named[5281]: too many timeouts resolving 'linuxhaters.blogspot.com/A' (in '.'?): disabling EDNS Oct 31 03:44:17 coppelius named[5281]: too many timeouts resolving 'www.pro-linux.de/A' (in '.'?): disabling EDNS Oct 31 03:44:17 coppelius named[5281]: too many timeouts resolving 'linuxhaters.blogspot.com/A' (in '.'?): disabling EDNS coppelius named[5281]: too many timeouts resolving 'linuxhaters.blogspot.com/A' (in '.'?): disabling EDNS Oct 31 03:44:17 coppelius named[5281]: too many timeouts resolving 'www.pro-linux.de/A' (in '.'?): disabling EDNS Oct 31 03:44:17 coppelius named[5281]: too many timeouts resolving 'linuxhaters.blogspot.com/A' (in '.'?): disabling EDNS /var/log/daemon.log Oct 31 20:29:41 coppelius NetworkManager: debug [1225481381.966597] periodic_update(): Roamed from BSSID 00:04:0E:73:0F:34 (Silkes Parfum) to (none) ((none)) Oct 31 20:29:47 coppelius NetworkManager: debug [1225481387.969699] periodic_update(): Roamed from BSSID (none) ((none)) to 00:04:0E:73:0F:34 (Silkes Parfum) Oct 31 20:31:42 coppelius NetworkManager: debug [1225481502.049585] periodic_update(): Roamed from BSSID 00:04:0E:73:0F:34 (Silkes Parfum) to (none) ((none)) Oct 31 20:31:48 coppelius NetworkManager: debug [1225481508.054596] periodic_update(): Roamed from BSSID (none) ((none)) to 00:04:0E:73:0F:34 (Silkes Parfum) Oct 31 20:33:42 coppelius NetworkManager: debug [1225481622.130595] periodic_update(): Roamed from BSSID 00:04:0E:73:0F:34 (Silkes Parfum) to (none) ((none)) Oct 31 20:33:48 coppelius NetworkManager: debug [1225481628.134635] periodic_update(): Roamed from BSSID (none) ((none)) to 00:04:0E:73:0F:34 (Silkes Parfum) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/291760/+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 1173761] Re: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported
Hi Felix, how did you get the 43b1 to work with the kernel 3.10? Could you bring some additional information? -- 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/1173761 Title: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported Status in “linux” package in Ubuntu: Confirmed Bug description: Both during and after installation, 13.04 doesn't support the Broadcom-based 802.11ac wifi chipsets. lspci reports it as Network controller: Broadcom Corporation Device 43b1 (rev 03). Would love to see this worker as it's being a bit of a show stopper for me. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc8-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 --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atrauzzi 2141 F pulseaudio /dev/snd/controlC0: atrauzzi 2141 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 176.287266] atl1c :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=90e84f80-b3fc-4480-b4cd-21d15e3abc6d InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=b0911040-5a49-4581-9a7a-bac9d830a0ba ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 StagingDrivers: r8712u Tags: raring staging Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX 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.:bvrG75VX.203:bd10/23/2012:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX 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/1173761/+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 1172852] Re: USB keyboard and mouse don't work
I confirm the bug and in my installation this happen today with an update that have installed 3.8.0-29.42 By the way, also the login screen resolution was not high as expected. Before this update my kernel in 13.04 was 3.8.0-25.37 Booting with grub menu and going to advanced, I've booted into that previous image 3.8.0-25 and mouse and keyboard got back to be operational. (My mainboard is an Asus P8P67, with the corresponding intel chipset) Synaptic lists as available the linux-image-extra-3.8.0-29-generic and it could be possible to apply it as Nikolai does suggest, which right now I'm processing... Yes, the linux-image-extra-3.8.0-29-generic works Bad joke, though Regards to all of you and thank you to Nikolai for his hints Cor -- 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/1172852 Title: USB keyboard and mouse don't work Status in “linux” package in Ubuntu: Incomplete Bug description: I am installing Ubuntu 13.04 from a live USB key. I downloaded the stable amd64 iso of Ubuntu 13.04 after it was released today. It runs beautifully from a live USB key. However, after installing the OS to my hard drive and rebooting, the keyboard and mouse both fail to work. They are standard USB input devices (US layout) which have worked for years on other versions of Red Hat and Ubuntu. They work fine with the live USB version of the OS. I can't even log into the computer to collect bug data. I've tried reinstalling several times, changing the install options. Installing fresh on this computer, keeping only my old /home partition, and disallowing the installation of third-party software still produces the error. The same system has run several previous versions of Ubuntu without problems. Thanks for your help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172852/+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 644898] Re: required kernel toshiba support not enabled
@Alejandro Salas No, just replace with: PDE_DATA(inode) -- 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/644898 Title: required kernel toshiba support not enabled Status in “linux” package in Ubuntu: Confirmed Status in “toshset” package in Ubuntu: Confirmed Status in “toshset” package in Debian: New Bug description: Binary package hint: toshset The kernel support required to use these utilities isn't installed - I can't use extra buttons, hotkeys, or change screen brightness. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: toshset 1.75-2 ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 CheckboxSubmission: 8b15f4fca5292e90a3327d5e528e925e CheckboxSystem: 988b7c9be54a1e2525cae7d97805a134 Date: Wed Sep 22 01:13:08 2010 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: toshset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/644898/+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 644898] Re: required kernel toshiba support not enabled
For kernel=3.10: replace PDE()-data with PDE_DATA() -- 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/644898 Title: required kernel toshiba support not enabled Status in “linux” package in Ubuntu: Confirmed Status in “toshset” package in Ubuntu: Confirmed Status in “toshset” package in Debian: New Bug description: Binary package hint: toshset The kernel support required to use these utilities isn't installed - I can't use extra buttons, hotkeys, or change screen brightness. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: toshset 1.75-2 ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 CheckboxSubmission: 8b15f4fca5292e90a3327d5e528e925e CheckboxSystem: 988b7c9be54a1e2525cae7d97805a134 Date: Wed Sep 22 01:13:08 2010 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: toshset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/644898/+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
