[Kernel-packages] [Bug 1950046] Re: tg3 transmit timed out, resetting
apport information ** Tags added: apport-collected uec-images ** Description changed: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Oct 29 13:56 seq + crw-rw 1 root audio 116, 33 Oct 29 13:56 timer + AplayDevices: aplay: device_list:276: no soundcards found... + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + ArecordDevices: arecord: device_list:276: no soundcards found... + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-26 (559 days ago) + InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: HP ProLiant MicroServer Gen8 + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity + ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-38-generic N/A + linux-backports-modules-5.11.0-38-generic N/A + linux-firmware 1.187.20 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.11.0-38-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + dmi.bios.date: 04/04/2019 + dmi.bios.vendor: HP + dmi.bios.version: J06 + dmi.chassis.type: 7 + dmi.chassis.vendor: HP + dmi.ec.firmware.release: 2.78 + dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: + dmi.product.family: ProLiant + dmi.product.name: ProLiant MicroServer Gen8 + dmi.product.sku: 712317-421 + dmi.sys.vendor: HP ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538608/+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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20
[Kernel-packages] [Bug 1950046] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538613/+files/Lsusb-t.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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538611/+files/Lspci-vt.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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538615/+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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538619/+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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538621/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538609/+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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538617/+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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538620/+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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538618/+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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538614/+files/Lsusb-v.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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538612/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538610/+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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1950046/+attachment/5538616/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Confirmed Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 29 13:56 seq crw-rw 1 root audio 116, 33 Oct 29 13:56 timer AplayDevices: aplay: device_list:276: no soundcards found... ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: arecord: device_list:276: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-26 (559 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=/dev/mapper/svr2--vg-root ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.11.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/04/2019 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.78 dmi.modalias: dmi:bvnHP:bvrJ06:bd04/04/2019:efr2.78:svnHP:pnProLiantMicroServerGen8:pvr:sku712317-421:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
Switching back from Kernel 5.13.0 to 5.11.0 has fixed the issue. So this appears to be a kernel regression. -- 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/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+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 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
New best workaround, instead of blacklisting i2c-i801 keep it but disable interrupts and use polling instead. Step 1 Temporary and to be able to boot for step 2). a. To able to boot enter the grub menu (press ESC once during boot) b. select the (Ubuntu)Linux entry you want to boot and press "e" to edit this. c. edit the line start with " linux /boot/vmlinuz ." d. at the end of this line add " i2c-i801.disable_features=0x10" e. press F10 Now the machine will boot with this new i2c-i801 module parameter. This will happen only once, next boot will be without this parameter (unless you manually add it again by repeating the above steps). Step 2 After the boot and login, make it last: a. Run "sudo vi /etc/modprobe.d/i2c-i801.conf" b. Add the line "options i2c-i801 disable_features=0x10" c To make sure its used at boot-time run: "sudo update-initramfs -u" With this best workaround the module i2c-i801 is still loaded but using polling instead of interrupts. I think this is better then no i2c-i801 at all. I can boot, the issue does not occur. Still a workaround .. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1931001/+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 1948025] Re: Update the NVIDIA drivers October 2021
This bug was fixed in the package nvidia-graphics-drivers-495 - 495.44-0ubuntu1 --- nvidia-graphics-drivers-495 (495.44-0ubuntu1) jammy; urgency=medium * Initial release (LP: #1948025). -- Alberto Milone Tue, 26 Oct 2021 11:05:02 +0200 ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: Fix Released Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in fabric-manager-450 source package in Impish: Fix Committed Status in fabric-manager-460 source package in Impish: Fix Committed Status in libnvidia-nscq-450 source package in Impish: Fix Committed Status in libnvidia-nscq-460 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that
[Kernel-packages] [Bug 1949909] Re: Bluetooth crashes on resume from suspend
Hi, apologies if bluez is not the appropriate package. I have followed the above instructions in an case. 1. No crash files present. 2. The following problems were reported on errors.ubuntu.com https://errors.ubuntu.com/oops/feac943a-8847-11eb-9538-fa163ee63de6 https://errors.ubuntu.com/oops/7f383282-8841-11eb-9347-fa163e6cac46 https://errors.ubuntu.com/oops/414874ba-40fd-11e9-90bf-fa163e6cac46 https://errors.ubuntu.com/oops/6c93da58-3552-11e9-9eff-fa163e102db1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949909 Title: Bluetooth crashes on resume from suspend Status in bluez package in Ubuntu: Incomplete Bug description: Crash on resume from suspend. The following messages appear and the computer stops responding: ``` [ 26.227264] Bluetooth: hci0: Reading supported features failed (-16) [ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask failed (-95) ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 22:50:23 2021 InstallationDate: Installed on 2021-09-16 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949909/+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 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
It was the same for me. After running 5.4 kernel recovery and from there to the desktop, the system was running on llvmpipe. After rebooting to 5.11 kernel the system is still working on mesa... -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+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 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
Update, on mesa freeze after few minutes system use 100% cpu. -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+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 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1302 F pulseaudio /dev/snd/controlC1: bob1302 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=8cc37bc2-8e6b-42a0-8d35-815fac62d66b InstallationDate: Installed on 2015-12-13 (2156 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-161-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-161.169-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-161-generic N/A linux-backports-modules-4.15.0-161-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-161-generic x86_64 UpgradeStatus: Upgraded to bionic on 2020-10-07 (396 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/24/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: MYBDWi5v.86A.0033.2016.1124.2006 dmi.board.name: NUC5i5MYBE dmi.board.vendor: Intel Corporation dmi.board.version: H47797-202 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrMYBDWi5v.86A.0033.2016.1124.2006:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5MYBE:rvrH47797-202:cvn:ct3:cvr: ** Tags added: apport-collected -- 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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 003
[Kernel-packages] [Bug 1849713] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538688/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic
Problem still visible with linux-image-4.15.0-161-generic on Intel NUC5i5MYBE -- 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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538686/+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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538690/+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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538687/+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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538692/+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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538689/+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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538695/+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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538685/+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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538691/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538684/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538694/+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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1849713] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1849713/+attachment/5538693/+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/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [1.485776] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.485776] RSP: 0018:a6c8c1e539b0 EFLAGS: 00010286 [1.485778] RAX: RBX: 93621079 RCX: bce63a28 [1.485778] RDX: 0001 RSI: 0082 RDI: 0247 [1.485779] RBP: a6c8c1e53a40 R08: 036a R09: 0004 [1.485779] R10: 0040 R11: 0001 R12: 936210764400 [1.485780] R13: 9362104d9400 R14: ffea R15: 936210790358 [1.485781] FS: 7f76c1bfb680() GS:93622ee0() knlGS: [1.485782] CS: 0010 DS: ES: CR0: 80050033 [1.485783] CR2: 7f5c5aea088b CR3: 000410a5c004 CR4: 001606f0 [1.485783] Call Trace: [1.485807] i915_driver_load+0xa73/0xe60 [i915] [1.485829] i915_pci_probe+0x42/0x70 [i915] [1.485831] local_pci_probe+0x47/0xa0 [1.485833] pci_device_probe+0x10e/0x1c0 [1.485835] driver_probe_device+0x30c/0x490 [1.485836] __driver_attach+0xcc/0xf0 [1.485837] ? driver_probe_device+0x490/0x490 [1.485838] bus_for_each_dev+0x70/0xc0 [1.485840] driver_attach+0x1e/0x20 [1.485840] bus_add_driver+0x1c7/0x270 [1.485841] ? 0xc075c000 [1.485843] driver_register+0x60/0xe0 [1.485843] ? 0xc075c000 [1.485844] __pci_register_driver+0x5a/0x60 [1.485870] i915_init+0x5c/0x5f [i915] [1.485872] do_one_initcall+0x52/0x19f [1.485874] ? __slab_alloc+0x20/0x40 [1.485876] ? kmem_cache_alloc_trace+0x171/0x1b0 [1.485878] ? do_init_module+0x27/0x213 [1.485879] do_init_module+0x5f/0x213 [1.485881] load_module+0x16bc/0x1f10 [1.485884] ? ima_post_read_file+0x96/0xa0 [1.485886] SYSC_finit_module+0xfc/0x120 [1.485887] ? SYSC_finit_module+0xfc/0x120 [1.485889] SyS_finit_module+0xe/0x10 [1.485890] do_syscall_64+0x73/0x130 [1.485893] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1.485894] RIP: 0033:0x7f76c1705839 [1.485895] RSP: 002b:7ffe1ff8c938 EFLAGS: 0246 ORIG_RAX: 0139 [1.485896] RAX: ffda RBX: 55672d2fda50 RCX: 7f76c1705839 [1.485896] RDX: RSI: 7f76c13e4145 RDI: 0010 [1.485897] RBP: 7f76c13e4145 R08: R09: 7ffe1ff8ca50 [1.485897] R10: 0010 R11: 0246 R12: [1.485898] R13: 55672d2f93e0 R14: 0002 R15: 55672d2fda50 [1.485899] Code: e9 46 fc ff ff 48 c7 c6 37 b6 6e c0 48 c7 c7 8f a9 6e c0 e8 c4 0e 43 fb 0f 0b e9 73 fe ff ff 48 c7 c7 a0 0b 70 c0 e8 b1 0e 43 fb <0f> 0b e9 4b fe ff ff 48 c7 c6 44 b6 6e c0 48 c7 c7 8f a9 6e c0 [1.485918] ---[ end trace 32f66b94f944dd29 ]--- [1.488016] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Seems like no one does anything with 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1942759] Re: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install
@herwich I am in the same situation as you, since I also need to be on 18.04 for now. I am having trouble with the display driver as well. My model is equipped with an NVIDIA T500 (same as yours), but installing any NVIDIA display driver higher than version 390 fails and drops be in tty mode. Have you had success with using display drivers other than nomodeset? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1942759 Title: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS The touchpad is not detected with or without the Logitech M705 mouse plugged in. cat /proc/bus/input/devices Outputs: I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=20 0 0 1500f0210 43803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=101b Version=0111 N: Name="Logitech M705" P: Phys=usb-:00:14.0-4/input2:1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0004/0003:046D:101B.0005/input/input14 U: Uniq=101b-fc-92-33-df H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input15 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input16 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input17 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP HD Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input19 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP IR Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.2/input/input20 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 6 11:37:52 2021 InstallationDate: Installed on 2021-09-06 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1942759/+subscriptions -- Mailing
[Kernel-packages] [Bug 1950087] [NEW] ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug)
You have been subscribed to a public bug: I am attempting to install Ubuntu on to a new Razer Blade 15 Advanced (mid-2021) laptop. However, there seems to be some issues with kernel compatibility. When installing 20.04 LTS I have many issues with hardware not being detected (especially the intel AX210 wifi card). Running the 21.10 release from a live usb happily detected all of my hardware out of the box, with one show-stopping exception.. the internal nvme drive is NOT visible at all. I have tried every combination of bios options imaginable, as well as multiple Ubuntu-based distros such as Kubuntu, Pop!OS and Ubuntu Studio - all with the same results: 20.04 LTS detects the internal nvme and will install, but lacks important hardware support - while 21.10 (running in live mode) is compatible with all the essential hardware out of the box, but does not "see" the internal nvme. This seems to be an emerging issue.. see: https://askubuntu.com/questions/1370379/21-10-does-not-see-windows-nvme- drive/1374079?noredirect=1#comment2364713_1374079 And the current consensus seems to be that it is a kernel bug. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment installation live nvme -- ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug) https://bugs.launchpad.net/bugs/1950087 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950087] Re: ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug)
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: impish -- 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/1950087 Title: ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug) Status in linux package in Ubuntu: New Bug description: I am attempting to install Ubuntu on to a new Razer Blade 15 Advanced (mid-2021) laptop. However, there seems to be some issues with kernel compatibility. When installing 20.04 LTS I have many issues with hardware not being detected (especially the intel AX210 wifi card). Running the 21.10 release from a live usb happily detected all of my hardware out of the box, with one show-stopping exception.. the internal nvme drive is NOT visible at all. I have tried every combination of bios options imaginable, as well as multiple Ubuntu-based distros such as Kubuntu, Pop!OS and Ubuntu Studio - all with the same results: 20.04 LTS detects the internal nvme and will install, but lacks important hardware support - while 21.10 (running in live mode) is compatible with all the essential hardware out of the box, but does not "see" the internal nvme. This seems to be an emerging issue.. see: https://askubuntu.com/questions/1370379/21-10-does-not-see-windows- nvme-drive/1374079?noredirect=1#comment2364713_1374079 And the current consensus seems to be that it is a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950087/+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 1950101] [NEW] Cannot wakeup from sleep from keyboard
Public bug reported: I have always been able to wake up from sleep by pressing any key. Since a few days, I need to press the startup button of my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: izak 2934 F pulseaudio /dev/snd/pcmC1D0p: izak 2934 F...m pulseaudio /dev/snd/controlC0: izak 2934 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 20:49:07 2021 HibernationDevice: RESUME=UUID=4226b1a5-ebed-4bf9-afa2-33431caa2763 InstallationDate: Installed on 2014-10-24 (2570 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-89-generic root=/dev/mapper/ubuntu--vg-root ro acpi_enforce_resources=lax quiet splash acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-05 (367 days ago) dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- 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/1950101 Title: Cannot wakeup from sleep from keyboard Status in linux package in Ubuntu: Confirmed Bug description: I have always been able to wake up from sleep by pressing any key. Since a few days, I need to press the startup button of my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: izak 2934 F pulseaudio /dev/snd/pcmC1D0p: izak 2934 F...m pulseaudio /dev/snd/controlC0: izak 2934 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 20:49:07 2021 HibernationDevice: RESUME=UUID=4226b1a5-ebed-4bf9-afa2-33431caa2763 InstallationDate: Installed on 2014-10-24 (2570 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-89-generic root=/dev/mapper/ubuntu--vg-root ro acpi_enforce_resources=lax quiet splash acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-05 (367 days ago) dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : ht
[Kernel-packages] [Bug 1950101] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950101 Title: Cannot wakeup from sleep from keyboard Status in linux package in Ubuntu: Confirmed Bug description: I have always been able to wake up from sleep by pressing any key. Since a few days, I need to press the startup button of my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: izak 2934 F pulseaudio /dev/snd/pcmC1D0p: izak 2934 F...m pulseaudio /dev/snd/controlC0: izak 2934 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 20:49:07 2021 HibernationDevice: RESUME=UUID=4226b1a5-ebed-4bf9-afa2-33431caa2763 InstallationDate: Installed on 2014-10-24 (2570 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUS All Series ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-89-generic root=/dev/mapper/ubuntu--vg-root ro acpi_enforce_resources=lax quiet splash acpi_backlight=video vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-05 (367 days ago) dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950101/+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 1950087] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1950087 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950087 Title: ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug) Status in linux package in Ubuntu: Incomplete Bug description: I am attempting to install Ubuntu on to a new Razer Blade 15 Advanced (mid-2021) laptop. However, there seems to be some issues with kernel compatibility. When installing 20.04 LTS I have many issues with hardware not being detected (especially the intel AX210 wifi card). Running the 21.10 release from a live usb happily detected all of my hardware out of the box, with one show-stopping exception.. the internal nvme drive is NOT visible at all. I have tried every combination of bios options imaginable, as well as multiple Ubuntu-based distros such as Kubuntu, Pop!OS and Ubuntu Studio - all with the same results: 20.04 LTS detects the internal nvme and will install, but lacks important hardware support - while 21.10 (running in live mode) is compatible with all the essential hardware out of the box, but does not "see" the internal nvme. This seems to be an emerging issue.. see: https://askubuntu.com/questions/1370379/21-10-does-not-see-windows- nvme-drive/1374079?noredirect=1#comment2364713_1374079 And the current consensus seems to be that it is a kernel bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950087/+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 1950087] Re: ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug)
** Description changed: I am attempting to install Ubuntu on to a new Razer Blade 15 Advanced (mid-2021) laptop. However, there seems to be some issues with kernel compatibility. When installing 20.04 LTS I have many issues with hardware not being detected (especially the intel AX210 wifi card). Running the 21.10 release from a live usb happily detected all of my hardware out of the box, with one show-stopping exception.. the internal - nvme drive is NOT visible at all. + nvme drive is not visible at all. I have tried every combination of bios options imaginable, as well as multiple Ubuntu-based distros such as Kubuntu, Pop!OS and Ubuntu Studio - all with the same results: 20.04 LTS detects the internal nvme and will install, but lacks important hardware support - while 21.10 (running in live mode) is compatible with all the essential hardware out of the box, but does not "see" the internal nvme. + My short-term solution has been to install a 20.04 release using a wired + internet connection, followed by upgrading to 21.04. This configuration + then works, however if I upgrade again to 21.10 the internal drive again + becomes undetectable, making it impossible to boot the OS. + This seems to be an emerging issue.. see: https://askubuntu.com/questions/1370379/21-10-does-not-see-windows-nvme- drive/1374079?noredirect=1#comment2364713_1374079 - - And the current consensus seems to be that it is a kernel bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950087 Title: ubuntu 21.10 live usb does not recognize Razer Blade 15 (2021) nvme drive (possible kernel bug) Status in linux package in Ubuntu: Confirmed Bug description: I am attempting to install Ubuntu on to a new Razer Blade 15 Advanced (mid-2021) laptop. However, there seems to be some issues with kernel compatibility. When installing 20.04 LTS I have many issues with hardware not being detected (especially the intel AX210 wifi card). Running the 21.10 release from a live usb happily detected all of my hardware out of the box, with one show-stopping exception.. the internal nvme drive is not visible at all. I have tried every combination of bios options imaginable, as well as multiple Ubuntu-based distros such as Kubuntu, Pop!OS and Ubuntu Studio - all with the same results: 20.04 LTS detects the internal nvme and will install, but lacks important hardware support - while 21.10 (running in live mode) is compatible with all the essential hardware out of the box, but does not "see" the internal nvme. My short-term solution has been to install a 20.04 release using a wired internet connection, followed by upgrading to 21.04. This configuration then works, however if I upgrade again to 21.10 the internal drive again becomes undetectable, making it impossible to boot the OS. This seems to be an emerging issue.. see: https://askubuntu.com/questions/1370379/21-10-does-not-see-windows- nvme-drive/1374079?noredirect=1#comment2364713_1374079 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950087/+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 1950104] [NEW] Touchpad and WIFI randomly stop working
Public bug reported: Just based on environment it seems that the wifi is crashing and results in other Intel to crash as well. Dell 7390 XPS 13 (dev) has been fine but after changing wifi router I started noticing dropped wifi with firmware crashes in dmesg on 18.04, upgraded to 20.04, updated BIOS, updated all other firmware using firmware update manager and the wifi problem persisted, but now the touchpad has become a noticeable issue as well. One the wifi signal comes back the touchpad works again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1005-oem 5.14.0-1005.5 ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9 Uname: Linux 5.14.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 18:07:38 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-06 (702 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.14 UpgradeStatus: Upgraded to focal on 2021-04-25 (196 days ago) ** Affects: linux-signed-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950104 Title: Touchpad and WIFI randomly stop working Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: Just based on environment it seems that the wifi is crashing and results in other Intel to crash as well. Dell 7390 XPS 13 (dev) has been fine but after changing wifi router I started noticing dropped wifi with firmware crashes in dmesg on 18.04, upgraded to 20.04, updated BIOS, updated all other firmware using firmware update manager and the wifi problem persisted, but now the touchpad has become a noticeable issue as well. One the wifi signal comes back the touchpad works again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1005-oem 5.14.0-1005.5 ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9 Uname: Linux 5.14.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 18:07:38 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-06 (702 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.14 UpgradeStatus: Upgraded to focal on 2021-04-25 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1950104/+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 1950104] Re: Touchpad and WIFI randomly stop working
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1950104/+attachment/5538744/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950104 Title: Touchpad and WIFI randomly stop working Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: Just based on environment it seems that the wifi is crashing and results in other Intel to crash as well. Dell 7390 XPS 13 (dev) has been fine but after changing wifi router I started noticing dropped wifi with firmware crashes in dmesg on 18.04, upgraded to 20.04, updated BIOS, updated all other firmware using firmware update manager and the wifi problem persisted, but now the touchpad has become a noticeable issue as well. One the wifi signal comes back the touchpad works again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1005-oem 5.14.0-1005.5 ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9 Uname: Linux 5.14.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 18:07:38 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-06 (702 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.14 UpgradeStatus: Upgraded to focal on 2021-04-25 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1950104/+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 1950107] [NEW] Ubuntu MATE 20.04.3 window-list crashed
Public bug reported: I got an error pop-up about a program crashing. I did not recognize the name as pertaining to Ubuntu MATE, so I closed it. The list of windows at the bottom of the screen was blank. Google how to reset the Windows List Manager. Dic alt-cntl-F2. Then the display went black (no signal). Had to turn off (without shutting down - blank screen). Had to reboot. Tried to report bug but was told that although it is in the distro, it is not supported (like Caja). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Nov 7 21:11:20 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1950107 Title: Ubuntu MATE 20.04.3 window-list crashed Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I got an error pop-up about a program crashing. I did not recognize the name as pertaining to Ubuntu MATE, so I closed it. The list of windows at the bottom of the screen was blank. Google how to reset the Windows List Manager. Dic alt-cntl-F2. Then the display went black (no signal). Had to turn off (without shutting down - blank screen). Had to reboot. Tried to report bug but was told that although it is in the distro, it is not supported (like Caja). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Nov 7 21:11:20 2021 SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1950107/+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 1949909] Re: Bluetooth crashes on resume from suspend
Thanks but none of those crashes are related to BlueZ. And even if you did have a BlueZ crash it wouldn't cause the computer to stop responding. If you can't find any more error reports like above then please: 1. Reproduce the bug again. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Package changed: bluez (Ubuntu) => ubuntu ** Summary changed: - Bluetooth crashes on resume from suspend + Computer stops responding on resume from suspend ** Tags added: nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949909 Title: Computer stops responding on resume from suspend Status in Ubuntu: Incomplete Bug description: Crash on resume from suspend. The following messages appear and the computer stops responding: ``` [ 26.227264] Bluetooth: hci0: Reading supported features failed (-16) [ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask failed (-95) ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 22:50:23 2021 InstallationDate: Installed on 2021-09-16 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1949909/+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 1950060] [NEW] Unable to adjust screen backlight brightness on Google Pixelbook Eve
You have been subscribed to a public bug: The machine is Pixelbook 2017 Eve. OS is 21.10 fresh install and there is no way to adjust the screen backlight brightness. It is 100% all the time. IN 21.04 the solution was to add to kernel command line the i915.enable_dpcd_backlight=1 however this does not work in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 22:38:37 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 615 [8086:591e] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Google, Inc. HD Graphics 615 [1ae0:2212] InstallationDate: Installed on 2021-11-06 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 003: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:564b Realtek Semiconductor Corp. WebCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Eve ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lt_LT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dpcd_backlight=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Eve dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 31 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd08/06/2021:br4.14:efr0.0:svnGoogle:pnEve:pvr1.0:sku:rvnGoogle:rnEve:rvr1.0:cvnGoogle:ct31:cvr: dmi.product.family: Google_Eve dmi.product.name: Eve dmi.product.version: 1.0 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session -- Unable to adjust screen backlight brightness on Google Pixelbook Eve https://bugs.launchpad.net/bugs/1950060 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169
Is this landed in 5.13-OEM update? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946433 Title: Can only reach PC3 when ethernet is plugged r8169 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+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 1950060] Re: Unable to adjust screen backlight brightness on Google Pixelbook Eve
** Summary changed: - Unable to adjust screen backlight brightness + Unable to adjust screen backlight brightness on Google Pixelbook Eve ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950060 Title: Unable to adjust screen backlight brightness on Google Pixelbook Eve Status in linux package in Ubuntu: New Bug description: The machine is Pixelbook 2017 Eve. OS is 21.10 fresh install and there is no way to adjust the screen backlight brightness. It is 100% all the time. IN 21.04 the solution was to add to kernel command line the i915.enable_dpcd_backlight=1 however this does not work in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 22:38:37 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 615 [8086:591e] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Google, Inc. HD Graphics 615 [1ae0:2212] InstallationDate: Installed on 2021-11-06 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 003: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:564b Realtek Semiconductor Corp. WebCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Eve ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lt_LT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dpcd_backlight=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Eve dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 31 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd08/06/2021:br4.14:efr0.0:svnGoogle:pnEve:pvr1.0:sku:rvnGoogle:rnEve:rvr1.0:cvnGoogle:ct31:cvr: dmi.product.family: Google_Eve dmi.product.name: Eve dmi.product.version: 1.0 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950060/+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 1950060] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950060 Title: Unable to adjust screen backlight brightness on Google Pixelbook Eve Status in linux package in Ubuntu: Confirmed Bug description: The machine is Pixelbook 2017 Eve. OS is 21.10 fresh install and there is no way to adjust the screen backlight brightness. It is 100% all the time. IN 21.04 the solution was to add to kernel command line the i915.enable_dpcd_backlight=1 however this does not work in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 22:38:37 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 615 [8086:591e] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Google, Inc. HD Graphics 615 [1ae0:2212] InstallationDate: Installed on 2021-11-06 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 003: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:564b Realtek Semiconductor Corp. WebCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Eve ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lt_LT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dpcd_backlight=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Eve dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 31 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd08/06/2021:br4.14:efr0.0:svnGoogle:pnEve:pvr1.0:sku:rvnGoogle:rnEve:rvr1.0:cvnGoogle:ct31:cvr: dmi.product.family: Google_Eve dmi.product.name: Eve dmi.product.version: 1.0 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950060/+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 1919508] Re: AMDGPU lockup on every computer sleep if monitor is already asleep
Getting this with 5.13 on 21.10 with a Radeon RX 6800 XT with a AMD Ryzen 5 3600. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1919508 Title: AMDGPU lockup on every computer sleep if monitor is already asleep Status in linux-signed-oem-5.10 package in Ubuntu: Confirmed Bug description: The system always locks up, requiring a reboot. Steps to reproduce: 1. Configure power saving to turn off the monitor after a period of inactivity. 2. Configure power saving to suspend the PC automatically after a certain delay which is longer than the above one. 3. Wait. 4. The system will lock up with no way of returning to an operational state. === Hardware tested === GPU: Radeon RX 5600XT Monitor: Samsung LS24H850QFU (FreeSync enabled) Connection: DisplayPort === Previous kernels === Same issue on 5.4 and 5.8 kernels (from Ubuntu packages). === Relevant crash info === Mar 17 19:48:56 laptop kernel: [ 8692.935426] [drm] free PSP TMR buffer Mar 17 19:49:04 laptop kernel: [ 8700.925536] [drm] PCIE GART of 512M enabled (table at 0x0080). Mar 17 19:49:04 laptop kernel: [ 8700.925549] [drm] PSP is resuming... Mar 17 19:49:04 laptop kernel: [ 8701.107392] [drm] reserve 0xa0 from 0x803f40 for PSP TMR Mar 17 19:49:04 laptop kernel: [ 8701.295353] amdgpu :0a:00.0: amdgpu: RAS: optional ras ta ucode is not available Mar 17 19:49:04 laptop kernel: [ 8701.319351] amdgpu :0a:00.0: amdgpu: RAP: optional rap ta ucode is not available Mar 17 19:49:04 laptop kernel: [ 8701.319353] amdgpu :0a:00.0: amdgpu: SMU is resuming... Mar 17 19:49:04 laptop kernel: [ 8701.319358] amdgpu :0a:00.0: amdgpu: smu driver if version = 0x0036, smu fw if version = 0x0035, smu fw version = 0x002a3200 (42.50.0) Mar 17 19:49:04 laptop kernel: [ 8701.319358] amdgpu :0a:00.0: amdgpu: SMU driver if version not matched Mar 17 19:49:07 laptop kernel: [ 8703.784372] amdgpu :0a:00.0: amdgpu: failed send message: EnableAllSmuFeatures (6) param: 0x response 0xffc2 Mar 17 19:49:07 laptop kernel: [ 8703.784375] amdgpu :0a:00.0: amdgpu: Failed to enable requested dpm features! Mar 17 19:49:07 laptop kernel: [ 8703.784377] amdgpu :0a:00.0: amdgpu: Failed to setup smc hw! Mar 17 19:49:07 laptop kernel: [ 8703.784458] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -62 Mar 17 19:49:07 laptop kernel: [ 8703.784460] amdgpu :0a:00.0: amdgpu: amdgpu_device_ip_resume failed (-62). Mar 17 19:49:07 laptop kernel: [ 8703.803693] snd_hda_intel :0a:00.1: refused to change power state from D3hot to D0 Mar 17 19:49:07 laptop kernel: [ 8703.907879] snd_hda_intel :0a:00.1: CORB reset timeout#2, CORBRP = 65535 Mar 17 19:49:07 laptop kernel: [ 8703.929045] amdgpu: Move buffer fallback to memcpy unavailable Mar 17 19:49:07 laptop kernel: [ 8703.929137] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -19! Mar 17 19:49:09 laptop kernel: [ 8705.904322] amdgpu: Move buffer fallback to memcpy unavailable Mar 17 19:49:09 laptop kernel: [ 8705.904385] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -19! Mar 17 19:49:19 laptop kernel: [ 8715.651540] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=11267, emitted seq=11269 Mar 17 19:49:19 laptop kernel: [ 8715.651633] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Mar 17 19:49:19 laptop kernel: [ 8715.651638] amdgpu :0a:00.0: amdgpu: GPU reset begin! Mar 17 19:49:19 laptop kernel: [ 8715.651667] [ cut here ] Mar 17 19:49:19 laptop kernel: [ 8715.651668] kernel BUG at mm/slub.c:304! Mar 17 19:49:19 laptop kernel: [ 8715.651674] invalid opcode: [#1] SMP NOPTI Mar 17 19:49:19 laptop kernel: [ 8715.651677] CPU: 11 PID: 8470 Comm: kworker/11:1 Tainted: PW O 5.10.0-1016-oem #17-Ubuntu Mar 17 19:49:19 laptop kernel: [ 8715.651678] Hardware name: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX/B550I AORUS PRO AX, BIOS F12 01/18/2021 Mar 17 19:49:19 laptop kernel: [ 8715.651684] Workqueue: events drm_sched_job_timedout [gpu_sched] Mar 17 19:49:19 laptop kernel: [ 8715.651689] RIP: 0010:__slab_free+0x1c9/0x380 Mar 17 19:49:19 laptop kernel: [ 8715.651691] Code: 41 5e 41 5f 5d c3 41 f7 46 08 00 0d 21 00 0f 85 f0 fe ff ff 4d 85 ed 0f 85 e7 fe ff ff 80 4c 24 5b 80 45 31 c0 e9 2a ff ff ff <0f> 0b 49 3b 5c 24 28 75 97 4c 89 c0 41 89 f0 44 89 fe 49 89 4c 24 Mar 17 19:49:19 laptop kernel: [ 8715.651693] RSP: 0018:bb0cc06ffbc0 EFLAGS: 00010246 Mar 17 19:49:19 laptop kernel: [ 8715.651695] RAX: 96a256699d00 RBX: 8020001f RCX: 96a256699c00 Mar 17 19:49:19 laptop kernel: [ 8715.651697] RDX: 96a25669
[Kernel-packages] [Bug 1919508] Re: AMDGPU lockup on every computer sleep if monitor is already asleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-oem-5.10 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1919508 Title: AMDGPU lockup on every computer sleep if monitor is already asleep Status in linux-signed-oem-5.10 package in Ubuntu: Confirmed Bug description: The system always locks up, requiring a reboot. Steps to reproduce: 1. Configure power saving to turn off the monitor after a period of inactivity. 2. Configure power saving to suspend the PC automatically after a certain delay which is longer than the above one. 3. Wait. 4. The system will lock up with no way of returning to an operational state. === Hardware tested === GPU: Radeon RX 5600XT Monitor: Samsung LS24H850QFU (FreeSync enabled) Connection: DisplayPort === Previous kernels === Same issue on 5.4 and 5.8 kernels (from Ubuntu packages). === Relevant crash info === Mar 17 19:48:56 laptop kernel: [ 8692.935426] [drm] free PSP TMR buffer Mar 17 19:49:04 laptop kernel: [ 8700.925536] [drm] PCIE GART of 512M enabled (table at 0x0080). Mar 17 19:49:04 laptop kernel: [ 8700.925549] [drm] PSP is resuming... Mar 17 19:49:04 laptop kernel: [ 8701.107392] [drm] reserve 0xa0 from 0x803f40 for PSP TMR Mar 17 19:49:04 laptop kernel: [ 8701.295353] amdgpu :0a:00.0: amdgpu: RAS: optional ras ta ucode is not available Mar 17 19:49:04 laptop kernel: [ 8701.319351] amdgpu :0a:00.0: amdgpu: RAP: optional rap ta ucode is not available Mar 17 19:49:04 laptop kernel: [ 8701.319353] amdgpu :0a:00.0: amdgpu: SMU is resuming... Mar 17 19:49:04 laptop kernel: [ 8701.319358] amdgpu :0a:00.0: amdgpu: smu driver if version = 0x0036, smu fw if version = 0x0035, smu fw version = 0x002a3200 (42.50.0) Mar 17 19:49:04 laptop kernel: [ 8701.319358] amdgpu :0a:00.0: amdgpu: SMU driver if version not matched Mar 17 19:49:07 laptop kernel: [ 8703.784372] amdgpu :0a:00.0: amdgpu: failed send message: EnableAllSmuFeatures (6) param: 0x response 0xffc2 Mar 17 19:49:07 laptop kernel: [ 8703.784375] amdgpu :0a:00.0: amdgpu: Failed to enable requested dpm features! Mar 17 19:49:07 laptop kernel: [ 8703.784377] amdgpu :0a:00.0: amdgpu: Failed to setup smc hw! Mar 17 19:49:07 laptop kernel: [ 8703.784458] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -62 Mar 17 19:49:07 laptop kernel: [ 8703.784460] amdgpu :0a:00.0: amdgpu: amdgpu_device_ip_resume failed (-62). Mar 17 19:49:07 laptop kernel: [ 8703.803693] snd_hda_intel :0a:00.1: refused to change power state from D3hot to D0 Mar 17 19:49:07 laptop kernel: [ 8703.907879] snd_hda_intel :0a:00.1: CORB reset timeout#2, CORBRP = 65535 Mar 17 19:49:07 laptop kernel: [ 8703.929045] amdgpu: Move buffer fallback to memcpy unavailable Mar 17 19:49:07 laptop kernel: [ 8703.929137] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -19! Mar 17 19:49:09 laptop kernel: [ 8705.904322] amdgpu: Move buffer fallback to memcpy unavailable Mar 17 19:49:09 laptop kernel: [ 8705.904385] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the buffer list -19! Mar 17 19:49:19 laptop kernel: [ 8715.651540] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=11267, emitted seq=11269 Mar 17 19:49:19 laptop kernel: [ 8715.651633] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Mar 17 19:49:19 laptop kernel: [ 8715.651638] amdgpu :0a:00.0: amdgpu: GPU reset begin! Mar 17 19:49:19 laptop kernel: [ 8715.651667] [ cut here ] Mar 17 19:49:19 laptop kernel: [ 8715.651668] kernel BUG at mm/slub.c:304! Mar 17 19:49:19 laptop kernel: [ 8715.651674] invalid opcode: [#1] SMP NOPTI Mar 17 19:49:19 laptop kernel: [ 8715.651677] CPU: 11 PID: 8470 Comm: kworker/11:1 Tainted: PW O 5.10.0-1016-oem #17-Ubuntu Mar 17 19:49:19 laptop kernel: [ 8715.651678] Hardware name: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX/B550I AORUS PRO AX, BIOS F12 01/18/2021 Mar 17 19:49:19 laptop kernel: [ 8715.651684] Workqueue: events drm_sched_job_timedout [gpu_sched] Mar 17 19:49:19 laptop kernel: [ 8715.651689] RIP: 0010:__slab_free+0x1c9/0x380 Mar 17 19:49:19 laptop kernel: [ 8715.651691] Code: 41 5e 41 5f 5d c3 41 f7 46 08 00 0d 21 00 0f 85 f0 fe ff ff 4d 85 ed 0f 85 e7 fe ff ff 80 4c 24 5b 80 45 31 c0 e9 2a ff ff ff <0f> 0b 49 3b 5c 24 28 75 97 4c 89 c0 41 89 f0 44 89 fe 49 89 4c 24 Mar 17 19:49:19 laptop kernel: [ 8715.651693] RSP: 0018:bb0cc06ffbc0 EFLAGS: 00010246 Mar 17 19:49:19 laptop kernel: [ 8715.651695] RAX: 96a256699d00 RBX: 8020001f RCX: 96a256699c0
[Kernel-packages] [Bug 1950117] [NEW] [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi
Public bug reported: [Description] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi. Fail rate: 12 times out of 14 attempts [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository 5. apt dist-upgrade all packages and reboot [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi3 and cm3+ Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz ubuntu-21.10-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.13.0-1010.11-raspi ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1950117 Title: [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi Status in linux-raspi package in Ubuntu: New Bug description: [Description] Unable to boot rpi3b and cm3+ after upgrade to kernel 5.13.0-1010.11-raspi. Fail rate: 12 times out of 14 attempts [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository 5. apt dist-upgrade all packages and reboot [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi3 and cm3+ Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz ubuntu-21.10-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.13.0-1010.11-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950117/+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 1949278] Re: Sometimes getting console with purple text (xorg not starting)
** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Impish) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi (Ubuntu) Assignee: Juerg Haefliger (juergh) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1949278 Title: Sometimes getting console with purple text (xorg not starting) Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Impish: New Bug description: Affected HW: Raspberry Pi 4B Sometimes I'm getting console with purple text and boot freezes. Able to switch to another console (with regular white on black font) and start display manager manually. Experiencing same problem with kernels 5.13.0-1010-raspi, 5.13.0-1008-raspi, 5.11.0-1021-raspi. First time got this issue after upgrade to 21.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/controlC2', '/dev/snd/pcmC2D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.10 ImageMediaBuild: 20210421.1 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M Package: linux-meta-raspi (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:61:DD:84 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2 rootwait rootfstype=ext4 fixrtc pty.legacy_count=6 zswap.enabled=1 net.ifnames=0 ProcVersionSignature: Ubuntu 5.11.0-1021.22-raspi 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-1021-raspi N/A linux-backports-modules-5.11.0-1021-raspi N/A linux-firmware 1.201.1 StagingDrivers: bcm2835_codec vc_sm_cma snd_bcm2835 bcm2835_v4l2 bcm2835_isp bcm2835_mmal_vchiq Tags: arm64-image raspi-image impish staging Uname: Linux 5.11.0-1021-raspi aarch64 UpgradeStatus: Upgraded to impish on 2021-08-31 (60 days ago) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1949278/+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 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels (Error: Unknown device type)
Spotted in F-ibm 5.4.0-1007.8 ** Tags added: 5.4 ibm sru-20211018 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels (Error: Unknown device type) Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=2 Note, the following error has been fix in bug 1908342 Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+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
