[Kernel-packages] [Bug 1917419] Re: Can't adjust brightness on Dell Precision 7000 laptop
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917419 Title: Can't adjust brightness on Dell Precision 7000 laptop Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: [Impact] Screen brightness can't be adjusted. It can't be adjusted via Hotkey and system setting. You can see the value bar changed, but brightness didn't. [Fix] Bisect mainine kernel and found below commit in v5.12-rc1 fix the issue. f12110afee05 drm/i915/dp: Program source OUI on eDP panels [Test] Verified on Dell Precision 7000 laptop with DPCD eDP panel. [Where problems could occur] It checks the source OUI before writing it, so it won't re-program the source OUI during driver initialization. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917419/+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 1885862] Re: Add in-tree Realtek 8821CE wireless module support
SRU: * kernel: https://lists.ubuntu.com/archives/kernel-team/2021-March/117705.html (U/OEM-5.10) * firmware: https://lists.ubuntu.com/archives/kernel-team/2021-March/117709.html (F) ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => Won't Fix ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1885862 Title: Add in-tree Realtek 8821CE wireless module support Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Won't Fix Status in linux source package in Groovy: Won't Fix Status in linux-firmware source package in Groovy: Invalid Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: 8821ce is being upstreamed in https://lore.kernel.org/linux- wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce . To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1885862/+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 1917528] Re: bcmwl-kernel-source fails to build on Linux 5.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1917528 Title: bcmwl-kernel-source fails to build on Linux 5.10 Status in bcmwl package in Ubuntu: Confirmed Bug description: OS: Kubuntu 21.04 Installing bcmwl-kernel-source on Linux 5.10 kernel will fail. This didn't happen on Kubuntu 20.10. During the installation the messages are: Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.10.0-14-generic Building for architecture x86_64 Building initial module for 5.10.0-14-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.10.0-14-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: errore nell'elaborare il pacchetto bcmwl-kernel-source (--configure): il sottoprocesso installato pacchetto bcmwl-kernel-source script post-installation ha restituito lo stato di errore 10 Si sono verificati degli errori nell'elaborazione: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) Logs report: $ cat /var/crash/bcmwl-kernel-source.0.crash ProblemType: Package DKMSBuildLog: DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.10.0-14-generic (x86_64) Tue Mar 2 08:50:04 PM CET 2021 make: Entering directory '/usr/src/linux-headers-5.10.0-14-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:784:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 784 | if ((val & 0xff00) != 0) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:786:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 786 | bar1_size = pci_resource_len(pdev, 2); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] 461 | fs = get_fs(); | ^~ | get_ds /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: incompatible types when assigning to type ‘mm_segment_t’ from type ‘int’ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:2: error: implicit declaration of function ‘set_fs’; did you mean ‘sget_fc’? [-Werror=implicit-function-declaration] 462 | set_fs(get_ds()); | ^~ | sget_fc In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:26: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’? 600 | #define get_ds() (KERNEL_DS) | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: note: in expansion of macro ‘get_ds’ 462 | set_fs(get_ds()); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: note: each undeclared identifier is reported only once for each function it appears in 600 | #define get_ds() (KERNEL_DS) | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: note: in expansion of macro ‘get_ds’ 462 | set_fs(get_ds()); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:1662:6: error: implicit declaration of function ‘segment_eq’ [-Werror=implicit-function-declaration] 1662 | if (segment_eq(get_fs(), KERNEL_DS)) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:1662:17: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] 1662 | if (segment_eq(get_fs(),
[Kernel-packages] [Bug 1917709] 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/1917709 Title: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error Status in linux package in Ubuntu: Confirmed Bug description: kernel: sd 14:0:0:0: [sdd] No Caching mode page found kernel: sd 14:0:0:0: [sdd] Assuming drive cache: write through kernel: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295100, async page read kernel: Buffer I/O error on dev sr0, logical block 2295101, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179392 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179904 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9180096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295024, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180100 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295025, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295098, async page read kernel: Buffer I/O error on dev sr0, logical block 2295099, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295094, async page read kernel: Buffer I/O error on dev sr0, logical block 2295095, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179648 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294944, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179780 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294945, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295092, async page read kernel: Buffer I/O error on dev sr0, logical block 2295093, async page read systemd[1]: Failed unmounting /cdrom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.10.0-14-generic 5.10.0-14.15 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC0: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC1: ubuntu-mate 5498 F pulseaudio CasperMD5CheckResult: unknown CasperVersion: 1.458 Date: Thu Mar 4 06:07:11 2021 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hipp" - Alpha amd64 (20210304) MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications
[Kernel-packages] [Bug 1917709] [NEW] Ubuntu tries to read blu-ray when boot from ssd and gives I/O error
Public bug reported: kernel: sd 14:0:0:0: [sdd] No Caching mode page found kernel: sd 14:0:0:0: [sdd] Assuming drive cache: write through kernel: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295100, async page read kernel: Buffer I/O error on dev sr0, logical block 2295101, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179392 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179904 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9180096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295024, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180100 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295025, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295098, async page read kernel: Buffer I/O error on dev sr0, logical block 2295099, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295094, async page read kernel: Buffer I/O error on dev sr0, logical block 2295095, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179648 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294944, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179780 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294945, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295092, async page read kernel: Buffer I/O error on dev sr0, logical block 2295093, async page read systemd[1]: Failed unmounting /cdrom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.10.0-14-generic 5.10.0-14.15 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC0: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC1: ubuntu-mate 5498 F pulseaudio CasperMD5CheckResult: unknown CasperVersion: 1.458 Date: Thu Mar 4 06:07:11 2021 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hipp" - Alpha amd64 (20210304) MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Summary changed: - Ubuntu tries to read blueray when boot from ssd and gives I/O error + Ubuntu tries to read blu-ray when boot from ssd and gives I/O error ** Description changed: kernel: sd 14:0:0:0: [sdd] No Caching mode page found kernel: sd 14:0:0:0: [sdd] Assuming drive cache: write through kernel: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on
[Kernel-packages] [Bug 1913263] Re: Remove scary stack trace from Realtek WiFi driver
** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913263 Title: Remove scary stack trace from Realtek WiFi driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Won't Fix Bug description: [Impact] Scary stack trace spamming by Realtek WiFi driver. [Fix] The issue is actually harmless, so replace the WARN macro with dbg macro. [Test] No more scary stack trace in dmesg after applying the patch. [Where problems could occur] This patch doesn't bring any behavior change, so there won't be any regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1913263/+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 1906168] Re: Prevent thermal shutdown during boot process
** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1906168 Title: Prevent thermal shutdown during boot process Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Bug description: [Impact] Surprising thermal shutdown at boot on Intel based mobile workstations. [Fix] Since these thermal devcies are not in ACPI ThermalZone, OS shouldn't shutdown the system. These critial temperatures are for usespace to handle, so let kernel know it shouldn't handle it. SRU for stable kernels will be sent after the fix is in upstream. [Test] Use reboot stress as a reproducer. 5% chance to see a surprising shutdown at boot. With the fix applied, the thermal shutdown is no longer reproducible. [Where problems could occur] For ACPI based platforms, we still have "acpitz" to protect systems from overheating. If these acpitz sensors don't work, then the system could face real overheating issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906168/+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 1912676] Re: Fix regression introduced by codec PM change
** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912676 Title: Fix regression introduced by codec PM change Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Bug description: [Impact] After the codec PM optimization, laptops with SOF may take very long to suspend. In addition to that, HDA may not be able to be runtim suspended again after resume from hibernation. [Fix] Prevent the SOF driver touches codec during system suspend, and properly refcount the PM usage counter. [Test] On an affected SOF system, it takes 5 mins to suspend. On another affected HDA system, S4 resume causes high power consumption becuase HDA controller can't be runtime suspended. Both issues are gone by applying these patches. [Where problems could occur] If somehow any laptop depends on the old behavior to work properly, this can break them. It's highly unlikely though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912676/+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 1913520] Re: Restore palm ejection on multi-input devices
** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913520 Title: Restore palm ejection on multi-input devices Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Won't Fix Bug description: [Impact] Palm ejection stops working on Elan and Synaptics touchpads with pointstick. [Fix] Re-apply "confidence" quirk on those devices. [Test] Move the palm on touchpad, cursor moves too. With the fix applied, moving palm on touchpad won't move the cursor and won't generate click events. [Where problems could occur] Not that I can think of. Originally these touchpads are working fine with palm ejection, it's just overlooked when enabling pointsticks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1913520/+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 1903798] Re: Some Dell RKL AIO platform with e1000e require quirk to enter s0ix
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903798 Title: Some Dell RKL AIO platform with e1000e require quirk to enter s0ix Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Invalid Bug description: [Impact] The RKL-S system with I219LM NIC resume automatically while entering s2i. [Fix] Have to add those product sku into e1000e quirk. [Test] Verified on RKL platform with I219LM NIC [Regression Potential] Low, only affects the platforms listed in the quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1903798/+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 1916950] Re: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works
Sorry, I read that wrong. The fix is in the 5.8 HWE kernel already. ** Changed in: linux-meta-hwe-5.8 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916950 Title: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Bug description: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
[Kernel-packages] [Bug 1902672] Re: Support Advantech UNO-420 platform
** Tags removed: verification-needed-focal ** Tags added: verification-done-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/1902672 Title: Support Advantech UNO-420 platform Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] There are some drivers are required to enable Advantech UNO-420 platform. [Fix] Advantech is submitting their drivers to upstream for review, and considering that the patches are new drivers, it should be safe pull them back to ubuntu kernel. https://lkml.org/lkml/2021/1/18/500 [Test] Verified on Advantech UNO-420 platform. [Where problems could occur] Those commits create 3 new drivers, and do not modify any existing drivers. Should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902672/+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 1910113] Re: zfsutils-linux does not match kernel version
This is an issue on 20.04 with the HWE kernel too. zfs --version reports: zfs-0.8.3-1ubuntu12.6 zfs-kmod-0.8.4-1ubuntu11.1 ZFS userland not matching zfs kernel I believe is the cause of a bug I'm having with zfs send. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1910113 Title: zfsutils-linux does not match kernel version Status in zfs-linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04.5 running a "linux-image-generic-hwe-18.04 5.4.0.53.59~18.04.47" kernel. This kernel comes with ZFS 0.8.3-1ubuntu12.4. Sadly, I'm unable to use features included in zfs 0.8 release (ex. TRIM support) because zfsutils-linux is stuck on version 0.7.5-1ubuntu16.10. Can we please package zfsutils-linux that will match ZFS versions provided with hwe and hwe-edge kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1910113/+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 1910113] Re: zfsutils-linux does not match kernel version
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1910113 Title: zfsutils-linux does not match kernel version Status in zfs-linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04.5 running a "linux-image-generic-hwe-18.04 5.4.0.53.59~18.04.47" kernel. This kernel comes with ZFS 0.8.3-1ubuntu12.4. Sadly, I'm unable to use features included in zfs 0.8 release (ex. TRIM support) because zfsutils-linux is stuck on version 0.7.5-1ubuntu16.10. Can we please package zfsutils-linux that will match ZFS versions provided with hwe and hwe-edge kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1910113/+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 1916950] Re: [amdgpu] Screen fails to wake up after sleep
Aha! Yes indeed the offending commit first appeared in amdgpu_dm.c in 5.4.0-66, so reverting to 5.4.0-65 should work around the problem. ** Summary changed: - [amdgpu] Screen fails to wake up after sleep + [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works ** Tags added: regression-update ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux-meta-hwe-5.8 (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux-meta-hwe-5.8 (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1916950 Title: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd.
[Kernel-packages] [Bug 1916950] Re: [amdgpu] Screen fails to wake up after sleep
^^^ Anders, can you please try booting 5.4.0-65-generic ? -- 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/1916950 Title: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
[Kernel-packages] [Bug 1915481] Re: [nvidia] gnome crashes because Xorg crashes after running `apt upgrade`
** Summary changed: - [nvidia] gnome crashes after running `apt upgrade` + [nvidia] gnome crashes because Xorg crashes after running `apt upgrade` ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [nvidia] gnome crashes because Xorg crashes after running `apt upgrade` + [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after running `apt upgrade` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915481 Title: [nvidia] gnome crashes with Fatal IO errors (lost connection to Xorg) after running `apt upgrade` Status in gnome-shell package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
We are waiting for either: * A Mesa developer to cherry pick the fix into 20.2; or * Mesa 22.0 to reach a future version of 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1915264] Re: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Fix Released Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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: 07/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+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 1917138] Re: Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to lack of KVM patch
** Changed in: dosemu2
Status: Fix Released => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917138
Title:
Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to
lack of KVM patch
Status in Dosemu2:
New
Status in linux package in Ubuntu:
In Progress
Bug description:
[Impact]
* Since kernel 4.15.0-136, Bionic kernel included a very complex KVM fix for
a kind of "race" in interrupt window with irqchip-split (reported in [0]). The
fix was proposed in the form of a patch series containing 2 patches [1] - this
was merged in Ubuntu though the stable tree, in the form of the following
commit:
71cc849b7093 ("KVM: x86: Fix split-irqchip vs interrupt injection window
request") [2]
* The problem is that such commit has a companion required commit,
which was not proposed in the stable tree. In fact, there was a
confusion among KVM community and the stable maintainer [3], due to
the lack of such missing commit - because of that, the series was
removed from stable trees 4.14.y and 4.9.y, but the solo commit was
merged alone in Ubuntu kernel.
* Without the companion patch, we might have a KVM infinite "loop" condition
in the core IRQ handling, since the merged commit requires an extra check in
kvm_cpu_has_extint() and a condition "inversion" in kvm_cpu_get_extint(), only
present in the missing companion patch. Users reported that this manifested as
dosemu2 (running in KVM mode) to be stuck in kernel 4.15.0-136 and -137, while
works fine in 4.15.0-135 and the
-137 plus the companion patch.
* So, we hereby backport the companion commit, originally upstream
patch: 72c3bcdcda ("KVM: x86: handle !lapic_in_kernel case in
kvm_cpu_*_extint") [4]
[Test Case]
* The test case proposed was the reported bug: try running dosemu2 (with kvm
mode enabled) and it fails without the companion commit.
* In order to test the correctness of both fixes together, we could
rely in the test proposed in [0] (running a guest with "noapic"), but
it wasn't consistent and the VMM wasn't mentioned, so we might have a
workaround mechanism in qemu, for example, preventing such test to
reproduce the issue.
[Where problems could occur]
* Since this is a KVM core modification, it could affect interrupt handling
in KVM but without the fix, we are already experiencing a bug. Also, both
commits were backported to 5.4.y and 4.19.y, so Focal and subsequent released
are already running with them.
[0]
https://lore.kernel.org/kvm/62918f65ec78f8990278a6a0db0567968fa23e49.ca...@infradead.org/
[1]
https://lore.kernel.org/kvm/20201127112114.3219360-1-pbonz...@redhat.com/
[2] http://git.kernel.org/linus/71cc849b70
[3]
https://lore.kernel.org/stable/d29c4b25-33f6-8d99-7a45-8f4e06f5a...@redhat.com/
[4] http://git.kernel.org/linus/72c3bcdcda
With the latest kernel 4.15.0-136 updates on ubuntu 18.04 and ubuntu
16.04, dosemu2 with kvm freezes boot.
dosemu2 source: https://github.com/dosemu2/dosemu2
dosemu2 package can be obtained from
https://launchpad.net/~dosemu2/+archive/ubuntu/ppa
1. ubuntu version
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
2. package version
$ apt-cache policy dosemu2
dosemu2:
Installed: (none)
Candidate: (none)
Version table:
2.0~pre8-2 -1
100 /var/lib/dpkg/status
3. What is expected to happen: The dosemu program runs fine as in previous
kernel version
4. What happened instead: The dosemu freezes on loading
I have also reported this problem to dosemu2 developer, here is my bug report:
https://github.com/dosemu2/dosemu2/issues/1404
To manage notifications about this bug go to:
https://bugs.launchpad.net/dosemu2/+bug/1917138/+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 1915481] Re: [nvidia] gnome crashes after running `apt upgrade`
This is the output of journalctl -b0 > journal.txt after a recent crash of gnome-shell after I ran `sudo apt upgrade`. The problems start at roughly Mar 03 19:15:58. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+attachment/5472270/+files/journal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915481 Title: [nvidia] gnome crashes after running `apt upgrade` Status in gnome-shell package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+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 1915481] Re: [nvidia] gnome crashes after running `apt upgrade`
I just had gnome crash on me again while running `sudo apt upgrade`. Only 3 packages were updated. Here's the latest entry in /var/log/apt/history.log: Start-Date: 2021-03-03 19:16:46 Commandline: apt upgrade Requested-By: waltman (1000) Upgrade: python3-twisted:amd64 (18.9.0-11, 18.9.0-11ubuntu0.20.10.1), python3-twisted-bin:amd64 (18.9.0-11, 18.9.0-11ubuntu0.20.10.1), wpasupplicant:amd64 (2:2.9-1ubuntu8.1, 2:2.9-1ubuntu8.2) End-Date: 2021-03-03 19:17:23 And here's the latest entry in /var/log/apt/term.log: Log started: 2021-03-03 19:16:46 (Reading database ... 479992 files and directories currently installed.) Preparing to unpack .../python3-twisted-bin_18.9.0-11ubuntu0.20.10.1_amd64.deb ... Unpacking python3-twisted-bin:amd64 (18.9.0-11ubuntu0.20.10.1) over (18.9.0-11) ... Preparing to unpack .../python3-twisted_18.9.0-11ubuntu0.20.10.1_all.deb ... Unpacking python3-twisted (18.9.0-11ubuntu0.20.10.1) over (18.9.0-11) ... Preparing to unpack .../wpasupplicant_2%3a2.9-1ubuntu8.2_amd64.deb ... Unpacking wpasupplicant (2:2.9-1ubuntu8.2) over (2:2.9-1ubuntu8.1) ... Setting up python3-twisted-bin:amd64 (18.9.0-11ubuntu0.20.10.1) ... Setting up wpasupplicant (2:2.9-1ubuntu8.2) ... Setting up python3-twisted (18.9.0-11ubuntu0.20.10.1) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for dbus (1.12.20-1ubuntu1) ... Log ended: 2021-03-03 19:17:23 I'll attach the output of journalctl -b0 > journal.txt Note that the times seem a bit off to me. They seem to say I started the update at 19:16:46, but according to journal.txt I ran `apt update` at 19:15:52. I think I ran `apt upgrade` earlier than 19:16:46 because the first stack trace for gnome-shell is at 19:16:21. One other odd thing is that while I got a new gnome login prompt fairly quickly, it took me about half a dozen login attempts before I could successfully login. I didn't get any errors; rather, the screen would go blank and then I'd get the login prompt again. There was nothing new under /var/crash, nor under https://errors.ubuntu.com/user/ID. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915481 Title: [nvidia] gnome crashes after running `apt upgrade` Status in gnome-shell package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1916950] Re: [amdgpu] Screen fails to wake up after sleep
This issue is also affecting me. I booted up with kernel 5.4.0-65-generic which resolved the issue. Ubuntu 20.04.2 LTS 5.4.0-66-generic AMD Radeon RX5700XT -- 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/1916950 Title: [amdgpu] Screen fails to wake up after sleep Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in linux-meta-hwe-5.8 package in Ubuntu: Incomplete Bug description: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel:
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
The attachment "lp1879214_hirsute.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Status in makedumpfile source package in Hirsute: Confirmed Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential
[Kernel-packages] [Bug 1917679] 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/1917679 Title: dmesg trace Status in linux package in Ubuntu: Confirmed Bug description: hello, please find attached dmesg.txt [39822.436288] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-66-generic 5.4.0-66.74 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi3251 F pulseaudio /dev/snd/controlC1: imi3251 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 23:43:53 2021 InstallationDate: Installed on 2019-11-23 (466 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-w0XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/vg_af1-root ro quiet splash pcie_aspm=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-03 (273 days ago) dmi.bios.date: 05/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917679/+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 1917679] Re: dmesg trace
feel free to ask for additional files and/or commands to be ran if that can help resolving the issue. thank you in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917679 Title: dmesg trace Status in linux package in Ubuntu: Confirmed Bug description: hello, please find attached dmesg.txt [39822.436288] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-66-generic 5.4.0-66.74 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi3251 F pulseaudio /dev/snd/controlC1: imi3251 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 23:43:53 2021 InstallationDate: Installed on 2019-11-23 (466 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-w0XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/vg_af1-root ro quiet splash pcie_aspm=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-03 (273 days ago) dmi.bios.date: 05/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917679/+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 1917679] Re: dmesg trace
I experienced the machine getting unresponsive, then my network connections started to break, then I noticed I don't have the wired connection icon in the top right corner, so I decided to unplug and then replug my usb ethernet adapter -- 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/1917679 Title: dmesg trace Status in linux package in Ubuntu: Confirmed Bug description: hello, please find attached dmesg.txt [39822.436288] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-66-generic 5.4.0-66.74 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi3251 F pulseaudio /dev/snd/controlC1: imi3251 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 23:43:53 2021 InstallationDate: Installed on 2019-11-23 (466 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-w0XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/vg_af1-root ro quiet splash pcie_aspm=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-03 (273 days ago) dmi.bios.date: 05/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917679/+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 1917679] [NEW] dmesg trace
Public bug reported: hello, please find attached dmesg.txt [39822.436288] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-66-generic 5.4.0-66.74 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi3251 F pulseaudio /dev/snd/controlC1: imi3251 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 23:43:53 2021 InstallationDate: Installed on 2019-11-23 (466 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-w0XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/vg_af1-root ro quiet splash pcie_aspm=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-03 (273 days ago) dmi.bios.date: 05/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1917679/+attachment/5472245/+files/dmesg.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/1917679 Title: dmesg trace Status in linux package in Ubuntu: Confirmed Bug description: hello, please find attached dmesg.txt [39822.436288] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-66-generic 5.4.0-66.74 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi3251 F pulseaudio /dev/snd/controlC1: imi3251 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 23:43:53 2021 InstallationDate: Installed on 2019-11-23 (466 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-w0XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/vg_af1-root ro quiet splash pcie_aspm=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-03 (273 days ago) dmi.bios.date: 05/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917679/+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 1917265] Re: Suspending to RAM freezes computer
I switched to nvidia-340 driver (via "Additional Drivers"), rebooted and tested few times that suspend-resume works. -- 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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1917608] Re: Use the option the --ignore-cpuid-check for adaptive
This bug was fixed in the package thermald - 2.4.3-1 --- thermald (2.4.3-1) unstable; urgency=medium * sync with latest upstream release 2.4.3 (LP: #1917608) * debian/rules remove "HERE" debug message -- Colin King Wed, 3 Mar 2021 10:42:47 + ** Changed in: thermald (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1917608 Title: Use the option the --ignore-cpuid-check for adaptive Status in thermald package in Ubuntu: Fix Released Bug description: Currently the--ignore-cpuid-check option should work along with --adaptive option. Upstream point release 2.4.3 fixes this. commit 4a2bb6a011b010a47dea784c878cbbb2424edf83 Author: Srinivas Pandruvada Date: Tue Mar 2 13:59:00 2021 -0800 Use the option the --ignore-cpuid-check for adaptive Make --ignore-cpuid-check option to work along with --adaptive option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1917608/+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 1917194] Re: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04
Seems like everything gets locked, including the kernel. I tried connecting through SSH but it isn't answering. debug1: Connecting to ariel-nt [ariel-nt] port 22. debug1: connect to address ariel-nt port 22: No route to host ssh: connect to host ariel-nt port 22: No route to host I also tried pinging it, when it freezes it also stops answering. # Before booting >From _ icmp_seq=30 Destination Host Unreachable >From _ icmp_seq=31 Destination Host Unreachable >From _ icmp_seq=32 Destination Host Unreachable >From _ icmp_seq=33 Destination Host Unreachable >From _ icmp_seq=34 Destination Host Unreachable >From _ icmp_seq=35 Destination Host Unreachable >From _ icmp_seq=36 Destination Host Unreachable >From _ icmp_seq=37 Destination Host Unreachable >From _ icmp_seq=38 Destination Host Unreachable >From _ icmp_seq=39 Destination Host Unreachable # Connected to the internet 64 bytes from ariel-nt: icmp_seq=40 ttl=64 time=2512 ms 64 bytes from ariel-nt: icmp_seq=41 ttl=64 time=1490 ms 64 bytes from ariel-nt: icmp_seq=42 ttl=64 time=467 ms 64 bytes from ariel-nt: icmp_seq=43 ttl=64 time=33.6 ms 64 bytes from ariel-nt: icmp_seq=44 ttl=64 time=39.4 ms 64 bytes from ariel-nt: icmp_seq=45 ttl=64 time=6.22 ms 64 bytes from ariel-nt: icmp_seq=46 ttl=64 time=7.62 ms 64 bytes from ariel-nt: icmp_seq=47 ttl=64 time=6.84 ms 64 bytes from ariel-nt: icmp_seq=48 ttl=64 time=3.22 ms # Froze >From _ icmp_seq=97 Destination Host Unreachable >From _ icmp_seq=98 Destination Host Unreachable >From _ icmp_seq=99 Destination Host Unreachable >From _ icmp_seq=100 Destination Host Unreachable >From _ icmp_seq=101 Destination Host Unreachable >From _ icmp_seq=102 Destination Host Unreachable >From _ icmp_seq=103 Destination Host Unreachable >From _ icmp_seq=107 Destination Host Unreachable >From _ icmp_seq=108 Destination Host Unreachable -- 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/1917194 Title: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 18.04 to 20.04 my computer started to freeze when running lspci. I ended up noticing that it happened when trying to query device '1f:00.0' a USB port. After some kernel and bios updates the problem got worse. Now the computer freezes ~5 seconds after booting up. I tried: 1) Running in recovery mode, also freezes 2) Running an older kernel version (5.4.0-66-generic), also freezes 3) Removing nvidia drivers (just in case), also freezes 4) Running all combinations nodemodeset, acpi=off an nouveau blacklisting 5) Updating all drivers The computer freezes for ever, I can't switch TTYs, move the mouse, anything, the only way to leave was to force shutdown. On the last cases after switching to a tty I could see this messages before the freeze ocurred: kernel: xhci_hcd :1f:00.0: PCI post-resume error -19! kernel: xhci_hcd :1f:00.0: HC died; cleaning up Running Ubuntu 20.04 from a USB sticks works fine, as well as doing a fresh install. All logs were obtained by chrooting to the faulty partition from a fresh install, if there are any more logs that would be helpful, let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917194/+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 1917138] Re: Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to lack of KVM patch
Thanks a lot for the tests Bambang, and for the report! The patch was submitted
to the Ubuntu kernel ML, soon it should be applied.
Cheers,
Guilherme
--
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/1917138
Title:
Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to
lack of KVM patch
Status in Dosemu2:
Fix Released
Status in linux package in Ubuntu:
In Progress
Bug description:
[Impact]
* Since kernel 4.15.0-136, Bionic kernel included a very complex KVM fix for
a kind of "race" in interrupt window with irqchip-split (reported in [0]). The
fix was proposed in the form of a patch series containing 2 patches [1] - this
was merged in Ubuntu though the stable tree, in the form of the following
commit:
71cc849b7093 ("KVM: x86: Fix split-irqchip vs interrupt injection window
request") [2]
* The problem is that such commit has a companion required commit,
which was not proposed in the stable tree. In fact, there was a
confusion among KVM community and the stable maintainer [3], due to
the lack of such missing commit - because of that, the series was
removed from stable trees 4.14.y and 4.9.y, but the solo commit was
merged alone in Ubuntu kernel.
* Without the companion patch, we might have a KVM infinite "loop" condition
in the core IRQ handling, since the merged commit requires an extra check in
kvm_cpu_has_extint() and a condition "inversion" in kvm_cpu_get_extint(), only
present in the missing companion patch. Users reported that this manifested as
dosemu2 (running in KVM mode) to be stuck in kernel 4.15.0-136 and -137, while
works fine in 4.15.0-135 and the
-137 plus the companion patch.
* So, we hereby backport the companion commit, originally upstream
patch: 72c3bcdcda ("KVM: x86: handle !lapic_in_kernel case in
kvm_cpu_*_extint") [4]
[Test Case]
* The test case proposed was the reported bug: try running dosemu2 (with kvm
mode enabled) and it fails without the companion commit.
* In order to test the correctness of both fixes together, we could
rely in the test proposed in [0] (running a guest with "noapic"), but
it wasn't consistent and the VMM wasn't mentioned, so we might have a
workaround mechanism in qemu, for example, preventing such test to
reproduce the issue.
[Where problems could occur]
* Since this is a KVM core modification, it could affect interrupt handling
in KVM but without the fix, we are already experiencing a bug. Also, both
commits were backported to 5.4.y and 4.19.y, so Focal and subsequent released
are already running with them.
[0]
https://lore.kernel.org/kvm/62918f65ec78f8990278a6a0db0567968fa23e49.ca...@infradead.org/
[1]
https://lore.kernel.org/kvm/20201127112114.3219360-1-pbonz...@redhat.com/
[2] http://git.kernel.org/linus/71cc849b70
[3]
https://lore.kernel.org/stable/d29c4b25-33f6-8d99-7a45-8f4e06f5a...@redhat.com/
[4] http://git.kernel.org/linus/72c3bcdcda
With the latest kernel 4.15.0-136 updates on ubuntu 18.04 and ubuntu
16.04, dosemu2 with kvm freezes boot.
dosemu2 source: https://github.com/dosemu2/dosemu2
dosemu2 package can be obtained from
https://launchpad.net/~dosemu2/+archive/ubuntu/ppa
1. ubuntu version
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
2. package version
$ apt-cache policy dosemu2
dosemu2:
Installed: (none)
Candidate: (none)
Version table:
2.0~pre8-2 -1
100 /var/lib/dpkg/status
3. What is expected to happen: The dosemu program runs fine as in previous
kernel version
4. What happened instead: The dosemu freezes on loading
I have also reported this problem to dosemu2 developer, here is my bug report:
https://github.com/dosemu2/dosemu2/issues/1404
To manage notifications about this bug go to:
https://bugs.launchpad.net/dosemu2/+bug/1917138/+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 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
Debdiff for G. ** Patch added: "lp1879214_groovy.debdiff" https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5472237/+files/lp1879214_groovy.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Status in makedumpfile source package in Hirsute: Confirmed Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] For H only the 3 commits are needed and they cherry-pick. For G and F the 3rd commit does not apply and an extra commit is needed : commit da0d25ffa585c9a1adb94562c815daa393b1ee5e [PATCH] arm64: Add support for ARMv8.2-LPA (52-bit PA
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
Debdiff for F. ** Patch added: "lp1879214_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5472238/+files/lp1879214_focal.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Status in makedumpfile source package in Hirsute: Confirmed Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] For H only the 3 commits are needed and they cherry-pick. For G and F the 3rd commit does not apply and an extra commit is needed : commit da0d25ffa585c9a1adb94562c815daa393b1ee5e [PATCH] arm64: Add support for ARMv8.2-LPA (52-bit PA
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
Debdiff for H. ** Patch added: "lp1879214_hirsute.debdiff" https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5472236/+files/lp1879214_hirsute.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Status in makedumpfile source package in Hirsute: Confirmed Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] For H only the 3 commits are needed and they cherry-pick. For G and F the 3rd commit does not apply and an extra commit is needed : commit da0d25ffa585c9a1adb94562c815daa393b1ee5e [PATCH] arm64: Add support for ARMv8.2-LPA (52-bit
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
Debdiff for H. ** Description changed: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. - Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] + + For H only the 3 commits are needed and they cherry-pick. + + For G and F the 3rd commit does not apply and an extra commit is needed + : + + commit da0d25ffa585c9a1adb94562c815daa393b1ee5e + [PATCH] arm64: Add support for ARMv8.2-LPA (52-bit PA support) ** Changed in: makedumpfile (Ubuntu Groovy) Status: New => Confirmed ** Changed in: makedumpfile (Ubuntu Focal) Status: New => Confirmed ** Patch added: "lp1879214_hirsute.debdiff" https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5472235/+files/lp1879214_hirsute.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile
[Kernel-packages] [Bug 1917138] Re: Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to lack of KVM patch
** Summary changed:
- kernel 4.15.0-136 causes dosemu2 with kvm freezes
+ Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to lack
of KVM patch
** Description changed:
+ [Impact]
+ * Since kernel 4.15.0-136, Bionic kernel included a very complex KVM fix for
a kind of "race" in interrupt window with irqchip-split (reported in [0]). The
fix was proposed in the form of a patch series containing 2 patches [1] - this
was merged in Ubuntu though the stable tree, in the form of the following
commit:
+ 71cc849b7093 ("KVM: x86: Fix split-irqchip vs interrupt injection window
request") [2]
+
+ * The problem is that such commit has a companion required commit, which
+ was not proposed in the stable tree. In fact, there was a confusion
+ among KVM community and the stable maintainer [3], due to the lack of
+ such missing commit - because of that, the series was removed from
+ stable trees 4.14.y and 4.9.y, but the solo commit was merged alone in
+ Ubuntu kernel.
+
+ * Without the companion patch, we might have a KVM infinite "loop" condition
in the core IRQ handling, since the merged commit requires an extra check in
kvm_cpu_has_extint() and a condition "inversion" in kvm_cpu_get_extint(), only
present in the missing companion patch. Users reported that this manifested as
dosemu2 (running in KVM mode) to be stuck in kernel 4.15.0-136 and -137, while
works fine in 4.15.0-135 and the
+ -137 plus the companion patch.
+
+ * So, we hereby backport the companion commit, originally upstream
+ patch: 72c3bcdcda ("KVM: x86: handle !lapic_in_kernel case in
+ kvm_cpu_*_extint") [4]
+
+ [Test Case]
+ * The test case proposed was the reported bug: try running dosemu2 (with kvm
mode enabled) and it fails without the companion commit.
+
+ * In order to test the correctness of both fixes together, we could rely
+ in the test proposed in [0] (running a guest with "noapic"), but it
+ wasn't consistent and the VMM wasn't mentioned, so we might have a
+ workaround mechanism in qemu, for example, preventing such test to
+ reproduce the issue.
+
+ [Where problems could occur]
+ * Since this is a KVM core modification, it could affect interrupt handling
in KVM but without the fix, we are already experiencing a bug. Also, both
commits were backported to 5.4.y and 4.19.y, so Focal and subsequent released
are already running with them.
+
+ [0]
+
https://lore.kernel.org/kvm/62918f65ec78f8990278a6a0db0567968fa23e49.ca...@infradead.org/
+
+ [1]
+ https://lore.kernel.org/kvm/20201127112114.3219360-1-pbonz...@redhat.com/
+
+ [2] http://git.kernel.org/linus/71cc849b70
+
+ [3]
+
https://lore.kernel.org/stable/d29c4b25-33f6-8d99-7a45-8f4e06f5a...@redhat.com/
+
+ [4] http://git.kernel.org/linus/72c3bcdcda
+
+
+
+
With the latest kernel 4.15.0-136 updates on ubuntu 18.04 and ubuntu
- 16.04, dosemu2 with kvm freezes boot.
+ 16.04, dosemu2 with kvm freezes boot.
dosemu2 source: https://github.com/dosemu2/dosemu2
dosemu2 package can be obtained from
https://launchpad.net/~dosemu2/+archive/ubuntu/ppa
1. ubuntu version
lsb_release -rd
- Description: Ubuntu 18.04.5 LTS
- Release: 18.04
+ Description: Ubuntu 18.04.5 LTS
+ Release: 18.04
2. package version
$ apt-cache policy dosemu2
dosemu2:
Installed: (none)
Candidate: (none)
Version table:
2.0~pre8-2 -1
100 /var/lib/dpkg/status
3. What is expected to happen: The dosemu program runs fine as in previous
kernel version
4. What happened instead: The dosemu freezes on loading
I have also reported this problem to dosemu2 developer, here is my bug report:
https://github.com/dosemu2/dosemu2/issues/1404
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
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/1917138
Title:
Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to
lack of KVM patch
Status in Dosemu2:
Fix Released
Status in linux package in Ubuntu:
In Progress
Bug description:
[Impact]
* Since kernel 4.15.0-136, Bionic kernel included a very complex KVM fix for
a kind of "race" in interrupt window with irqchip-split (reported in [0]). The
fix was proposed in the form of a patch series containing 2 patches [1] - this
was merged in Ubuntu though the stable tree, in the form of the following
commit:
71cc849b7093 ("KVM: x86: Fix split-irqchip vs interrupt injection window
request") [2]
* The problem is that such commit has a companion required commit,
which was not proposed in the stable tree. In fact, there was a
confusion among KVM community and the stable maintainer [3], due to
the lack of such missing commit - because of that, the series was
removed from stable trees 4.14.y and 4.9.y, but the solo commit was
merged
[Kernel-packages] [Bug 1917194] Re: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04
Hi Ariel, thanks for the pictures! This is interesting, seems you're facing a USB host controller breakage, so all your USB devices are frozen. Can you try something, in order for us to be sure about that? Please, setup a SSH server [0], and after the freeze, try to connect to the machine using SSH. I'm wondering if the system is working "fine", only USB is broken. That will help us to debug. Oh, and in case you don't have multiple computers, you could use an Android/iOS ssh client to access the computer, just for the testing perspective. Thanks, Guilherme [0] https://help.ubuntu.com/community/SSH/OpenSSH/Configuring -- 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/1917194 Title: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 18.04 to 20.04 my computer started to freeze when running lspci. I ended up noticing that it happened when trying to query device '1f:00.0' a USB port. After some kernel and bios updates the problem got worse. Now the computer freezes ~5 seconds after booting up. I tried: 1) Running in recovery mode, also freezes 2) Running an older kernel version (5.4.0-66-generic), also freezes 3) Removing nvidia drivers (just in case), also freezes 4) Running all combinations nodemodeset, acpi=off an nouveau blacklisting 5) Updating all drivers The computer freezes for ever, I can't switch TTYs, move the mouse, anything, the only way to leave was to force shutdown. On the last cases after switching to a tty I could see this messages before the freeze ocurred: kernel: xhci_hcd :1f:00.0: PCI post-resume error -19! kernel: xhci_hcd :1f:00.0: HC died; cleaning up Running Ubuntu 20.04 from a USB sticks works fine, as well as doing a fresh install. All logs were obtained by chrooting to the faulty partition from a fresh install, if there are any more logs that would be helpful, let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917194/+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 1917265] Re: Suspending to RAM freezes computer
Unfortunately there is nothing relevant on logs in a first sight; your theory is interesting, is it possible for you to give a try to Nvidia drivers? At least as a data point. You could try "ubuntu-drivers devices" to show the latest nvidia driver supported by your device, and use it for a while, trying to suspend and see if it fails or not. Please, let us know the results. Cheers, Guilherme -- 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/1917265 Title: Suspending to RAM freezes computer Status in linux package in Ubuntu: Confirmed Bug description: When I try to suspend, it does not work: fans keep spinning, but just screen blanks and computer does not respond to keyboard. 'journalctl -b -1' does not tell anything suspicious after shut down - start. This used to work. Might not be reproduceable always. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarnos 1014 F pulseaudio /dev/snd/controlC2: jarnos 1014 F pulseaudio /dev/snd/controlC0: jarnos 1014 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Feb 28 23:57:02 2021 InstallationDate: Installed on 2020-05-03 (301 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917265/+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 1915332] Re: Vulkaninfo crashes on dual gpu setup
Just to update. I finally tested this with X11 and cannot reproduce the
bug there. Seems to be another issue with Nvidia and Wayland.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1915332
Title:
Vulkaninfo crashes on dual gpu setup
Status in nvidia-graphics-drivers-460 package in Ubuntu:
New
Bug description:
Hi!
First, I should mention that the driver in general works very well and
I have not encountered other problems with it.
I noticed however that vulkaninfo (from vulkan-tools) is not able to
run. I think it is either related to Wayland or my prime
configuration. I tried with both XWayland and Wayland.
```
~/dev/Vulkan-Tools/build master ❯ vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so:
wrong ELF class: ELFCLASS32
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
ERROR at
/build/vulkan-tools-A4vpMj/vulkan-tools-1.2.162.0+dfsg1/vulkaninfo/vulkaninfo.h:248:vkGetPhysicalDeviceSurfaceFormats2KHR
failed with ERROR_INITIALIZATION_FAILED
~/dev/Vulkan-Tools/build master ❯ env DISPLAY= vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so:
wrong ELF class: ELFCLASS32
'DISPLAY' environment variable not set... skipping surface info
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
fish: “env DISPLAY= vulkaninfo” terminated by signal SIGSEGV (Address
boundary error)
```
I then built vulkaninfo from source. The backtrace is not very helpful
though, it crashes somewhere inside the NVIDIA egl libraries.
```
Thread 1 "vulkaninfo" received signal SIGSEGV, Segmentation fault.
0x7fffed803d59 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
(gdb) bt
#0 0x7fffed803d59 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
#1 0x7fffed8041f0 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
#2 0x555cd723 in GetVectorInit (
func_name=0x555f55e8 "vkGetPhysicalDeviceSurfacePresentModesKHR",
f=@0x7fffcfd8: 0x77833d50 ,
init=VK_PRESENT_MODE_IMMEDIATE_KHR) at vulkaninfo/vulkaninfo.h:247
#3 0x555bcc37 in GetVector (
func_name=0x555f55e8 "vkGetPhysicalDeviceSurfacePresentModesKHR",
f=@0x7fffcfd8: 0x77833d50 )
at vulkaninfo/vulkaninfo.h:259
#4 0x555b42d5 in AppSurface::AppSurface (this=0x55ecc090,
inst=..., phys_device=0x55eca990, surface_extension=...,
sur_extension_pNextChain=std::vector of length 2, capacity 2 = {...})
at vulkaninfo/vulkaninfo.h:1217
#5 0x555abeb5 in main (argc=1, argv=0x7fffde98) at
vulkaninfo/vulkaninfo.cpp:948
```
Any idea what this could be caused by? I provide core dumps if that is
helpful.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2020-09-22 (141 days ago)
InstallationMedia:
NonfreeKernelModules: nvidia_modeset nvidia
Package: nvidia-driver-460 460.39-0ubuntu1 [origin: unknown]
PackageArchitecture: amd64
ProcEnviron:
TERM=tmux-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/usr/bin/fish
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Tags: third-party-packages hirsute wayland-session
Uname: Linux 5.10.0-14-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: bumblebee sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915332/+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 1917283] Re: "The following packages have been kept back:" bionic requesting focal downloads
I posted this bug report with features I have note here to the pulseaudio group two days ago. No response. The pulseaudio group is implicated as the source of the issue. sent to: pulseaudio-b...@lists.freedesktop.org I posted this as a kernel bug, but perhaps this is a pulseaudio problem. On latest update of kde kubuntu kernel I saw that libpulsedsp was "kept back" from updating. This remains so. The dependencies are listed as items in focal (kubuntu 20.04) however I am running bionic kubuntu 18.04. The situation cannot be resolved. I also note that the list of items (there are 8) are difficult. $ sudo apt upgrade [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libpulsedsp please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917283 $ sudo apt list -a --upgradable [sudo] password for dad: Listing... Done libpulse-dev/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 1:11.1-1ubuntu7.11] libpulse-dev/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1] libpulse-dev/bionic 1:11.1-1ubuntu7 amd64 libpulse-mainloop-glib0/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 1:11.1-1ubuntu7.11] libpulse-mainloop-glib0/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1] libpulse-mainloop-glib0/bionic 1:11.1-1ubuntu7 amd64 libpulse0/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 1:11.1-1ubuntu7.11] libpulse0/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1] libpulse0/bionic 1:11.1-1ubuntu7 amd64 libpulsedsp/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 1:11.1-1ubuntu7.11] libpulsedsp/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1] libpulsedsp/bionic 1:11.1-1ubuntu7 amd64 pulseaudio/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 1:11.1-1ubuntu7.11] pulseaudio/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1] pulseaudio/bionic 1:11.1-1ubuntu7 amd64 pulseaudio-module-jack/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 1:11.1-1ubuntu7.11] pulseaudio-module-jack/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1] pulseaudio-module-jack/bionic 1:11.1-1ubuntu7 amd64 pulseaudio-utils/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 1:11.1-1ubuntu7.11] pulseaudio-utils/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1] pulseaudio-utils/bionic 1:11.1-1ubuntu7 amd64 As is visible, I am not able to upgrade to Focal elements because I am running Bionic and I cannot upgrade Focal elements because the current upgrade tree uses Bionic ppa. If I were to put Focal ppa in my /etc/apt/sources.list there would likely be havoc! pulseaudio currently does not work so I am using alsa. I do not know how many other Focal elements will emerge even if I can resolve these, Additionally, I do not know how to fix these anyhow. Respectfully, Michael F Winthrop Member: Sterling Lions Club, VA Member: EAA Chapter 186, Manassas Apt. KHEF -- 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/1917283 Title: "The following packages have been kept back:" bionic requesting focal downloads Status in linux package in Ubuntu: Confirmed Bug description: I am happily running Bionic 18.04 Kubuntu (all previous bugs resolved). I decided to upgrade to Focal 20.04 and got a failure for an unsolvable conflict. I discovered a ppa for xenial was the cause. I removed that and then retried. (All my ppa were now for Bionic so it seemed safe) sudo do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. On "sudo apt update" I discovered that numerous pulseaudio applications and dependencies were a problem:"The following packages have been kept back:" dad@dad314159:~$ sudo apt list -a --upgradable Listing... Done libpulse-dev/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 1:11.1-1ubuntu7.11] libpulse-dev/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1] libpulse-dev/bionic 1:11.1-1ubuntu7 amd64 libpulse-mainloop-glib0/focal 1:13.99.1-1ubuntu3.7+kxstudio1 amd64 [upgradable from: 1:11.1-1ubuntu7.11] libpulse-mainloop-glib0/bionic-updates,bionic-security,now 1:11.1-1ubuntu7.11 amd64 [installed,upgradable to: 1:13.99.1-1ubuntu3.7+kxstudio1]
[Kernel-packages] [Bug 1917608] Re: Use the option the --ignore-cpuid-check for adaptive
** Changed in: thermald (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1917608 Title: Use the option the --ignore-cpuid-check for adaptive Status in thermald package in Ubuntu: Fix Committed Bug description: Currently the--ignore-cpuid-check option should work along with --adaptive option. Upstream point release 2.4.3 fixes this. commit 4a2bb6a011b010a47dea784c878cbbb2424edf83 Author: Srinivas Pandruvada Date: Tue Mar 2 13:59:00 2021 -0800 Use the option the --ignore-cpuid-check for adaptive Make --ignore-cpuid-check option to work along with --adaptive option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1917608/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
For those following along - it appears that the future of Linux audio servers will likely be PipeWire: https://lwn.net/SubscriberLink/847412/d7826b1353e33734/ -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1910907] Re: Software Installer/Updater crashes on nvidia installer: package nvidia-dkms-460 460.32.03-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-460 pack
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1910907 Title: Software Installer/Updater crashes on nvidia installer: package nvidia-dkms-460 460.32.03-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: Running Ubuntu 20.10. Opening the nvidia settings app also crashes. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-dkms-460 460.32.03-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jan 9 11:17:45 2021 ErrorMessage: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-08-29 (864 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: nvidia-graphics-drivers-460 Title: package nvidia-dkms-460 460.32.03-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1910907/+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 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
** Description changed: + [Impact] + + On arm64 and kernels 5.4+ makedumpfile fails. + + Upstream patches solve this bug : + + [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option + https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab + + [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo + https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 + + [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA + https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 + + [Test Case] + OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 - [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done + + [Regression Potential] + + Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option + removes get_elf_loads function this function was only used with --mem-usage option + , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) + the information needed is in vmcoreinfo + Any regression potential would affect the --mem-usage only + + Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo + arm64 only + make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS + does not work on Linux 5.4 and later. + Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however + this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo + and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. + + From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not + great regression potentional and if any it would only affect arm64. + + + Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA + arm64 only + Linux 5.4 and later kernels for arm64 changed the kernel VA space + arrangement and introduced 52-bit kernel VAs by merging branch + commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries + and 5.4+ kernels with best guessing. + + This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset + Any regression potential would affect only arm64 and the calculation of the above variables. + + [Other] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Focal: New Status in makedumpfile source package in Groovy: New Status in makedumpfile source package in Hirsute: Confirmed Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
[Kernel-packages] [Bug 1916950] Re: [amdgpu] Screen fails to wake up after sleep
The tty2 workaround didn't work for me. I have to do a couple of sleep/wake cycles and eventually the screen stays on. -- 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/1916950 Title: [amdgpu] Screen fails to wake up after sleep Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in linux-meta-hwe-5.8 package in Ubuntu: Incomplete Bug description: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
** Also affects: makedumpfile (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Hirsute) Importance: Undecided Assignee: Ioanna Alifieraki (joalif) Status: Confirmed ** Also affects: makedumpfile (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Focal: New Status in makedumpfile source package in Groovy: New Status in makedumpfile source package in Hirsute: Confirmed Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] To manage notifications about this bug go to:
[Kernel-packages] [Bug 1916028] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472207/+files/acpidump.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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472206/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] Re: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5
Relevant messages from dmesg: [ 7558.964284] wlp68s0b1: deauthenticating from 2c:a1:7d:d2:d7:eb by local choice (Reason: 3=DEAUTH_LEAVING) [ 7558.967915] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: disassociated [ 7558.967924] brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement) [ 7558.967926] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 7569.944159] wlp68s0b1: authenticate with 2c:a1:7d:d2:d7:eb [ 7569.944301] wlp68s0b1: send auth to 2c:a1:7d:d2:d7:eb (try 1/3) [ 7569.947116] wlp68s0b1: authenticated [ 7569.948994] wlp68s0b1: associate with 2c:a1:7d:d2:d7:eb (try 1/3) [ 7569.952839] wlp68s0b1: RX AssocResp from 2c:a1:7d:d2:d7:eb (capab=0x1411 status=0 aid=1) [ 7569.953462] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 7569.953467] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 7569.953480] wlp68s0b1: associated [ 7569.975338] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 159/256 dur 1778/1504 [ 7569.996823] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 137/256 dur 1602/1504 [ 7569.997320] IPv6: ADDRCONF(NETDEV_CHANGE): wlp68s0b1: link becomes ready [ 7571.052103] brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement) -- 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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1916028] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472205/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472203/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472204/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472198/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472202/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472200/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472196/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472197/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472189/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472201/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472199/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472195/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472194/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472193/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472190/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472192/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1916028/+attachment/5472191/+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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1916028] Re: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbojan 1017 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-18 (13 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP ProBook 6450b Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=c83c5991-d3cd-4b19-9406-46354a976ee2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.8.0-44-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: 01/11/2011 dmi.bios.release: 15.6 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CDE Ver. F.06 dmi.board.name: 146D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 73.13 dmi.chassis.asset.tag: CNU10919TZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 115.19 dmi.modalias: dmi:bvnHewlett-Packard:bvr68CDEVer.F.06:bd01/11/2011:br15.6:efr115.19:svnHewlett-Packard:pnHPProBook6450b:pvr:rvnHewlett-Packard:rn146D:rvrKBCVersion73.13:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 6450b dmi.product.sku: WD777EA#AKD dmi.sys.vendor: Hewlett-Packard ** 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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not
[Kernel-packages] [Bug 1916028] Re: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5
I'm having exactly the same problems. -- 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/1916028 Title: Problem with Wireless Network Adapter on brcmsmac driver (Broadcom BCM4313) - Ubuntu 18.04.5 Status in linux package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I want to a report errors for my hardware but I don't know if it bug or problem with the kernel itself. I installed Xubuntu 20.04.1 and I noticed when it is startup (booting) that are two information (errors?) shown of the screen. I thinked that this is only a problem with Xubuntu system but on Ubuntu 20.04.1 I had also this same informations when I run dmesg command in terminal. I installed also Ubuntu 18.04.5 but in this system I have also these errors? I think that on Ubuntu 18.04.5 I have more errors that on Ubuntu 20.04.1. This is from dmesg on Ubuntu 18.04.5 system: [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 25.402xxx] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement) [ 26.711xxx] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated [ 26.711xxx] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement) [ 13.771xxx] b43: probe of bcma0:1 failed with error -524 I erased some data with "x" because I don't know if it safe to write these kind of information public. I am beginner. One of the Launchpad user told me that this is not error. Okay but I have problem with my Wi-fi. This don't work sometimes. I found the fix. I musted to change in panel configuration of my router channels for 2.4 Ghz. It had auto option enabled. I musted limited to 3 channel because when this was high value my wi-fi doesn't work. I think that this is problem with brcmsmac driver because on bcmwl-kernel-source I don't have this problem on bionic (Ubuntu 18.04.5). I have this same problem on Ubuntu 20.04 and 20.04.1. I had also problems with bcmwl-kernel-source on Ubuntu 20.04.1 after some update but maybe this is fixed now. I don't know because I switched back to bionic. Some terminal output: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lshw -C network *-network description: Wireless interface product: BCM4313 802.11bgn Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries configuration: broadcast=yes driver=brcmsmac driverversion=5.4.0-65-generic lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 On lsusb output I can see Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR. So this is a bluetooth card. I don't know if it the same device. I think that bluetooth and wi-fi is supported by this same device but like you can see there are different names. On lspci -nnk output BCM4313 802.11bgn Wireless Network Adapter Kernel driver in use: bcma-pci-bridge Kernel modules: bcma Can you fix it? Broadcom users have a lot of problems on Ubuntu system. Maybe if you fix brcmsmac driver this will be not problem anymore. Sorry if this doubled bug, maybe someone in the past report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916028/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Hi, Last message seems to indicate that a fix is found, good news! Anything to do to get the fix? Thanks, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1894910] Re: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument
Can't be reproduced with the latest 5.8 kernel; likely fixed upstream by: https://lkml.org/lkml/2020/9/4/259 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894910 Title: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument Status in linux package in Ubuntu: Fix Released Bug description: 1) Groovy 2) root@ubuntu:/home/ubuntu# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.8.0.18.22 Candidate: 5.8.0.18.22 Version table: *** 5.8.0.18.22 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status 3) swapon --verbose /swap.img enables swap file successfully 4) swapon returns error, says swapfile has holes. Curtin creates file-based swap files with fallocate: fallocate -l XXXM /swap.img When booting Groovy (5.8 kernel), the swapfile fails to load, complains it has holes root@ubuntu:/home/ubuntu# swapon --verbose /swap.img swapon: /swap.img: found signature [pagesize=4096, signature=swap] swapon: /swap.img: pagesize=4096, swapsize=1251999744, devsize=1251999744 swapon /swap.img [ 178.283022] swapon: swapfile has holes swapon: /swap.img: swapon failed: Invalid argument root@ubuntu:/home/ubuntu# uname -r 5.8.0-18-generic This configuration works fine on Focal (5.4) and older. Previous Groovy kernels, (5.7) also worked. It may be related to: https://lkml.org/lkml/2020/9/4/259 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 8 21:38 seq crw-rw 1 root audio 116, 33 Sep 8 21:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Sep 8 21:44:13 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=UUID=ce45bbaf-5a44-4487-b89e-035c2dd40657 ro console=ttyS0 systemd.mask=snapd.seeded.service systemd.mask=snapd.service panic=-1 softlockup_panic=1 hung_task_panic=1 nmi_watchdog=panic,1 ip=:BOOTIF:dhcp RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894910/+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 1917633] [NEW] Card stuck in wrong state! card_busy_detect status: 0x700
Public bug reported: Running sdtool from https://github.com/BertoldVdb/sdtool yields: $ sudo ./sdtool /dev/mmcblk0 status [+] Found RCA for /dev/mmcblk0: . Error 110 [-] Failed to send command: Connection timed out [ 43.004983] sdhost-bcm2835 3f202000.mmc: Card stuck in wrong state! card_busy_detect status: 0x700 [ 43.102348] sdhost-bcm2835 3f202000.mmc: sdhost_busy_irq: intmask 0440 [ 53.224992] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware interrupt. [ 53.285006] sdhost-bcm2835 3f202000.mmc: __mmc_blk_ioctl_cmd: cmd error -110 [ 63.465196] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware interrupt. Tested both arm64 and armhf on 2B (armhf only), 3B, 3B+ and 4B. Focal 5.4 seems to be OK. Groovy 5.8 fails on: - 2B armhf - 3B+ armhf - 4B arm64 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Confirmed -- 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/1917633 Title: Card stuck in wrong state! card_busy_detect status: 0x700 Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Groovy: Confirmed Bug description: Running sdtool from https://github.com/BertoldVdb/sdtool yields: $ sudo ./sdtool /dev/mmcblk0 status [+] Found RCA for /dev/mmcblk0: . Error 110 [-] Failed to send command: Connection timed out [ 43.004983] sdhost-bcm2835 3f202000.mmc: Card stuck in wrong state! card_busy_detect status: 0x700 [ 43.102348] sdhost-bcm2835 3f202000.mmc: sdhost_busy_irq: intmask 0440 [ 53.224992] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware interrupt. [ 53.285006] sdhost-bcm2835 3f202000.mmc: __mmc_blk_ioctl_cmd: cmd error -110 [ 63.465196] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware interrupt. Tested both arm64 and armhf on 2B (armhf only), 3B, 3B+ and 4B. Focal 5.4 seems to be OK. Groovy 5.8 fails on: - 2B armhf - 3B+ armhf - 4B arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1917633/+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 1915185] Re: linux kernel MSI MS-7817
** Changed in: linux (Ubuntu) Assignee: (unassigned) => sessetessu2021 (sessetessu) -- 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/1915185 Title: linux kernel MSI MS-7817 Status in linux package in Ubuntu: Incomplete Bug description: linux kernel 5.8 freeze and jammed cause problems my intel graphic card Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD linux kernel 5.4 working Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD my intel graphic card is Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD linux kernels 5.8 freeze and jammed my intel graphic card Driver: Intel Open Source Technology Center Mesa DRI Intel(R) HD --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1444 F pulseaudio /dev/snd/controlC0: snowden1444 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-07 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=8603e1a2-896a-48b4-9a52-8620ce811f29 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-65-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/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1444 F pulseaudio /dev/snd/controlC0: snowden1444 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-07 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=8603e1a2-896a-48b4-9a52-8620ce811f29 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-65-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/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 1916486] Re: zfs_zrele_async can cause txg sync deadlocks
FYI, I've sponsored these and uploaded, now waiting in -proposed. I also tested these patches on and AMD64 VM using the more exhaustive kernel team ZFS tests suite and they passed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1916486 Title: zfs_zrele_async can cause txg sync deadlocks Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: In Progress Status in zfs-linux source package in Bionic: In Progress Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: In Progress Status in zfs-linux source package in Hirsute: Fix Released Status in zfs-linux package in Debian: New Bug description: [Impact] TXG sync stalls, causing ZFS workloads to hang indefinitely [Description] For certain ZFS workloads, we can see hung task timeouts in the kernel logs due to a transaction group deadlock. Userspace process will hang and display stack traces similar to the one below: [49181.619711] clnt_server D0 21699 28868 0x0320 [49181.619715] Call Trace: [49181.619725] __schedule+0x24e/0x880 [49181.619730] schedule+0x2c/0x80 [49181.619750] cv_wait_common+0x11e/0x140 [spl] [49181.619763] ? wait_woken+0x80/0x80 [49181.619775] __cv_wait+0x15/0x20 [spl] [49181.619872] zil_commit.part.14+0x80/0x8c0 [zfs] [49181.619884] ? _cond_resched+0x19/0x40 [49181.619887] ? mutex_lock+0x12/0x40 [49181.619959] zil_commit+0x17/0x20 [zfs] [49181.620026] zfs_fsync+0x77/0xe0 [zfs] [49181.620093] zpl_fsync+0x68/0xa0 [zfs] [49181.620100] vfs_fsync_range+0x51/0xb0 [49181.620105] do_fsync+0x3d/0x70 [49181.620109] SyS_fsync+0x10/0x20 [49181.620114] do_syscall_64+0x73/0x130 [49181.620119] entry_SYSCALL_64_after_hwframe+0x41/0xa6 We also might see a kworker thread blocking in the zfs writeback/evict path: [49181.881570] kworker/u17:3 D0 4915 2 0x8000 [49181.881576] Workqueue: writeback wb_workfn (flush-zfs-10) [49181.881577] Call Trace: [49181.881580] __schedule+0x24e/0x880 [49181.881582] ? atomic_t_wait+0x60/0x60 [49181.881584] schedule+0x2c/0x80 [49181.881588] bit_wait+0x11/0x60 [49181.881592] __wait_on_bit+0x4c/0x90 [49181.881596] ? atomic_t_wait+0x60/0x60 [49181.881599] __inode_wait_for_writeback+0xb9/0xf0 [49181.881601] ? bit_waitqueue+0x40/0x40 [49181.881605] inode_wait_for_writeback+0x26/0x40 [49181.881609] evict+0xb5/0x1a0 [49181.881611] iput+0x19c/0x230 [49181.881648] zfs_iput_async+0x1d/0x80 [zfs] [49181.881682] zfs_get_data+0x1d4/0x2a0 [zfs] [49181.881718] zil_commit.part.14+0x640/0x8c0 [zfs] [49181.881752] zil_commit+0x17/0x20 [zfs] [49181.881784] zpl_writepages+0xd5/0x160 [zfs] [49181.881787] do_writepages+0x4b/0xe0 [49181.881790] __writeback_single_inode+0x45/0x350 [49181.881792] ? __writeback_single_inode+0x45/0x350 [49181.881794] writeback_sb_inodes+0x1d7/0x530 [49181.881796] wb_writeback+0xfb/0x300 [49181.881799] wb_workfn+0xad/0x400 [49181.881800] ? wb_workfn+0xad/0x400 [49181.881803] ? __switch_to_asm+0x35/0x70 [49181.881809] process_one_work+0x1de/0x420 [49181.881811] worker_thread+0x32/0x410 [49181.881813] kthread+0x121/0x140 [49181.881815] ? process_one_work+0x420/0x420 [49181.881817] ? kthread_create_worker_on_cpu+0x70/0x70 [49181.881819] ret_from_fork+0x35/0x40 This is caused by a race between ZFS writeback and evict threads, usually during a transaction group sync operation. It's possible to have two iput() threads racing for the same inode: one of them scheduled async and the other executed synchronously as part of the writeback path. If the writeback thread tries to evict the inode while the async thread is running, it might re-enter the block layer for the same inode due to ZFS counters being in an inconsistent state. This then causes the kworker thread to stall the writeback, which in turn prevents the transaction group sync to complete and locks other ZFS threads. This is fixed by the upstream commit: - Fix zrele race in zrele_async that can cause hang (43eaef6de817) [0] [Test Case] Being a race condition, this issue has been hard to reproduce consistently. This has been reported on heavy I/O workloads, mixing file creation and deletion. We have some reports both from upstream and from Ubuntu users that this is usually reproducible on e.g. heavy SQL workloads or on complex ccache-enabled builds [1]. [0] https://github.com/openzfs/zfs/pull/11530 [1] https://github.com/openzfs/zfs/issues/11527 [Regression Potential] The patch has been tested in the ZFS test suite and in production environments, so the potential for further regressions should be fairly controlled. Potential regressions might arise in the ZFS writeback path, causing write hangs and eventually stalling all
[Kernel-packages] [Bug 1917284] Re: laptop E402SA document scanner linux ubuntu 20.04 LTS
** Changed in: linux (Ubuntu) Assignee: (unassigned) => sessetessu2021 (sessetessu) -- 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/1917284 Title: laptop E402SA document scanner linux ubuntu 20.04 LTS Status in linux package in Ubuntu: Incomplete Bug description: laptop E402SA document scanner dont working HP deskjet 2600 series and Canon lide 220 scanner dont working laptop E402SA linux ubuntu 20.04 LTS laptop E402SA document scanner HP deskjet and Canon lide 220 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1372 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. E402SA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=32c14ba7-6abd-49ad-b9b6-25073031646a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.8.0-44-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: 12/14/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402SA.208:bd12/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: E dmi.product.name: E402SA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917284/+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 1917421] Re: MSI MS-7817 2.3.2021 linux kernel 5.8 dont working jammed all
** Changed in: linux (Ubuntu) Assignee: (unassigned) => sessetessu2021 (sessetessu) -- 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/1917421 Title: MSI MS-7817 2.3.2021 linux kernel 5.8 dont working jammed all Status in linux package in Ubuntu: Incomplete Bug description: MSI MS-7817 2.3.2021 linux kernel 5.8 dont working jammed all trying send ubuntu launchpad bug report linux kernel 5.8 jammed bug is login me out i am removed linux kernel 5.8 MSI MS-7817 desktop is not working jammed and freeze all linux kernel 5.8 cause jammed problems i am removed because linux kernel 5.8 is not working MSI MS-7817 desktop sudo apt purge linux-generic-hwe-20.04 this kernels is working MSI MS-7817 desktop rc linux-image-5.4.0-42-generic 5.4.0-42.46 amd64Signed kernel image generic rc linux-image-5.4.0-65-generic 5.4.0-65.73 amd64Signed kernel image generic ii linux-image-5.4.0-66-generic 5.4.0-66.74 amd64Signed kernel image generic rc linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 amd64Signed kernel image generic rc linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 amd64Signed kernel image generic ii linux-image-generic5.4.0.66.69 amd64Generic Linux kernel image --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1434 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (9 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 6000 Pro MT PC Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=2a4fb579-9676-4e2a-8293-120b9188db54 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-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: 08/25/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v01.09 dmi.board.asset.tag: CZC0195QPD dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC0195QPD dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v01.09:bd08/25/2009:svnHewlett-Packard:pnHPCompaq6000ProMTPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6000 Pro MT PC dmi.product.sku: VN784ET#UUW dmi.sys.vendor: Hewlett-Packard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1386 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (9 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57de Realtek Semiconductor Corp. USB2.0 VGA UVC WebCam Bus 001 Device 003: ID 0bda:b721 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0951:16de Kingston Technology HyperX Pulsefire Core Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E402SA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=32c14ba7-6abd-49ad-b9b6-25073031646a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 Tags: focal
[Kernel-packages] [Bug 1917419] Re: Can't adjust brightness on Dell Precision 7000 laptop
** Description changed: [Impact] Screen brightness can't be adjusted. It can't be adjusted via Hotkey and system setting. You can see the value bar changed, but brightness didn't. - [Fix] + Bisect mainine kernel and found below commit in v5.12-rc1 fix the issue. + f12110afee05 drm/i915/dp: Program source OUI on eDP panels [Test] + Verified on Dell Precision 7000 laptop with DPCD eDP panel. [Where problems could occur] + It checks the source OUI before writing it, so it won't re-program the source OUI during driver initialization. -- 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/1917419 Title: Can't adjust brightness on Dell Precision 7000 laptop Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Screen brightness can't be adjusted. It can't be adjusted via Hotkey and system setting. You can see the value bar changed, but brightness didn't. [Fix] Bisect mainine kernel and found below commit in v5.12-rc1 fix the issue. f12110afee05 drm/i915/dp: Program source OUI on eDP panels [Test] Verified on Dell Precision 7000 laptop with DPCD eDP panel. [Where problems could occur] It checks the source OUI before writing it, so it won't re-program the source OUI during driver initialization. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917419/+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 1916950] Re: [amdgpu] Screen fails to wake up after sleep
I have this issue too. (@Anders Aagaard, thanks for the tty2 workaround). Distro: Ubuntu 20.04.2 LTS (Focal Fossa) Kernel: 5.4.0-66-generic x86_64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.4 wm: gnome-shell dm: GDM3 3.36.3 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] driver: amdgpu Display: server: X.Org 1.20.9 driver: amdgpu compositor: gnome-shell OpenGL: renderer: AMD Radeon RX 480 Graphics (POLARIS10 DRM 3.35.0 5.4.0-66-generic LLVM 11.0.0) v: 4.6 Mesa 20.2.6 -- 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/1916950 Title: [amdgpu] Screen fails to wake up after sleep Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in linux-meta-hwe-5.8 package in Ubuntu: Incomplete Bug description: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 version.compiz: compiz N/A version.libdrm2: libdrm2
[Kernel-packages] [Bug 1917419] Re: Can't adjust brightness on Dell Precision 7000 laptop
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/1917419 Title: Can't adjust brightness on Dell Precision 7000 laptop Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Screen brightness can't be adjusted. It can't be adjusted via Hotkey and system setting. You can see the value bar changed, but brightness didn't. [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917419/+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 1917419] Re: Can't adjust brightness on Dell Precision 7000 laptop
** Tags added: oem-priority originate-from-1911363 somerville ** Description changed: [Impact] + Screen brightness can't be adjusted. It can't be adjusted via Hotkey and system setting. You can see the value bar changed, but brightness didn't. + [Fix] [Test] [Where problems could occur] -- 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/1917419 Title: Can't adjust brightness on Dell Precision 7000 laptop Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Screen brightness can't be adjusted. It can't be adjusted via Hotkey and system setting. You can see the value bar changed, but brightness didn't. [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917419/+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 1917608] [NEW] Use the option the --ignore-cpuid-check for adaptive
Public bug reported: Currently the--ignore-cpuid-check option should work along with --adaptive option. Upstream point release 2.4.3 fixes this. commit 4a2bb6a011b010a47dea784c878cbbb2424edf83 Author: Srinivas Pandruvada Date: Tue Mar 2 13:59:00 2021 -0800 Use the option the --ignore-cpuid-check for adaptive Make --ignore-cpuid-check option to work along with --adaptive option. ** Affects: thermald (Ubuntu) Importance: High Assignee: Colin Ian King (colin-king) Status: In Progress ** Changed in: thermald (Ubuntu) Importance: Undecided => High ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: thermald (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1917608 Title: Use the option the --ignore-cpuid-check for adaptive Status in thermald package in Ubuntu: In Progress Bug description: Currently the--ignore-cpuid-check option should work along with --adaptive option. Upstream point release 2.4.3 fixes this. commit 4a2bb6a011b010a47dea784c878cbbb2424edf83 Author: Srinivas Pandruvada Date: Tue Mar 2 13:59:00 2021 -0800 Use the option the --ignore-cpuid-check for adaptive Make --ignore-cpuid-check option to work along with --adaptive option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1917608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Tue, Mar 02, 2021 at 01:40:54AM -, Helmut Stult wrote:
>Works again - have to set CONFIG_I2C_HID_ACPI=m in config
Well done!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
[Kernel-packages] [Bug 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #662 https://gitlab.freedesktop.org/drm/amd/-/issues/662 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/662 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #595 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/595 ** Also affects: gnome-settings-daemon via https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/595 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in GNOME Settings Daemon: Unknown Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1917433] Re: riscv: revert SiFive Unleashed CPUFreq
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Status: New => Triaged ** Package changed: linux (Ubuntu) => linux-riscv (Ubuntu) ** Changed in: linux-riscv (Ubuntu Groovy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917433 Title: riscv: revert SiFive Unleashed CPUFreq Status in linux-riscv package in Ubuntu: Incomplete Status in linux-riscv source package in Groovy: Fix Committed Bug description: == SRU Justifcation Groovy/RISCV == The SiFive Unleashed board with the current Ubuntu cpufreq default config can hang on boot with CPU freq enabled with the latest device tree settings. It is known that the cpufreq can be problematic so the recommended way forward is to currently revert the cpufreq enablement commit commit 3949df6ecdca04339bc8a3925c2ba7f881cf82b1 Author: David Abdurachmanov Date: Tue Jan 28 02:55:56 2020 -0800 SiFive Unleashed CPUFreq == The fix(es) == Revert commit "SiFive Unleashed CPUFreq" == Test Case == Boot with the latest DT. It should now boot. Boot without the latest DT, it should also boot. == Where problems could occur == 1. Users expecting CPU freq scaling now don't have this working option. This is deemed to be acceptable as without the fix their systems are likely to be unbootable with the updated DT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1917433/+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 1895502] Re: nouveau keeps crashing in nvkm_pmu_init
** Tags added: 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/1895502 Title: nouveau keeps crashing in nvkm_pmu_init Status in linux package in Ubuntu: Confirmed Bug description: screen brightness automatically gets full even if I reduce it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 14 09:59:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3963] Subsystem: Lenovo GP108M [GeForce MX150] [17aa:3963] InstallationDate: Installed on 2019-01-10 (612 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:241a Syntek Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=b5321cab-9053-41be-abdd-7ac822fa43b9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895502/+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 1917218] Re: X Crash appears to happen when using Zoom
*** This bug is a duplicate of bug 1895502 *** https://bugs.launchpad.net/bugs/1895502 Thanks for the bug report. I can actually see two unrelated crashes here. 1. XorgLogOld.txt is showing what looks like bug 1871959. 2. CurrentDmesg.txt is showing a kernel crash in nvkm_pmu_init [nouveau] So I'm guessing you mostly want to subscribe to bug 1871959. But I will also make this bug about the kernel crash. Although installing the official Nvidia driver via the 'Additional Drivers' app should avoid that. ** Summary changed: - X Crash appears to happen when using Zoom + [nouveau] Repeated crashes in nvkm_pmu_init ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: nouveau ** This bug has been marked a duplicate of bug 1895502 nouveau keeps crashing in nvkm_pmu_init -- 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/1917218 Title: [nouveau] Repeated crashes in nvkm_pmu_init Status in linux package in Ubuntu: New Bug description: Suddenly end up looking a black screen with number indicating that it cleared blocks. =>This *usually* happens when using Zoom screen share or watching Zoom video recording. =>Last X crash was about 5:03 am US Central Time Feb 28, 2021, approximately 90 mins ago. =>Crash frequency is about 2-4 times a week as an estimate. =>If check up time, I get the time of last system reboot (so not whole system being restarted): ==> 07:41:21 up 2 days, 10:14, 1 user, load average: 3.87, 5.35, 6.88 ==> This was probably the correct time for the last full system restart after applying OS patches =>After crash, immediately takes me to login screen for X within 10 secs (no Ubuntu boot screen) =>Initially this system was 18.04 updated regularly. It was upgraded to 20.04 (using software update process - upgraded in place) about a month ago when this restart situation started. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Feb 28 07:32:13 2021 DistUpgraded: 2021-01-17 00:24:49,141 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-65-generic, x86_64: installed evdi, 1.7.0, 5.4.0-66-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:15ae] Subsystem: ASUSTeK Computer Inc. GP108M [GeForce MX150] [1043:15ae] InstallationDate: Installed on 2018-09-09 (902 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X411UN ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=3288b326-8ac0-4e55-b66d-4b09be14341b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-01-17 (42 days ago) dmi.bios.date: 06/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X411UN.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X411UN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX411UN.307:bd06/04/2018:svnASUSTeKCOMPUTERINC.:pnX411UN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX411UN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: X411UN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
[Kernel-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-22 fixed-upstream ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' 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+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1917218] [NEW] [nouveau] Repeated crashes in nvkm_pmu_init
You have been subscribed to a public bug: Suddenly end up looking a black screen with number indicating that it cleared blocks. =>This *usually* happens when using Zoom screen share or watching Zoom video recording. =>Last X crash was about 5:03 am US Central Time Feb 28, 2021, approximately 90 mins ago. =>Crash frequency is about 2-4 times a week as an estimate. =>If check up time, I get the time of last system reboot (so not whole system being restarted): ==> 07:41:21 up 2 days, 10:14, 1 user, load average: 3.87, 5.35, 6.88 ==> This was probably the correct time for the last full system restart after applying OS patches =>After crash, immediately takes me to login screen for X within 10 secs (no Ubuntu boot screen) =>Initially this system was 18.04 updated regularly. It was upgraded to 20.04 (using software update process - upgraded in place) about a month ago when this restart situation started. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Feb 28 07:32:13 2021 DistUpgraded: 2021-01-17 00:24:49,141 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-65-generic, x86_64: installed evdi, 1.7.0, 5.4.0-66-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:15ae] Subsystem: ASUSTeK Computer Inc. GP108M [GeForce MX150] [1043:15ae] InstallationDate: Installed on 2018-09-09 (902 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X411UN ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=3288b326-8ac0-4e55-b66d-4b09be14341b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-01-17 (42 days ago) dmi.bios.date: 06/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X411UN.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X411UN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX411UN.307:bd06/04/2018:svnASUSTeKCOMPUTERINC.:pnX411UN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX411UN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: X411UN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Feb 28 05:03:27 2021 xserver.configfile: default xserver.errors: modeset(G1): glamor initialization failed modeset(G2): glamor initialization failed modeset(G3): glamor initialization failed modeset(G4): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.1 xserver.video_driver: modeset ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 focal ubuntu -- [nouveau] Repeated crashes in nvkm_pmu_init https://bugs.launchpad.net/bugs/1917218 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 1917334] Re: Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from i915_gem_object_set_tiling)
Please try some older/newer kernel versions so that we can figure out when the problem started, or if it's already been fixed... https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Summary changed: - Xorg freeze on a Dell 7240 + Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from i915_gem_object_set_tiling) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from i915_gem_object_set_tiling) + [i915] Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from i915_gem_object_set_tiling) ** Tags added: 5.8-gfx ** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (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/1917334 Title: [i915] Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from i915_gem_object_set_tiling) Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: New Dell laptop, fresh 20.04 install, 5.8.0-44-generic #50~20.04.1-Ubuntu SMP, had two xorg freezes the same day. Managed to grab dmesg from one where I got a text console: [12775.113344] BUG: unable to handle page fault for address: e6787008 [12775.113347] #PF: supervisor read access in kernel mode [12775.113347] #PF: error_code(0x) - not-present page [12775.113348] PGD 0 P4D 0 [12775.113349] Oops: [#1] SMP NOPTI [12775.113351] CPU: 0 PID: 2107 Comm: gnome-shell Tainted: G O 5.8.0-44-generic #50~20.04.1-Ubuntu [12775.113351] Hardware name: Dell Inc. Latitude 7420/095TWY, BIOS 1.3.5 01/18/2021 [12775.113355] RIP: 0010:kfree+0x55/0x250 [12775.113355] Code: 80 49 01 dc 0f 82 03 02 00 00 48 c7 c0 00 00 00 80 48 2b 05 c5 d9 1e 01 49 01 c4 49 c1 ec 0c 49 c1 e4 06 4c 03 25 a3 d9 1e 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 54 24 08 48 8d [12775.113356] RSP: 0018:a4cfc2bebcb0 EFLAGS: 00010286 [12775.113357] RAX: 6c3b8000 RBX: 0020 RCX: 93cc1c11d238 [12775.113358] RDX: 0001 RSI: 00106e56 RDI: 0020 [12775.113358] RBP: a4cfc2bebcd0 R08: 93cc5fa5f4a8 R09: 00106e77 [12775.113359] R10: R11: 0001 R12: e6787000 [12775.113359] R13: 9e345309 R14: 0002 R15: 93cb5060e800 [12775.113360] FS: 7fdebf4b9cc0() GS:93cc6f60() knlGS: [12775.113361] CS: 0010 DS: ES: CR0: 80050033 [12775.113361] CR2: e6787008 CR3: 00081c144006 CR4: 00760ef0 [12775.113362] PKRU: 5554 [12775.113362] Call Trace: [12775.113366] bitmap_free+0x9/0x10 [12775.113390] i915_gem_object_set_tiling+0x1db/0x480 [i915] [12775.113406] i915_gem_set_tiling_ioctl+0x146/0x240 [i915] [12775.113420] ? i915_gem_object_set_tiling+0x480/0x480 [i915] [12775.113429] drm_ioctl_kernel+0xae/0xf0 [drm] [12775.113431] ? ___sys_recvmsg+0x8d/0xc0 [12775.113437] drm_ioctl+0x234/0x3d0 [drm] [12775.113450] ? i915_gem_object_set_tiling+0x480/0x480 [i915] [12775.113452] ? __fget_light+0x62/0x80 [12775.113454] ? fput+0x13/0x20 [12775.113455] ? __sys_recvmsg+0x94/0xb0 [12775.113456] ksys_ioctl+0x9d/0xd0 [12775.113456] __x64_sys_ioctl+0x1a/0x20 [12775.113458] do_syscall_64+0x49/0xc0 [12775.113460] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [12775.113461] RIP: 0033:0x7fdec490d50b [12775.113462] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [12775.113462] RSP: 002b:7fff93f0ee88 EFLAGS: 0246 ORIG_RAX: 0010 [12775.113463] RAX: ffda RBX: 55f90aa9b4f0 RCX: 7fdec490d50b [12775.113464] RDX: 7fff93f0eee0 RSI: c0106461 RDI: 000d [12775.113464] RBP: 7fff93f0ef60 R08: R09: 55f90aa9bc80 [12775.113465] R10: 55f90aa97dd0 R11: 0246 R12: 55f91177efe0 [12775.113465] R13: 55f90aa9b4f0 R14: 7fff93f0eee0 R15: c0106461 [12775.113467] Modules linked in: cdc_ether usbnet r8152 mii rfcomm vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ccm cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci snd_hda_codec_hdmi snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi binfmt_misc snd_hda_codec_realtek mei_hdcp snd_hda_codec_generic dell_laptop intel_rapl_msr nls_iso8859_1 ledtrig_audio snd_soc_core x86_pkg_temp_thermal intel_powerclamp snd_compress coretemp ac97_bus snd_pcm_dmaengine snd_hda_intel kvm_intel btusb btrtl btbcm snd_intel_dspcfg btintel kvm snd_hda_codec snd_hda_core snd_hwdep bluetooth dell_wmi uvcvideo
[Kernel-packages] [Bug 1917415] Re: Xorg freeze
Thanks for the bug report. The attached files seem to show the nouveau kernel driver is crashing, so you will probably experience a freeze when that happens. This is a somewhat common problem and the best we can suggest is to use the official Nvidia driver instead. It seems driver version 340 is the correct one for your GPU so to install that you can run: sudo apt install nvidia-340 and then reboot. ** Tags added: nouveau ** Summary changed: - Xorg freeze + [nouveau] Xorg freeze ** Summary changed: - [nouveau] Xorg freeze + [nouveau] Xorg freeze and kernel crashed in nouveau_vma_del ** Package changed: xserver-xorg-video-nouveau (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/1917415 Title: [nouveau] Xorg freeze and kernel crashed in nouveau_vma_del Status in linux package in Ubuntu: Confirmed Bug description: Random freezes often using browsers like Chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 2 02:28:57 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. GT218M [GeForce 310M] [1854:0847] InstallationDate: Installed on 2021-02-28 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LG Electronics A410-K.BE47P1 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=d6b46107-6275-4957-9374-b6594451e87a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2011 dmi.bios.vendor: INSYDE dmi.bios.version: QL7L3G11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrQL7L3G11:bd05/25/2011:svnLGElectronics:pnA410-K.BE47P1:pvrTBD:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: A410-K.BE47P1 dmi.product.sku: Calpella_CRB dmi.product.version: TBD dmi.sys.vendor: LG Electronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917415/+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 1917334] [NEW] Xorg freeze on a Dell 7240 (kernel crashed in bitmap_free from i915_gem_object_set_tiling)
You have been subscribed to a public bug: New Dell laptop, fresh 20.04 install, 5.8.0-44-generic #50~20.04.1-Ubuntu SMP, had two xorg freezes the same day. Managed to grab dmesg from one where I got a text console: [12775.113344] BUG: unable to handle page fault for address: e6787008 [12775.113347] #PF: supervisor read access in kernel mode [12775.113347] #PF: error_code(0x) - not-present page [12775.113348] PGD 0 P4D 0 [12775.113349] Oops: [#1] SMP NOPTI [12775.113351] CPU: 0 PID: 2107 Comm: gnome-shell Tainted: G O 5.8.0-44-generic #50~20.04.1-Ubuntu [12775.113351] Hardware name: Dell Inc. Latitude 7420/095TWY, BIOS 1.3.5 01/18/2021 [12775.113355] RIP: 0010:kfree+0x55/0x250 [12775.113355] Code: 80 49 01 dc 0f 82 03 02 00 00 48 c7 c0 00 00 00 80 48 2b 05 c5 d9 1e 01 49 01 c4 49 c1 ec 0c 49 c1 e4 06 4c 03 25 a3 d9 1e 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 54 24 08 48 8d [12775.113356] RSP: 0018:a4cfc2bebcb0 EFLAGS: 00010286 [12775.113357] RAX: 6c3b8000 RBX: 0020 RCX: 93cc1c11d238 [12775.113358] RDX: 0001 RSI: 00106e56 RDI: 0020 [12775.113358] RBP: a4cfc2bebcd0 R08: 93cc5fa5f4a8 R09: 00106e77 [12775.113359] R10: R11: 0001 R12: e6787000 [12775.113359] R13: 9e345309 R14: 0002 R15: 93cb5060e800 [12775.113360] FS: 7fdebf4b9cc0() GS:93cc6f60() knlGS: [12775.113361] CS: 0010 DS: ES: CR0: 80050033 [12775.113361] CR2: e6787008 CR3: 00081c144006 CR4: 00760ef0 [12775.113362] PKRU: 5554 [12775.113362] Call Trace: [12775.113366] bitmap_free+0x9/0x10 [12775.113390] i915_gem_object_set_tiling+0x1db/0x480 [i915] [12775.113406] i915_gem_set_tiling_ioctl+0x146/0x240 [i915] [12775.113420] ? i915_gem_object_set_tiling+0x480/0x480 [i915] [12775.113429] drm_ioctl_kernel+0xae/0xf0 [drm] [12775.113431] ? ___sys_recvmsg+0x8d/0xc0 [12775.113437] drm_ioctl+0x234/0x3d0 [drm] [12775.113450] ? i915_gem_object_set_tiling+0x480/0x480 [i915] [12775.113452] ? __fget_light+0x62/0x80 [12775.113454] ? fput+0x13/0x20 [12775.113455] ? __sys_recvmsg+0x94/0xb0 [12775.113456] ksys_ioctl+0x9d/0xd0 [12775.113456] __x64_sys_ioctl+0x1a/0x20 [12775.113458] do_syscall_64+0x49/0xc0 [12775.113460] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [12775.113461] RIP: 0033:0x7fdec490d50b [12775.113462] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 [12775.113462] RSP: 002b:7fff93f0ee88 EFLAGS: 0246 ORIG_RAX: 0010 [12775.113463] RAX: ffda RBX: 55f90aa9b4f0 RCX: 7fdec490d50b [12775.113464] RDX: 7fff93f0eee0 RSI: c0106461 RDI: 000d [12775.113464] RBP: 7fff93f0ef60 R08: R09: 55f90aa9bc80 [12775.113465] R10: 55f90aa97dd0 R11: 0246 R12: 55f91177efe0 [12775.113465] R13: 55f90aa9b4f0 R14: 7fff93f0eee0 R15: c0106461 [12775.113467] Modules linked in: cdc_ether usbnet r8152 mii rfcomm vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ccm cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci snd_hda_codec_hdmi snd_sof_intel_byt snd_sof_intel_ipc snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_xtensa_dsp snd_sof_intel_hda snd_sof snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi binfmt_misc snd_hda_codec_realtek mei_hdcp snd_hda_codec_generic dell_laptop intel_rapl_msr nls_iso8859_1 ledtrig_audio snd_soc_core x86_pkg_temp_thermal intel_powerclamp snd_compress coretemp ac97_bus snd_pcm_dmaengine snd_hda_intel kvm_intel btusb btrtl btbcm snd_intel_dspcfg btintel kvm snd_hda_codec snd_hda_core snd_hwdep bluetooth dell_wmi uvcvideo snd_pcm iwlmvm videobuf2_vmalloc dell_smbios videobuf2_memops intel_cstate dcdbas videobuf2_v4l2 serio_raw mac80211 ecdh_generic videobuf2_common snd_seq_midi efi_pstore ecc snd_seq_midi_event joydev snd_rawmidi videodev input_leds libarc4 snd_seq mc snd_seq_device snd_timer wmi_bmof [12775.113485] dell_wmi_descriptor snd hid_sensor_gyro_3d hid_sensor_als hid_multitouch processor_thermal_device hid_sensor_accel_3d hid_sensor_trigger soundcore industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common iwlwifi industrialio ucsi_acpi intel_rapl_common mei_me typec_ucsi mei intel_soc_dts_iosf cfg80211 cros_ec_ishtp cros_ec typec int3403_thermal int340x_thermal_zone soc_button_array mac_hid intel_hid int3400_thermal acpi_thermal_rel sparse_keymap acpi_pad acpi_tad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 usbhid dm_crypt hid_sensor_custom hid_sensor_hub intel_ishtp_loader intel_ishtp_hid hid_generic rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper psmouse i2c_algo_bit rtsx_pci
[Kernel-packages] [Bug 1917415] [NEW] [nouveau] Xorg freeze and kernel crashed in nouveau_vma_del
You have been subscribed to a public bug: Random freezes often using browsers like Chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 2 02:28:57 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. GT218M [GeForce 310M] [1854:0847] InstallationDate: Installed on 2021-02-28 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LG Electronics A410-K.BE47P1 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=d6b46107-6275-4957-9374-b6594451e87a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2011 dmi.bios.vendor: INSYDE dmi.bios.version: QL7L3G11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrQL7L3G11:bd05/25/2011:svnLGElectronics:pnA410-K.BE47P1:pvrTBD:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: A410-K.BE47P1 dmi.product.sku: Calpella_CRB dmi.product.version: TBD dmi.sys.vendor: LG Electronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal freeze nouveau ubuntu -- [nouveau] Xorg freeze and kernel crashed in nouveau_vma_del https://bugs.launchpad.net/bugs/1917415 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 1916950] Re: [amdgpu] Screen fails to wake up after sleep
I was already looking at the HWE source code and the revert is not in that kernel version. -- 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/1916950 Title: [amdgpu] Screen fails to wake up after sleep Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in linux-meta-hwe-5.8 package in Ubuntu: Incomplete Bug description: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
