[Kernel-packages] [Bug 1930775] [NEW] package nvidia-dkms-465 465.27-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error ex
Public bug reported: I tried to install the graphics drivers for an nvidia graphics card on a 2021 ASUS scar 15 laptop with an amd ryzen processor and a 3070 graphics card. I tried to do it multiple times in multiple different ways; through the additional software GUI and through the terminal. Neither worked and threw up the prior mentioned error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-465 465.27-0ubuntu0.20.04.2 Uname: Linux 5.11.0-051100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 3 16:11:50 2021 ErrorMessage: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-06-01 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-465 Title: package nvidia-dkms-465 465.27-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-465 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-465 in Ubuntu. https://bugs.launchpad.net/bugs/1930775 Title: package nvidia-dkms-465 465.27-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: I tried to install the graphics drivers for an nvidia graphics card on a 2021 ASUS scar 15 laptop with an amd ryzen processor and a 3070 graphics card. I tried to do it multiple times in multiple different ways; through the additional software GUI and through the terminal. Neither worked and threw up the prior mentioned error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-465 465.27-0ubuntu0.20.04.2 Uname: Linux 5.11.0-051100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 3 16:11:50 2021 ErrorMessage: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-06-01 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-465 Title: package nvidia-dkms-465 465.27-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-465 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1930775/+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 1883681] Re: System freezes on specific kernel
Hi, Is an update for the patch "net: handle no dst on skb in icmp6_send" now available in the release of the kernel version "4.4.0.186.192". linux-generic/xenial-updates,xenial-security 4.4.0.186.192 amd64 [upgradable from: 4.4.0.179.187] Br, Anand -- 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/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Confirmed Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+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 1883681] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384338/+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/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+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 1883681] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384341/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+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 1883681] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384342/+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/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+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 1883681] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384345/+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/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+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 1883681] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384343/+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/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+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 1883681] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384340/+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/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+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 1883681] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384339/+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/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+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 1883681] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384344/+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/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+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 1883681] Re: System freezes on specific kernel
apport information ** Tags added: apport-collected xenial ** Description changed: - The servers will be running fine for some time and suddenly will freeze. - It won't even respond to ping requests. We have to reboot the servers - again to bring it back online but it won't be stable and will not - respond again. + The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 15 17:52 seq + crw-rw 1 root audio 116, 33 Jun 15 17:52 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.23 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c + IwConfig: + lono wireless extensions. + + ens160no wireless extensions. + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: VMware, Inc. VMware Virtual Platform + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen + PATH=(custom, no user) + LANG=en_US + SHELL=/bin/bash + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M + ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-184-generic N/A + linux-backports-modules-4.4.0-184-generic N/A + linux-firmware 1.157.23 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.4.0-184-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/17/2015 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: 6.00 + dmi.board.name: 440BX Desktop Reference Platform + dmi.board.vendor: Intel Corporation + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: + dmi.product.name: VMware Virtual Platform + dmi.product.version: None + dmi.sys.vendor: VMware, Inc. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384337/+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/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi
[Kernel-packages] [Bug 1875515] Re: Kubuntu 20.04 hangs during shutdown
Issue resolved after I updated the bios version. Please close the defect. -- 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/1875515 Title: Kubuntu 20.04 hangs during shutdown Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Kubuntu 20.04 hangs during shutdown. I see some RIP errors.If I wait for 15-20 mins, the machine usually shuts down (but not always). 1. Attached debug information (collected using ubuntu-bug) 2. 1.zip 1.zip has 3 files - Screenshot showing the error, two journalctl logs corresponding to two shutdown crashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anand 1101 F pulseaudio /dev/snd/controlC0: anand 1101 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 20:13:29 2020 InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B360 AORUS GAMING 3 WIFI ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=4ab861b2-c752-444f-930d-5327aa5963d6 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360 AORUS GAMING 3 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360AORUSGAMING3WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360AORUSGAMING3WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360 AORUS GAMING 3 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875515/+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 1875515] Re: Kubuntu 20.04 hangs during shutdown
** Description changed: Fresh install of Kubuntu 20.04 hangs during shutdown. I see some RIP - errors.If I wait for 15-20 mins, the machine usually shutsdown. + errors.If I wait for 15-20 mins, the machine usually shuts down (but not + always). 1. Attached debug information (collected using ubuntu-bug) 2. 1.zip 1.zip has 3 files - Screenshot showing the error, two journalctl logs corresponding to two shutdown crashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: anand 1101 F pulseaudio - /dev/snd/controlC0: anand 1101 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: anand 1101 F pulseaudio + /dev/snd/controlC0: anand 1101 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 20:13:29 2020 InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: - eno1 no wireless extensions. - - lono wireless extensions. + eno1 no wireless extensions. + + lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B360 AORUS GAMING 3 WIFI ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=4ab861b2-c752-444f-930d-5327aa5963d6 ro RelatedPackageVersions: - linux-restricted-modules-5.4.0-26-generic N/A - linux-backports-modules-5.4.0-26-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-26-generic N/A + linux-backports-modules-5.4.0-26-generic N/A + linux-firmware1.187 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360 AORUS GAMING 3 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360AORUSGAMING3WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360AORUSGAMING3WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360 AORUS GAMING 3 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- 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/1875515 Title: Kubuntu 20.04 hangs during shutdown Status in linux package in Ubuntu: Confirmed Bug description: Fresh install of Kubuntu 20.04 hangs during shutdown. I see some RIP errors.If I wait for 15-20 mins, the machine usually shuts down (but not always). 1. Attached debug information (collected using ubuntu-bug) 2. 1.zip 1.zip has 3 files - Screenshot showing the error, two journalctl logs corresponding to two shutdown crashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anand 1101 F pulseaudio /dev/snd/controlC0: anand 1101 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 20:13:29 2020 InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B360 AORUS GAMING 3 WIFI ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=4ab861b2-c752-444f-930d-5327aa5963d6 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360 AORUS GAMING 3 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset
[Kernel-packages] [Bug 1875515] [NEW] Kubuntu 20.04 hangs during shutdown
Public bug reported: Fresh install of Kubuntu 20.04 hangs during shutdown. I see some RIP errors.If I wait for 15-20 mins, the machine usually shutsdown. 1. Attached debug information (collected using ubuntu-bug) 2. 1.zip 1.zip has 3 files - Screenshot showing the error, two journalctl logs corresponding to two shutdown crashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anand 1101 F pulseaudio /dev/snd/controlC0: anand 1101 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 20:13:29 2020 InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B360 AORUS GAMING 3 WIFI ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=4ab861b2-c752-444f-930d-5327aa5963d6 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360 AORUS GAMING 3 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360AORUSGAMING3WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360AORUSGAMING3WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360 AORUS GAMING 3 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "1.zip" https://bugs.launchpad.net/bugs/1875515/+attachment/5362105/+files/1.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/1875515 Title: Kubuntu 20.04 hangs during shutdown Status in linux package in Ubuntu: New Bug description: Fresh install of Kubuntu 20.04 hangs during shutdown. I see some RIP errors.If I wait for 15-20 mins, the machine usually shutsdown. 1. Attached debug information (collected using ubuntu-bug) 2. 1.zip 1.zip has 3 files - Screenshot showing the error, two journalctl logs corresponding to two shutdown crashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anand 1101 F pulseaudio /dev/snd/controlC0: anand 1101 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 20:13:29 2020 InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B360 AORUS GAMING 3 WIFI ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=4ab861b2-c752-444f-930d-5327aa5963d6 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360 AORUS GAMING 3 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360AORUSGAMING3WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360AORUSGAMING3WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.
[Kernel-packages] [Bug 1838751] Re: Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas adapters(SAS3.5 onwards)
** Tags removed: verification-needed-bionic verification-needed-disco
** Tags added: verification-done-disco
--
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/1838751
Title:
Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas
adapters(SAS3.5 onwards)
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-osp1 package in Ubuntu:
New
Status in linux source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Committed
Status in linux-oem-osp1 source package in Disco:
Fix Released
Bug description:
[Impact]
Latest megaraid_sas and mpt3sas adapters which support Resizable BAR
with 1 MB BAR size fails to initialize during system resume from S3
sleep.
As per our findings the issue is caused by the below upstream commit:
d3252ace0bc652a1a24446b6a549f969bf99 ("PCI: Restore resized BAR
state on resume")
We see that the same commit has been ported to UBUNTU18.X - PCI:
Restore resized BAR state on resume (bsc#1105355).
the fix has been submitted to upstream
https://patchwork.kernel.org/patch/11058689/
please include this patch in the upcoming releases.please let me know
if additional information required.
https://bugzilla.kernel.org/show_bug.cgi?id=203939
[Test case]
See that suspend/resume works correctly after applying the patch
[Regression potential]
slim, itself fixes a regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838751/+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 1838751] Re: Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas adapters(SAS3.5 onwards)
Hi @kleber-souza,
I have validated the bug fix (Suspend to RAM(S3) does not wake up for
latest megaraid and mpt3sas adapters(SAS3.5 onwards)).
The Disco linux kernel (disco/linux: 5.0.0-31.33 -proposed) fixes the
issue.
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838751
Title:
Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas
adapters(SAS3.5 onwards)
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-osp1 package in Ubuntu:
New
Status in linux source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Committed
Status in linux-oem-osp1 source package in Disco:
Fix Released
Bug description:
[Impact]
Latest megaraid_sas and mpt3sas adapters which support Resizable BAR
with 1 MB BAR size fails to initialize during system resume from S3
sleep.
As per our findings the issue is caused by the below upstream commit:
d3252ace0bc652a1a24446b6a549f969bf99 ("PCI: Restore resized BAR
state on resume")
We see that the same commit has been ported to UBUNTU18.X - PCI:
Restore resized BAR state on resume (bsc#1105355).
the fix has been submitted to upstream
https://patchwork.kernel.org/patch/11058689/
please include this patch in the upcoming releases.please let me know
if additional information required.
https://bugzilla.kernel.org/show_bug.cgi?id=203939
[Test case]
See that suspend/resume works correctly after applying the patch
[Regression potential]
slim, itself fixes a regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838751/+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 1838751] Re: Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas adapters(SAS3.5 onwards)
Hi @kleber-souza,
Referring to the previous conversations by janitor,(where he said this
bug was fixed in the package linux - 5.3.0-12.13 Launchpad Janitor
(janitor) wrote on 2019-09-27:) i did follow the instructions provided
(https://wiki.ubuntu.com/Testing/EnableProposed) to upgrade to the
kernel version 5.3.0-12-generic and tested.
But i see issue still exists. I doubt if i have picked the proper kernel
where the fix is provided.
@Could you please check whether the Disco linux kernel currently in -proposed
fixes this issue?
Would you please provide the link/attach the kernel image, i will test it again
quickly and get back to you at the earliest.
Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838751
Title:
Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas
adapters(SAS3.5 onwards)
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-osp1 package in Ubuntu:
New
Status in linux source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Committed
Status in linux-oem-osp1 source package in Disco:
New
Bug description:
[Impact]
Latest megaraid_sas and mpt3sas adapters which support Resizable BAR
with 1 MB BAR size fails to initialize during system resume from S3
sleep.
As per our findings the issue is caused by the below upstream commit:
d3252ace0bc652a1a24446b6a549f969bf99 ("PCI: Restore resized BAR
state on resume")
We see that the same commit has been ported to UBUNTU18.X - PCI:
Restore resized BAR state on resume (bsc#1105355).
the fix has been submitted to upstream
https://patchwork.kernel.org/patch/11058689/
please include this patch in the upcoming releases.please let me know
if additional information required.
https://bugzilla.kernel.org/show_bug.cgi?id=203939
[Test case]
See that suspend/resume works correctly after applying the patch
[Regression potential]
slim, itself fixes a regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838751/+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 1838755] Re: Megaraid_sas Driver Update Request
upstream commit id's are as below: commit 7fa3174b3ef4e517ebb8a08078871ceab705a969 7fa3174 scsi: megaraid_sas: Release Mutex lock before OCR in case of DCMD timeout commit 62a04f81e6133c8eaa5e93e15eab1ad2511a45db 62a04f8 scsi: megaraid_sas: IRQ poll to avoid CPU hard lockups -- 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/1838755 Title: Megaraid_sas Driver Update Request Status in linux package in Ubuntu: Incomplete Bug description: Please consider below megaraid_sas driver's upstream commits for upcoming UBUNTU releases: commit 7fa3174b3ef4e517ebb8a08078871ceab705a969 7fa3174 scsi: megaraid_sas: Release Mutex lock before OCR in case of DCMD timeout commit 62a04f81e6133c8eaa5e93e15eab1ad2511a45db 62a04f8 scsi: megaraid_sas: IRQ poll to avoid CPU hard lockups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838755/+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 1838751] Re: Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas adapters(SAS3.5 onwards)
The BUG #1838755 is a kernel BUG (related to PCI subsystem), which is analysed
and fix is also provided.
The fix is reviewed by the PCI subsystem maintainers and is submitted to the
upstream. Will share the commit id once accepted.
--
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/1838751
Title:
Suspend to RAM(S3) does not wake up for latest megaraid and mpt3sas
adapters(SAS3.5 onwards)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Latest megaraid_sas and mpt3sas adapters which support Resizable BAR
with 1 MB BAR size fails to initialize during system resume from S3
sleep.
As per our findings the issue is caused by the below upstream commit:
d3252ace0bc652a1a24446b6a549f969bf99 ("PCI: Restore resized BAR
state on resume")
We see that the same commit has been ported to UBUNTU18.X - PCI:
Restore resized BAR state on resume (bsc#1105355).
the fix has been submitted to upstream
https://patchwork.kernel.org/patch/11058689/
please include this patch in the upcoming releases.please let me know if
additional information required.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838751/+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 1838755] Re: Megaraid_sas Driver Update Request
This is not a duplicate of BUG #1838751.
BUG #1838755 is just a request (not a BUG) to integrate the megaraid_sas
driver update/changes which would handle certain scenarios identified as
critical ("critical" in the sense,that, if these scenarios are not
handled the driver may not function as expected).
The above issue was identified, fix is reviewed and is submitted to the
upstream. Once the fix is accepted the commit id will be shared.
--
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/1838755
Title:
Megaraid_sas Driver Update Request
Status in linux package in Ubuntu:
Incomplete
Bug description:
Please consider below megaraid_sas driver's upstream commits for
upcoming UBUNTU releases:
commit 7fa3174b3ef4e517ebb8a08078871ceab705a969
7fa3174 scsi: megaraid_sas: Release Mutex lock before OCR in case of DCMD
timeout
commit 62a04f81e6133c8eaa5e93e15eab1ad2511a45db
62a04f8 scsi: megaraid_sas: IRQ poll to avoid CPU hard lockups
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838755/+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 1813796] Re: kernel bug null pointer dereference
*** This bug is a duplicate of bug 1813663 *** https://bugs.launchpad.net/bugs/1813663 I had similar problem with my Thinkpad X1 and Thinkpad Thunderbolt dock. Updating to the newest release of kernel (4.15.0-45-generic) today morning fixed the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813796 Title: kernel bug null pointer dereference Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to linux-image-4.15.0-44-generic via the update manager today, I can't log in anymore. The login screen appears, but as soon as I've entered my password and hit enter, the desktop locks up, keyboard stops working and display goes black. Network is still working, so I could login remotely and see the crash live via journalctl. I attached the full output of journalctl -k -b -1 In short it says BUG: unable to handle kernel NULL pointer dereference at 0245 IP: intel_ddi_post_disable+0x54/0x170 [i915] PGD 0 P4D 0 Oops: [#1] SMP PTI Infos about my hardware: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy linux-image-4.15.0-44-generic linux-image-4.15.0-44-generic: Installiert: 4.15.0-44.47 Installationskandidat: 4.15.0-44.47 Versionstabelle: *** 4.15.0-44.47 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status Rebooting to the previous kernel 4.15.0-43 doesn't have this issue and I can login without issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813796/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
** Changed in: linux (Ubuntu) Assignee: Biral Choudhury (biralchoudhury) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => anand maity (anandmaity) -- 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/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: SRU Justification: [Impact] Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work. [Test Case] Touchpad doesn't work on the system. With the patch, touchpad works. [Regression Potential] Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to one device. --- Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+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 1764645] Re: Bluetooth not working
Bluetooth doesn't turn on, fresh install on formatted disk on Lenovo
G50, single OS.
lsusb | grep -i blue
Bus 002 Device 006: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth
4.0
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename: bionic
dmesg | grep -i blue
[ 15.902210] Bluetooth: Core ver 2.22
[ 15.902232] Bluetooth: HCI device and connection manager initialized
[ 15.902236] Bluetooth: HCI socket layer initialized
[ 15.902239] Bluetooth: L2CAP socket layer initialized
[ 15.902247] Bluetooth: SCO socket layer initialized
[ 15.916264] Bluetooth: hci0: don't support firmware rome 0x3101
[ 22.243557] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 22.243559] Bluetooth: BNEP filters: protocol multicast
[ 22.243563] Bluetooth: BNEP socket layer initialized
--
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/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
In addition to my comment #53
uname -a
Linux system 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
--
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/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
/dev/snd/controlC0: stormy 1484 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 08:46:30 2018
HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: ASUSTeK COMPUTER INC. G750JH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-15-generic N/A
linux-backports-mo
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Some automatic updates came which I installed and now I am able to access and change settings of BIOS. Also it is recognising bootable USB drive(with Windows OS). Have not yet changed from Ubuntu, later will see. Thank you guys for working things out. "Lenovo Y500 45Q" -- 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I am using Lubuntu 17.10 Few week back I did this install and due to some requirement I wanted to change OS. But to my bad luck the initial BIOS page itself is not coming and while searching for the solution I got to know the big issue. Its not the way an OS should behave. My Laptop is LENOVO Y500 45Q. Either Lenovo or Ubuntu should come up with solution... every one is not that equipped to do BIOS flash or some hardware changes by themselves. Hoping to get some solution soon... :( -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: An update to linux kernel on Ubuntu 17.10 that enabled the intel-spi-* drivers made Insyde BIOS unusable. Main issues were Settings being not stored, USB Boot impossible and EFI entries read- only. Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS. Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into Linux and BIOS should be restored to a working state. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10) Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 (not fixed by 4.14.9) Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+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 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream'
Hi Joseph, Did we zero down on the kernel that we see this issue with. Can we pull in the latest bnxt driver for 16.04.03 updates ? Thanks, Anand -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Joseph Salisbury Sent: Thursday, September 21, 2017 12:54 AM To: anand.ra...@broadcom.com Subject: [Bug 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream' The purpose of going through a "Reverse" bisect is to identify the commit that fixes this bug and adds the proper CuW B1 device IDs. To do that, we would want to figure out the last kernel that did not have the ids and the first kernel that did. However, it sounds like all the upstream kernels you tested so far do not exhibit this bug (4.4 -> 4.13), but the 16.04.3 kernel does have the bug? Also, the 16.04.3 kernel should be 4.10 based, but you see version 4.4.0-87? Is that correct? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1715368 Title: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream' Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Bug description: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03. CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en driver(0.1.24) Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver. root@ubuntu160403:~# modinfo bnxt_en filename: /lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko version: 0.1.24 description: Broadcom BCM573xx network driver license: GPL srcversion: 0110469E9118262B301CA46 alias: pci:v14E4d16D3sv*sd*bc*sc*i* alias: pci:v14E4d16CBsv*sd*bc*sc*i* alias: pci:v14E4d16D2sv*sd*bc*sc*i* alias: pci:v14E4d16D1sv*sd*bc*sc*i* alias: pci:v14E4d16CAsv*sd*bc*sc*i* alias: pci:v14E4d16C9sv*sd*bc*sc*i* depends: vxlan intree: Y vermagic: 4.4.0-87-generic SMP mod_unload modversions OS Details: root@ubuntu160403:~# cat /etc/issue Ubuntu 16.04.3 LTS \n \l root@ubuntu160403:~# uname -a Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715368/+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/1715368 Title: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream' Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Bug description: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03. CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en driver(0.1.24) Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver. root@ubuntu160403:~# modinfo bnxt_en filename: /lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko version: 0.1.24 description: Broadcom BCM573xx network driver license: GPL srcversion: 0110469E9118262B301CA46 alias: pci:v14E4d16D3sv*sd*bc*sc*i* alias: pci:v14E4d16CBsv*sd*bc*sc*i* alias: pci:v14E4d16D2sv*sd*bc*sc*i* alias: pci:v14E4d16D1sv*sd*bc*sc*i* alias: pci:v14E4d16CAsv*sd*bc*sc*i* alias: pci:v14E4d16C9sv*sd*bc*sc*i* depends: vxlan intree: Y vermagic: 4.4.0-87-generic SMP mod_unload modversions OS Details: root@ubuntu160403:~# cat /etc/issue Ubuntu 16.04.3 LTS \n \l root@ubuntu160403:~# uname -a Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715368/+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 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream'
Joseph, Murali has tried with 4.4 kernel as well and even that kernel has Cu device ID's. Can we not just pull in the latest kernel patch which is 4.13. Thanks, Anand -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Joseph Salisbury Sent: Wednesday, September 13, 2017 8:45 PM To: anand.ra...@broadcom.com Subject: [Bug 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream' Can you also test the follow kernels: 4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ 4.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/ 4.10 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/ Again, you don't have to test every kernel, just up until the first kernel that does not have this bug. Thanks in advance! -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1715368 Title: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream' Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Bug description: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03. CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en driver(0.1.24) Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver. root@ubuntu160403:~# modinfo bnxt_en filename: /lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko version: 0.1.24 description: Broadcom BCM573xx network driver license: GPL srcversion: 0110469E9118262B301CA46 alias: pci:v14E4d16D3sv*sd*bc*sc*i* alias: pci:v14E4d16CBsv*sd*bc*sc*i* alias: pci:v14E4d16D2sv*sd*bc*sc*i* alias: pci:v14E4d16D1sv*sd*bc*sc*i* alias: pci:v14E4d16CAsv*sd*bc*sc*i* alias: pci:v14E4d16C9sv*sd*bc*sc*i* depends: vxlan intree: Y vermagic: 4.4.0-87-generic SMP mod_unload modversions OS Details: root@ubuntu160403:~# cat /etc/issue Ubuntu 16.04.3 LTS \n \l root@ubuntu160403:~# uname -a Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715368/+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/1715368 Title: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream' Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Bug description: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03. CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en driver(0.1.24) Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver. root@ubuntu160403:~# modinfo bnxt_en filename: /lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko version: 0.1.24 description: Broadcom BCM573xx network driver license: GPL srcversion: 0110469E9118262B301CA46 alias: pci:v14E4d16D3sv*sd*bc*sc*i* alias: pci:v14E4d16CBsv*sd*bc*sc*i* alias: pci:v14E4d16D2sv*sd*bc*sc*i* alias: pci:v14E4d16D1sv*sd*bc*sc*i* alias: pci:v14E4d16CAsv*sd*bc*sc*i* alias: pci:v14E4d16C9sv*sd*bc*sc*i* depends: vxlan intree: Y vermagic: 4.4.0-87-generic SMP mod_unload modversions OS Details: root@ubuntu160403:~# cat /etc/issue Ubuntu 16.04.3 LTS \n \l root@ubuntu160403:~# uname -a Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715368/+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 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03
We installed the latest upstream kernel and we do see the Broadcom devices listed. Below is the mail I have copied from the Engineer who verified this. Hi Anand, Installed 4.13.0-041300 upstream kernel on top on Ubuntu 16.04.03 base kernel. It has bnxt_en 1.7.0 driver and both CuW A0 and CuW+ B1 cards are getting detected with this driver. Below is the modinfo bnxt_en driver output. root@ubuntu160403-maaa:~# modinfo bnxt_en filename: /lib/modules/4.13.0-041300-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko version:1.7.0 description:Broadcom BCM573xx network driver license:GPL srcversion: C20CD2026202947F8BF535A alias: pci:v14E4d16E5sv*sd*bc*sc*i* alias: pci:v14E4d16E1sv*sd*bc*sc*i* alias: pci:v14E4d16DCsv*sd*bc*sc*i* alias: pci:v14E4d16D3sv*sd*bc*sc*i* alias: pci:v14E4d16CBsv*sd*bc*sc*i* alias: pci:v14E4d16C1sv*sd*bc*sc*i* alias: pci:v14E4d1609sv*sd*bc*sc*i* alias: pci:v14E4d1606sv*sd*bc*sc*i* alias: pci:v14E4d1614sv*sd*bc*sc*i* alias: pci:v14E4d16F1sv*sd*bc*sc*i* alias: pci:v14E4d16EFsv*sd*bc*sc*i* alias: pci:v14E4d16EEsv*sd*bc*sc*i* alias: pci:v14E4d16EDsv*sd*bc*sc*i* alias: pci:v14E4d16ECsv*sd*bc*sc*i* alias: pci:v14E4d16EBsv*sd*bc*sc*i* alias: pci:v14E4d16EAsv*sd*bc*sc*i* alias: pci:v14E4d16E9sv*sd*bc*sc*i* alias: pci:v14E4d16E8sv*sd*bc*sc*i* alias: pci:v14E4d16E7sv*sd*bc*sc*i* alias: pci:v14E4d16E3sv*sd*bc*sc*i* alias: pci:v14E4d16E2sv*sd*bc*sc*i* alias: pci:v14E4d16DFsv*sd*bc*sc*i* alias: pci:v14E4d16DEsv*sd*bc*sc*i* alias: pci:v14E4d16D9sv*sd*bc*sc*i* alias: pci:v14E4d16D8sv*sd*bc*sc*i* alias: pci:v14E4d16D7sv*sd*bc*sc*i* alias: pci:v14E4d16D6sv*sd*bc*sc*i* alias: pci:v14E4d16D5sv*sd*bc*sc*i* alias: pci:v14E4d16D4sv*sd*bc*sc*i* alias: pci:v14E4d16D2sv*sd*bc*sc*i* alias: pci:v14E4d16D1sv*sd*bc*sc*i* alias: pci:v14E4d16D0sv*sd*bc*sc*i* alias: pci:v14E4d16CFsv*sd*bc*sc*i* alias: pci:v14E4d16CEsv*sd*bc*sc*i* alias: pci:v14E4d16CDsv*sd*bc*sc*i* alias: pci:v14E4d16CCsv*sd*bc*sc*i* alias: pci:v14E4d16CAsv*sd*bc*sc*i* alias: pci:v14E4d16C9sv*sd*bc*sc*i* alias: pci:v14E4d16C8sv*sd*bc*sc*i* alias: pci:v14E4d16C0sv*sd*bc*sc*i* depends: intree: Y name: bnxt_en vermagic: 4.13.0-041300-generic SMP mod_unload ** Summary changed: - Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 + Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream' -- 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/1715368 Title: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream' Status in linux package in Ubuntu: Incomplete Bug description: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03. CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en driver(0.1.24) Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver. root@ubuntu160403:~# modinfo bnxt_en filename: /lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko version: 0.1.24 description: Broadcom BCM573xx network driver license: GPL srcversion: 0110469E9118262B301CA46 alias: pci:v14E4d16D3sv*sd*bc*sc*i* alias: pci:v14E4d16CBsv*sd*bc*sc*i* alias: pci:v14E4d16D2sv*sd*bc*sc*i* alias: pci:v14E4d16D1sv*sd*bc*sc*i* alias: pci:v14E4d16CAsv*sd*bc*sc*i* alias: pci:v14E4d16C9sv*sd*bc*sc*i* depends: vxlan intree: Y vermagic: 4.4.0-87-generic SMP mod_unload modversions OS Details: root@ubuntu160403:~# cat /etc/issue Ubuntu 16.04.3 LTS \n \l root@ubuntu160403:~# uname -a Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715368/+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 889012] Re: CPU time incorrect in 10.04
Hi guys, Ive changed the status to fix released by mistake. Can you please revert it back to confirmed ? ** Changed in: linux-ec2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ec2 in Ubuntu. https://bugs.launchpad.net/bugs/889012 Title: CPU time incorrect in 10.04 Status in linux-ec2 package in Ubuntu: Fix Released Bug description: I want to report that the CPU time bug is still present in the following kernel 2.6.32-317-ec2 on AWS instance m1.large with CPU model name : Intel(R) Xeon(R) CPU E5507 @ 2.27GHz I logged the output of ps every minute and I can now show the bug happening, as you can see the CPU time originally at 35790:43 does get corrupted and the next minute jumps at 17179869:11 to reach 29322904:44 1 minute later www-data 8269 31.3 9.2 853516 725496 ? Sl Aug23 35789:36 /usr/local/lib/erlang/erts-5.8.4/bin/beam.smp -P ... www-data 8269 31.3 9.2 866128 731640 ? Sl Aug23 35790:09 /usr/local/lib/erlang/erts-5.8.4/bin/beam.smp -P ... www-data 8269 31.3 9.3 868704 738800 ? Sl Aug23 35790:43 /usr/local/lib/erlang/erts-5.8.4/bin/beam.smp -P ... www-data 8269 31.3 9.4 872964 742660 ? Sl Aug23 35791:17 /usr/local/lib/erlang/erts-5.8.4/bin/beam.smp -P ... www-data 8269 120093018 9.4 885060 748036 ? Sl Aug23 17179869:11 /usr/local/lib/erlang/erts-5.8.4/bin/beam.smp -P ... www-data 8269 10652 9.3 868748 739144 ? Sl Aug23 29322904:44 /usr/local/lib/erlang/erts-5.8.4/bin/beam.smp -P ... It took us around 3 months running this process at around 30% load to reach this condition Because of this problem the machine currently reports a load of 0 when instead we know it should report between 20 and 40% depending by the moment of the day. Please let me know If I need to open a specific ticket for this issue. Today we're going to upgrade to 2.6.32-319-ec2 thanks, Paolo Negri To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/889012/+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 1296916] Re: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia]
Alberto Salvia Novella : "It renders the system temporarily or permanently unusable." What does it mean when you say that ? How makes it unusable ? Are you unable to boot ? GUI Freezes ? I think if you provide more information it will help the developers figure it out quicker. I would suggest you provide more details. -- 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/1296916 Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: Confirmed Bug description: Frustrating issues everywhere right from booting itself. Says Alloc magic is broken. Happens when connecting to external monitor. I am sure relates to GRUB ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anand 2092 F pulseaudio Date: Tue Mar 25 00:55:23 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=06701efe-03ad-4c2f-ad60-c6dd1a5144c3 InstallationDate: Installed on 2014-03-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322) InterpreterPath: /usr/bin/python3.4 Lsusb: Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 002: ID 1a2c:0c21 China Resource Semico Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=6c5c9f3f-77a2-41ac-8fb7-7e9745b235ce ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/26/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr217:bd08/26/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN 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/1296916/+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 1296916] Re: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia]
Looks it could not update the nvidia driver after the kernel update released today in nighly builds. dpkg configure -a resolved a few issues and I can now swtich between internal and external displays. For the alloc magic error, I updated bios of the ASUS K50IN to the most recent one and it seems to have resolved it. However, this is too bad if that is the solution. All versions of ubuntu including 13.10 and lower worked on this laptop without a glitch. I would like to know what changed in 14.04 that it demanded a BIOS update. I will keep updating this thread as I find anything 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/1296916 Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: Confirmed Bug description: Frustrating issues everywhere right from booting itself. Says Alloc magic is broken. Happens when connecting to external monitor. I am sure relates to GRUB ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anand 2092 F pulseaudio Date: Tue Mar 25 00:55:23 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=06701efe-03ad-4c2f-ad60-c6dd1a5144c3 InstallationDate: Installed on 2014-03-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322) InterpreterPath: /usr/bin/python3.4 Lsusb: Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 002: ID 1a2c:0c21 China Resource Semico Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=6c5c9f3f-77a2-41ac-8fb7-7e9745b235ce ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/26/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr217:bd08/26/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN 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/1296916/+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 1296916] Re: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia]
I am using Fallback , but the following applies to Regular Unity Login too, After Today's Update : When trying to reboot with External Monitor connected, gives alloc magic is broken error. Disconnecting the External Monitor's VGA cable boots up fine. When connecting the external monitor after boot and after login, the display takes a long time to appear in external display, Looks as if the system is hanged up. After login with external display, sometimes the Wirelss Network Functionality is gone and I cannot see any Wireless Cards in the network applet. Disabling and enabling network, does not do any good either and does not show up the Wireless connections as being available. A couple of hit and trail attempts with monitor connected, disconnected, and then re-login shows up the Wifi Networks fine. Overall GUI is slow after today's updates. I was unable to switch back to Opensource Nvidia Driver. Previously I could disable the Nvidia Proprietary driver and switch to open source one, but now I can no longer do so. If any more information is required, I can send details only after next 10 hours or so. Please let me know if there are any specific tests you would want me to do. -- 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/1296916 Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: Confirmed Bug description: Frustrating issues everywhere right from booting itself. Says Alloc magic is broken. Happens when connecting to external monitor. I am sure relates to GRUB ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anand 2092 F pulseaudio Date: Tue Mar 25 00:55:23 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=06701efe-03ad-4c2f-ad60-c6dd1a5144c3 InstallationDate: Installed on 2014-03-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322) InterpreterPath: /usr/bin/python3.4 Lsusb: Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 002: ID 1a2c:0c21 China Resource Semico Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=6c5c9f3f-77a2-41ac-8fb7-7e9745b235ce ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/26/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr217:bd08/26/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN 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/1296916/+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 1296916] Re: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia]
Not sure, what you meant by saying : This change was made by a bot. This does happen. There are a lot of other issues that are happening also after today's update. If there is someone listening, then I will post more details. -- 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/1296916 Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: Confirmed Bug description: Frustrating issues everywhere right from booting itself. Says Alloc magic is broken. Happens when connecting to external monitor. I am sure relates to GRUB ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anand 2092 F pulseaudio Date: Tue Mar 25 00:55:23 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=06701efe-03ad-4c2f-ad60-c6dd1a5144c3 InstallationDate: Installed on 2014-03-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322) InterpreterPath: /usr/bin/python3.4 Lsusb: Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 002: ID 1a2c:0c21 China Resource Semico Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=6c5c9f3f-77a2-41ac-8fb7-7e9745b235ce ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/26/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr217:bd08/26/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN 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/1296916/+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 1296916] [NEW] [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia]
Public bug reported: Frustrating issues everywhere right from booting itself. Says Alloc magic is broken. Happens when connecting to external monitor. I am sure relates to GRUB ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anand 2092 F pulseaudio Date: Tue Mar 25 00:55:23 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=06701efe-03ad-4c2f-ad60-c6dd1a5144c3 InstallationDate: Installed on 2014-03-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322) InterpreterPath: /usr/bin/python3.4 Lsusb: Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 002: ID 1a2c:0c21 China Resource Semico Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=6c5c9f3f-77a2-41ac-8fb7-7e9745b235ce ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/26/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr217:bd08/26/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume suspend 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/1296916 Title: [ASUSTeK Computer Inc. K50IN] suspend/resume failure [non-free: nvidia] Status in “linux” package in Ubuntu: New Bug description: Frustrating issues everywhere right from booting itself. Says Alloc magic is broken. Happens when connecting to external monitor. I am sure relates to GRUB ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anand 2092 F pulseaudio Date: Tue Mar 25 00:55:23 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=06701efe-03ad-4c2f-ad60-c6dd1a5144c3 InstallationDate: Installed on 2014-03-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322) InterpreterPath: /usr/bin/python3.4 Lsusb: Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 002: ID 1a2c:0c21 China Resource Semico Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=6c5c9f3f-77a2-41ac-8fb7-7e9745b235ce ro quiet splash PulseList: Error: command ['pacmd',
[Kernel-packages] [Bug 1276651] Re: BCM wl driver crashes during roaming
This issue is seen with bcmwl version 6.30.223.141 on Ubuntu 14.04 hprem@hprem-rmbp:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)" hprem@hprem-rmbp:~$ sudo dpkg -l bcmwl-kernel-source Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 amd64 Broadcom 802.11 Linux STA wireless driver source hprem@hprem-rmbp:~$ -- 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/1276651 Title: BCM wl driver crashes during roaming Status in “bcmwl” package in Ubuntu: New Bug description: Whenever my wireless connection roams from one AP to another AP, I see the following crash [ 5089.124259] [ cut here ] [ 5089.124283] WARNING: CPU: 1 PID: 605 at /home/apw/COD/linux/net/wireless/sme.c:797 cfg80211_roamed+0x97/0xa0 [cfg80211]() [ 5089.124284] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_cirrus parport_pc bnep ppdev rfcomm binfmt_misc nls_iso8859_1 lib80211_crypt_tkip intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd wl(POF) hid_apple joydev hid_generic btusb bluetooth uvcvideo snd_hda_intel snd_hda_codec snd_hwdep nouveau videobuf2_vmalloc snd_pcm videobuf2_memops videobuf2_core usbhid snd_page_alloc videodev hid snd_seq_midi snd_seq_midi_event bcm5974 i915 snd_rawmidi applesmc snd_seq input_polldev mxm_wmi snd_seq_device wmi lib80211 snd_timer ttm drm_kms_helper cfg80211 snd drm mei_me soundcore microcode i2c_algo_bit mei apple_gmux lpc_ich video apple_bl mac_hid lp parport ahci sdhci_pci libahci sdhci [ 5089.124316] CPU: 1 PID: 605 Comm: wl_event_handle Tainted: PF O 3.13.0-031300-generic #201401192235 [ 5089.124317] Hardware name: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS MBP101.88Z.00EE.B03.1212211437 12/21/2012 [ 5089.124318] 031d 880457115d68 8173356d 0007 [ 5089.124321] 880457115da8 81067bbc 88045528be1a [ 5089.124323] 880454dc5000 8800362e6120 0095 880407c603c0 [ 5089.124325] Call Trace: [ 5089.124331] [] dump_stack+0x46/0x58 [ 5089.124334] [] warn_slowpath_common+0x8c/0xc0 [ 5089.124336] [] warn_slowpath_null+0x1a/0x20 [ 5089.124345] [] cfg80211_roamed+0x97/0xa0 [cfg80211] [ 5089.124367] [] wl_bss_connect_done.isra.21+0x98/0x1a0 [wl] [ 5089.124383] [] wl_notify_connect_status+0x1fc/0x410 [wl] [ 5089.124399] [] wl_event_handler+0x55/0x220 [wl] [ 5089.124414] [] ? wl_get_assoc_ies+0x240/0x240 [wl] [ 5089.124417] [] kthread+0xc9/0xe0 [ 5089.124419] [] ? flush_kthread_worker+0xb0/0xb0 [ 5089.124422] [] ret_from_fork+0x7c/0xb0 [ 5089.124424] [] ? flush_kthread_worker+0xb0/0xb0 [ 5089.124425] ---[ end trace 8ddb9ebe0f635ec5 ]--- [ 5099.616376] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error [ 5112.795658] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error [ 5127.215934] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1276651/+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 1276651] [NEW] BCM wl driver crashes during roaming
Public bug reported: Whenever my wireless connection roams from one AP to another AP, I see the following crash [ 5089.124259] [ cut here ] [ 5089.124283] WARNING: CPU: 1 PID: 605 at /home/apw/COD/linux/net/wireless/sme.c:797 cfg80211_roamed+0x97/0xa0 [cfg80211]() [ 5089.124284] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_cirrus parport_pc bnep ppdev rfcomm binfmt_misc nls_iso8859_1 lib80211_crypt_tkip intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd wl(POF) hid_apple joydev hid_generic btusb bluetooth uvcvideo snd_hda_intel snd_hda_codec snd_hwdep nouveau videobuf2_vmalloc snd_pcm videobuf2_memops videobuf2_core usbhid snd_page_alloc videodev hid snd_seq_midi snd_seq_midi_event bcm5974 i915 snd_rawmidi applesmc snd_seq input_polldev mxm_wmi snd_seq_device wmi lib80211 snd_timer ttm drm_kms_helper cfg80211 snd drm mei_me soundcore microcode i2c_algo_bit mei apple_gmux lpc_ich video apple_bl mac_hid lp parport ahci sdhci_pci libahci sdhci [ 5089.124316] CPU: 1 PID: 605 Comm: wl_event_handle Tainted: PF O 3.13.0-031300-generic #201401192235 [ 5089.124317] Hardware name: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS MBP101.88Z.00EE.B03.1212211437 12/21/2012 [ 5089.124318] 031d 880457115d68 8173356d 0007 [ 5089.124321] 880457115da8 81067bbc 88045528be1a [ 5089.124323] 880454dc5000 8800362e6120 0095 880407c603c0 [ 5089.124325] Call Trace: [ 5089.124331] [] dump_stack+0x46/0x58 [ 5089.124334] [] warn_slowpath_common+0x8c/0xc0 [ 5089.124336] [] warn_slowpath_null+0x1a/0x20 [ 5089.124345] [] cfg80211_roamed+0x97/0xa0 [cfg80211] [ 5089.124367] [] wl_bss_connect_done.isra.21+0x98/0x1a0 [wl] [ 5089.124383] [] wl_notify_connect_status+0x1fc/0x410 [wl] [ 5089.124399] [] wl_event_handler+0x55/0x220 [wl] [ 5089.124414] [] ? wl_get_assoc_ies+0x240/0x240 [wl] [ 5089.124417] [] kthread+0xc9/0xe0 [ 5089.124419] [] ? flush_kthread_worker+0xb0/0xb0 [ 5089.124422] [] ret_from_fork+0x7c/0xb0 [ 5089.124424] [] ? flush_kthread_worker+0xb0/0xb0 [ 5089.124425] ---[ end trace 8ddb9ebe0f635ec5 ]--- [ 5099.616376] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error [ 5112.795658] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error [ 5127.215934] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- 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/1276651 Title: BCM wl driver crashes during roaming Status in “bcmwl” package in Ubuntu: New Bug description: Whenever my wireless connection roams from one AP to another AP, I see the following crash [ 5089.124259] [ cut here ] [ 5089.124283] WARNING: CPU: 1 PID: 605 at /home/apw/COD/linux/net/wireless/sme.c:797 cfg80211_roamed+0x97/0xa0 [cfg80211]() [ 5089.124284] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_cirrus parport_pc bnep ppdev rfcomm binfmt_misc nls_iso8859_1 lib80211_crypt_tkip intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd wl(POF) hid_apple joydev hid_generic btusb bluetooth uvcvideo snd_hda_intel snd_hda_codec snd_hwdep nouveau videobuf2_vmalloc snd_pcm videobuf2_memops videobuf2_core usbhid snd_page_alloc videodev hid snd_seq_midi snd_seq_midi_event bcm5974 i915 snd_rawmidi applesmc snd_seq input_polldev mxm_wmi snd_seq_device wmi lib80211 snd_timer ttm drm_kms_helper cfg80211 snd drm mei_me soundcore microcode i2c_algo_bit mei apple_gmux lpc_ich video apple_bl mac_hid lp parport ahci sdhci_pci libahci sdhci [ 5089.124316] CPU: 1 PID: 605 Comm: wl_event_handle Tainted: PF O 3.13.0-031300-generic #201401192235 [ 5089.124317] Hardware name: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS MBP101.88Z.00EE.B03.1212211437 12/21/2012 [ 5089.124318] 031d 880457115d68 8173356d 0007 [ 5089.124321] 880457115da8 81067bbc 88045528be1a [ 5089.124323] 880454dc5000 8800362e6120 0095 880407c603c0 [ 5089.124325] Call Trace: [ 5089.124331] [] dump_stack+0x46/0x58 [ 5089.124334] [] warn_slowpath_common+0x8c/0xc0 [ 5089.124336] [] warn_slowpath_null+0x1a/0x20 [ 5089.124345] [] cfg80211_roamed+0x97/0xa0 [cfg80211] [ 5089.124367] [] wl_bss_connect_done.isra.21+0x98/0x1a0 [wl] [ 5089.124383] [] wl_notify_connect_status+0x1fc/0x410 [wl] [ 5089.124399] [] wl_event_handler+0x55/0x220 [wl] [ 5089.124414] [] ? wl_get_assoc_ies+0x240/0x24
[Kernel-packages] [Bug 1205329] Re: Nouveau crashes at nouveau_object_decf on logout and system hangs on restarting lightdm
Please feel free to close this 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/1205329 Title: Nouveau crashes at nouveau_object_decf on logout and system hangs on restarting lightdm Status in “linux” package in Ubuntu: Incomplete Bug description: I am seeing nouveau consistently crashing @ nouveau_object_decf on logging out. On trying to restart the display manager, it hangs [29140.815287] nouveau E[ I2C][:01:00.0] AUXCH(1): begin idle timeout 0x [29140.816398] nouveau E[ I2C][:01:00.0] AUXCH(1): begin idle timeout 0x [29140.817495] nouveau E[ I2C][:01:00.0] AUXCH(3): begin idle timeout 0x [29140.819535] nouveau E[ I2C][:01:00.0] AUXCH(3): begin idle timeout 0x [29140.821547] nouveau E[ I2C][:01:00.0] AUXCH(2): begin idle timeout 0x [29140.823558] nouveau E[ I2C][:01:00.0] AUXCH(2): begin idle timeout 0x [29264.387025] BUG: unable to handle kernel NULL pointer dereference at (null) [29264.387062] IP: [< (null)>] (null) [29264.387081] PGD 0 [29264.387090] Oops: 0010 [#1] SMP [29264.387105] Modules linked in: snd_hda_codec_hdmi intel_powerclamp coretemp lib80211_crypt_tkip kvm_intel kvm crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev applesmc input_polldev snd_hda_codec_cirrus parport_pc ppdev uvcvideo snd_hda_intel wl(POF) microcode snd_hda_codec videobuf2_vmalloc videobuf2_memops snd_hwdep videobuf2_core snd_seq_midi bnep snd_seq_midi_event rfcomm videodev snd_rawmidi snd_pcm bluetooth bcm5974 snd_seq snd_page_alloc lib80211 lpc_ich cfg80211 mei_me mei snd_seq_device snd_timer snd apple_gmux soundcore apple_bl mac_hid binfmt_misc nls_iso8859_1 lp parport hid_apple nouveau mxm_wmi hid_generic i915 wmi sdhci_pci tg3 ttm ahci i2c_algo_bit sdhci usbhid drm_kms_helper libahci ptp hid drm pps_core video [last unloaded: btusb] [29264.387428] CPU: 3 PID: 1337 Comm: Xorg Tainted: PF W O 3.10.2-031002-generic #201307212216 [29264.387460] Hardware name: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS MBP101.88Z.00EE.B03.1212211437 12/21/2012 [29264.387498] task: 880452ea5dc0 ti: 8804570c2000 task.ti: 8804570c2000 [29264.387524] RIP: 0010:[<>] [< (null)>] (null) [29264.387551] RSP: 0018:8804570c3af0 EFLAGS: 00010246 [29264.387570] RAX: a02c0020 RBX: 88045717eb00 RCX: e000 [29264.387595] RDX: 0005 RSI: RDI: 88045717eb00 [29264.387620] RBP: 8804570c3b08 R08: R09: [29264.387645] R10: a021cb37 R11: 0002 R12: 0001 [29264.387671] R13: R14: 880458354688 R15: [29264.387696] FS: () GS:88046f2c() knlGS: [29264.387725] CS: 0010 DS: ES: CR0: 80050033 [29264.387745] CR2: CR3: 02c0d000 CR4: 001407e0 [29264.387770] DR0: DR1: DR2: [29264.387795] DR3: DR6: 0ff0 DR7: 0400 [29264.387819] Stack: [29264.387827] a01fb83a 88045717eb00 8804570c3b38 [29264.387857] a01fb7dd 880458354670 880458354670 [29264.387885] 880458354660 8804570c3b98 a01fa0db a02b3c31 [29264.387913] Call Trace: [29264.387939] [] ? nouveau_object_decf+0x3a/0xd0 [nouveau] [29264.387972] [] nouveau_object_dec+0x6d/0x90 [nouveau] [29264.388005] [] nouveau_handle_fini+0x13b/0x2b0 [nouveau] [29264.388039] [] nouveau_client_fini+0x61/0xa0 [nouveau] [29264.388081] [] nouveau_cli_destroy+0x2f/0x50 [nouveau] [29264.388119] [] nouveau_drm_postclose+0x19/0x20 [nouveau] [29264.388152] [] drm_release+0x340/0x520 [drm] [29264.388176] [] __fput+0xba/0x240 [29264.388195] [] fput+0xe/0x10 [29264.388215] [] task_work_run+0xc8/0xf0 [29264.388235] [] do_exit+0x19e/0x480 [29264.388256] [] ? __unqueue_futex+0x3f/0x80 [29264.388278] [] ? __dequeue_signal+0x6b/0xb0 [29264.388299] [] do_group_exit+0x44/0xa0 [29264.388320] [] get_signal_to_deliver+0x231/0x480 [29264.388345] [] do_signal+0x47/0x140 [29264.388366] [] ? account_user_time+0x9c/0xb0 [29264.388387] [] ? vtime_account_user+0x74/0x90 [29264.388410] [] do_notify_resume+0x88/0xc0 [29264.388433] [] int_signal+0x12/0x17 [29264.388451] Code: Bad RIP value. [29264.388467] RIP [< (null)>] (null) [29264.388487] RSP [29264.388499] CR2: [29264.388525] ---[ end trace 4ca6bffe89780c0c ]--- [29264.388543] Fixing recursive fault but
[Kernel-packages] [Bug 1205329] Re: Nouveau crashes at nouveau_object_decf on logout and system hangs on restarting lightdm
I dont see this crash with 3.13.0-4-generic (14.04) and 3.13.0-6-generic (13.10) kernel version. Both logout/login and supend/resume works perfectly fine. Though I do have problems now with switching off the dedicated video card. Though the integrated card powers the display, still on switching off the dedicated card, the screen turn blank. But thats a different 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/1205329 Title: Nouveau crashes at nouveau_object_decf on logout and system hangs on restarting lightdm Status in “linux” package in Ubuntu: Incomplete Bug description: I am seeing nouveau consistently crashing @ nouveau_object_decf on logging out. On trying to restart the display manager, it hangs [29140.815287] nouveau E[ I2C][:01:00.0] AUXCH(1): begin idle timeout 0x [29140.816398] nouveau E[ I2C][:01:00.0] AUXCH(1): begin idle timeout 0x [29140.817495] nouveau E[ I2C][:01:00.0] AUXCH(3): begin idle timeout 0x [29140.819535] nouveau E[ I2C][:01:00.0] AUXCH(3): begin idle timeout 0x [29140.821547] nouveau E[ I2C][:01:00.0] AUXCH(2): begin idle timeout 0x [29140.823558] nouveau E[ I2C][:01:00.0] AUXCH(2): begin idle timeout 0x [29264.387025] BUG: unable to handle kernel NULL pointer dereference at (null) [29264.387062] IP: [< (null)>] (null) [29264.387081] PGD 0 [29264.387090] Oops: 0010 [#1] SMP [29264.387105] Modules linked in: snd_hda_codec_hdmi intel_powerclamp coretemp lib80211_crypt_tkip kvm_intel kvm crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev applesmc input_polldev snd_hda_codec_cirrus parport_pc ppdev uvcvideo snd_hda_intel wl(POF) microcode snd_hda_codec videobuf2_vmalloc videobuf2_memops snd_hwdep videobuf2_core snd_seq_midi bnep snd_seq_midi_event rfcomm videodev snd_rawmidi snd_pcm bluetooth bcm5974 snd_seq snd_page_alloc lib80211 lpc_ich cfg80211 mei_me mei snd_seq_device snd_timer snd apple_gmux soundcore apple_bl mac_hid binfmt_misc nls_iso8859_1 lp parport hid_apple nouveau mxm_wmi hid_generic i915 wmi sdhci_pci tg3 ttm ahci i2c_algo_bit sdhci usbhid drm_kms_helper libahci ptp hid drm pps_core video [last unloaded: btusb] [29264.387428] CPU: 3 PID: 1337 Comm: Xorg Tainted: PF W O 3.10.2-031002-generic #201307212216 [29264.387460] Hardware name: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS MBP101.88Z.00EE.B03.1212211437 12/21/2012 [29264.387498] task: 880452ea5dc0 ti: 8804570c2000 task.ti: 8804570c2000 [29264.387524] RIP: 0010:[<>] [< (null)>] (null) [29264.387551] RSP: 0018:8804570c3af0 EFLAGS: 00010246 [29264.387570] RAX: a02c0020 RBX: 88045717eb00 RCX: e000 [29264.387595] RDX: 0005 RSI: RDI: 88045717eb00 [29264.387620] RBP: 8804570c3b08 R08: R09: [29264.387645] R10: a021cb37 R11: 0002 R12: 0001 [29264.387671] R13: R14: 880458354688 R15: [29264.387696] FS: () GS:88046f2c() knlGS: [29264.387725] CS: 0010 DS: ES: CR0: 80050033 [29264.387745] CR2: CR3: 02c0d000 CR4: 001407e0 [29264.387770] DR0: DR1: DR2: [29264.387795] DR3: DR6: 0ff0 DR7: 0400 [29264.387819] Stack: [29264.387827] a01fb83a 88045717eb00 8804570c3b38 [29264.387857] a01fb7dd 880458354670 880458354670 [29264.387885] 880458354660 8804570c3b98 a01fa0db a02b3c31 [29264.387913] Call Trace: [29264.387939] [] ? nouveau_object_decf+0x3a/0xd0 [nouveau] [29264.387972] [] nouveau_object_dec+0x6d/0x90 [nouveau] [29264.388005] [] nouveau_handle_fini+0x13b/0x2b0 [nouveau] [29264.388039] [] nouveau_client_fini+0x61/0xa0 [nouveau] [29264.388081] [] nouveau_cli_destroy+0x2f/0x50 [nouveau] [29264.388119] [] nouveau_drm_postclose+0x19/0x20 [nouveau] [29264.388152] [] drm_release+0x340/0x520 [drm] [29264.388176] [] __fput+0xba/0x240 [29264.388195] [] fput+0xe/0x10 [29264.388215] [] task_work_run+0xc8/0xf0 [29264.388235] [] do_exit+0x19e/0x480 [29264.388256] [] ? __unqueue_futex+0x3f/0x80 [29264.388278] [] ? __dequeue_signal+0x6b/0xb0 [29264.388299] [] do_group_exit+0x44/0xa0 [29264.388320] [] get_signal_to_deliver+0x231/0x480 [29264.388345] [] do_signal+0x47/0x140 [29264.388366] [] ? account_user_time+0x9c/0xb0 [29264.388387] [] ? vtime_account_user+0x74/0x90 [29264.3884
