[Kernel-packages] [Bug 1885289] Re: zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in Bionic
** Changed in: zfs-linux (Ubuntu Bionic) Status: Confirmed => Fix Released -- 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/1885289 Title: zfs-linux 0.7.5-1ubuntu16.9 ADT test failure with 5.4 kernels in Bionic Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Bionic: Fix Released Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20200625_160936_8fbbb@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20200625_161319_b9d4a@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20200625_134053_b1336@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20200625_133912_0757e@/log.gz The dkms tests are failing for two reasons: 1. spl-linux can't be installed (see bug 1885285). 2. test kernel-smoke-test fails with the following error: autopkgtest [16:08:43]: test kernel-smoke-test: [--- kernel smoke test, create and destroy pool, 2x2 mirror: PASSED kernel smoke test, create and destroy pool, 4x1 mirror: PASSED kernel smoke test, create and destroy pool, nested raidz3: PASSED kernel smoke test, create and destroy pool, raidz1: PASSED kernel smoke test, create and destroy pool, raidz2: PASSED kernel smoke test, create and destroy pool, raidz3: PASSED kernel smoke test, create and destroy pool, striped: PASSED kernel smoke test, create and destroy ZFS Intent Log: PASSED kernel smoke test, create and destroy ZFS filesystems: PASSED kernel smoke test, ZFS snapshot: PASSED kernel smoke test, ZFS clone: PASSED kernel smoke test, ZFS send and receive: PASSED kernel smoke test, corrupt data and clean with a scrub: cannot scrub pool-smoke-6551: currently resilvering FAILED: zpool scrub failed, exit code=1 autopkgtest [16:09:24]: test kernel-smoke-test: ---] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1885289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
** Changed in: bcmwl (Ubuntu) Milestone: None => ubuntu-20.10 -- 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/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Confirmed Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
@Hui Agreed, your backport in 1.2.2 testingvis working as well as the 1.2.3 from Debian Bullseye. It definitively makes sense to submit the 1.2.2 testing to the Ubuntu packagers. Do I need to file a bug against Groovy same issue or is the 1.2.2 is automatically included in Groovy too? I'll check more in deep the crackles issue and if it's the case I'll file new bug. Thank you so much for your fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 Status in alsa-ucm-conf package in Ubuntu: Confirmed Bug description: Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-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: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
I have made sure that the kernel team is aware of this issue. We will not be able to deal with it for beta, but hopefully this will be resolved before the final release. ** Changed in: bcmwl (Ubuntu) Importance: Undecided => High -- 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/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Confirmed Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893663] Re: touchpad not detected
I can confirm this bug as well (using Linux Mint 20, Kernel 5.4.0-48-generic) with the same laptop. However, I can offer a partial workaround: After adding "i8042.nomux i8042.notimeout" to the kernel command line (i.e. via GRUB_CMDLINE_LINUX in /etc/default/grub), the trackpad will be properly recognized and shown in the dmesg output. It still won't work out of the box BUT after suspending and resuming the laptop, it basically works. Occasionally, keyboard and/or trackpad will stop working which can be fixed by a reboot. The type of trackpad seems to be an Elantech Touchpad hw version 4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893663 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Fujitsu Lifebook U7410 core7 10th generation (Model: 7U14A1) S26391-K502-V100 no information on the touchpad fresh install ubuntu 20.04LTS * touchpad is not detected * sudo lspci -vnvn > lspci-vnvn.log more lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c) Subsystem: Fujitsu Client Computing Limited Device [1e26:003f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Client Computing Limited UHD Graphics [1e26:004a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, NROPrPrP-, LTR- 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 cat /proc/version_signature > version.log more version.log Ubuntu 5.4.0-42.46-generic 5.4.44 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmadmin2348 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 16:22:12 2020 InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=4dadb030-fc54-4457-a7cd-6934b85d602c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmwa
[Kernel-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
I have the same machine (Dell XPS 13 9300), came preloaded with Ubuntu 18, then upgraded to 20.04. Running Kernel 5.4.0-48-generic #52. I have the same problem, only that nothing really helps apart from restarting until it randomly 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/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898041] [NEW] Xubuntu groovy QA-test install, strange behavior first boot
Public bug reported: Xubuntu groovy QA-test install on sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (no internet connected) ** edited ISO.qa.ubuntu report On first reboot, bootup is not as expected. First message is at least two lines, first being "System Bootloader not found. Initializing defaults\n" Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. On second boot, the "System Bootloader not found... (error continues again I'm not quick enough)" but it's NOT followed by he flashing FSCK/VAIO screen this time.. DM/greeter has appeared, HOWEVER no background logo, characters at top are just BOXES. Once I'm logged in all looks good though again??!! Third boot and different behavior again, more normal than 2nd time... but 3 boots have resulted in 3 different behaviors at the greeter/DM & not what I except from a Xubuntu install. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc 834 F pulseaudio /dev/snd/controlC1: guiverc 834 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Oct 1 22:37:33 2020 InstallationDate: Installed on 2020-10-01 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: Sony Corporation SVP11216CGB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=c10da064-d98b-4678-94af-c267fe1c3b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898041 Title: Xubuntu groovy QA-test install, strange behavior first boot Status in linux package in Ubuntu: New Bug description: Xubuntu groovy QA-test install on sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (no internet connected) ** edited ISO.qa.ubuntu report On first reboot, bootup is not as expected. First message is at least two lines, first being "System Bootloader not found. Initializing defaults\n" Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. On second boot, the "System Bootloader not found... (error continues again I'm not quick enough)" but it's NOT followed by he flashing FSCK/VAIO screen this time.. DM/greeter has appeared, HOWEVER no background logo, characters at top are just BOXES. Once I'm logged in all looks good though again??!! Third boot and different behavior again, more normal than 2nd time... but 3 boots have resulted in 3 different behaviors at the greeter/DM & not what I except from a Xubuntu install. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiver
[Kernel-packages] [Bug 1898041] Re: Xubuntu groovy QA-test install, strange behavior first boot
** Description changed: - to be filled in on real keyboard, shortly + Xubuntu groovy QA-test install on + sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) + (no internet connected) + + ** edited ISO.qa.ubuntu report + + On first reboot, bootup is not as expected. + First message is at least two lines, first being + + "System Bootloader not found. Initializing defaults\n" + + + Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. + + + This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? + + + once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. + + On second boot, the "System Bootloader not found... (error continues + again I'm not quick enough)" but it's NOT followed by he flashing + FSCK/VAIO screen this time.. + + DM/greeter has appeared, HOWEVER no background logo, characters at top + are just BOXES. Once I'm logged in all looks good though again??!! + + Third boot and different behavior again, more normal than 2nd time... + but 3 boots have resulted in 3 different behaviors at the greeter/DM & + not what I except from a Xubuntu install. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: guiverc 834 F pulseaudio - /dev/snd/controlC1: guiverc 834 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: guiverc 834 F pulseaudio + /dev/snd/controlC1: guiverc 834 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Oct 1 22:37:33 2020 InstallationDate: Installed on 2020-10-01 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: Sony Corporation SVP11216CGB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=c10da064-d98b-4678-94af-c267fe1c3b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.8.0-20-generic N/A - linux-backports-modules-5.8.0-20-generic N/A - linux-firmware1.190 + linux-restricted-modules-5.8.0-20-generic N/A + linux-backports-modules-5.8.0-20-generic N/A + linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898041 Title: Xubuntu groovy QA-test install, strange behavior first boot Status in linux package in Ubuntu: New Bug description: Xubuntu groovy QA-test install on sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (no internet connected) this contains two issues. (1) Bootloader error post-install "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." (2) Strange behavior with Xubuntu's greeter/DM login ** edited ISO.qa.ubuntu report On first reboot, bootup is not as expected. First message is at least two lines, first being "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. On second boot, the "System Bootloader not found... (error continues again I'm not quick enough)" but it's NOT followed by he flashing FSCK/VAIO screen this time.. DM/greeter has appeared, HOWEVER no backgro
[Kernel-packages] [Bug 1898041] Re: Xubuntu groovy QA-test install, strange behavior first boot
** Description changed: Xubuntu groovy QA-test install on sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (no internet connected) ** edited ISO.qa.ubuntu report On first reboot, bootup is not as expected. First message is at least two lines, first being - "System Bootloader not found. Initializing defaults\n" + "System Bootloader not found. Initializing defaults" + "Creating Boot Entry BOOT..." + Second line relates to the reconstruction of bootloader but it's too + quick for me to recall/type.. - Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. + This is followed by of flashing between FSCK like screen & VAIO logo, + many times and looks like it's having issues, or a 'fight'? - - This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? - - - once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. + once DM/greeter appears, the session is as expected. ctrl+alt+T and + terminal & all disk space utilized and system looks as expected, install + appears good now. On second boot, the "System Bootloader not found... (error continues again I'm not quick enough)" but it's NOT followed by he flashing FSCK/VAIO screen this time.. DM/greeter has appeared, HOWEVER no background logo, characters at top are just BOXES. Once I'm logged in all looks good though again??!! Third boot and different behavior again, more normal than 2nd time... but 3 boots have resulted in 3 different behaviors at the greeter/DM & not what I except from a Xubuntu install. + + Fourth boot, and back to black screen at greeter/DM, BOXES instead of + charaters again in the top panel... This issue has to be related to + Xubuntu software and not installer is my feeling + + ** Expected Results + + No ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc 834 F pulseaudio /dev/snd/controlC1: guiverc 834 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Oct 1 22:37:33 2020 InstallationDate: Installed on 2020-10-01 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: Sony Corporation SVP11216CGB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=c10da064-d98b-4678-94af-c267fe1c3b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation ** Description changed: Xubuntu groovy QA-test install on sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (no internet connected) + + this contains two issues. + + (1) Bootloader error post-install + + "System Bootloader not found. Initializing defaults" + "Creating Boot Entry BOOT..." + + (2) Strange behavior with Xubuntu's greeter/DM login + ** edited ISO.qa.ubuntu report On first reboot, bootup is not as expected. First message is at least two lines, first being "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. On second boot, the "System Bootloader not found... (error continues again I'm not quick enough)" but it's NOT followed by he flashing FSC
[Kernel-packages] [Bug 1898041] 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/1898041 Title: Xubuntu groovy QA-test install, strange behavior first boot Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu groovy QA-test install on sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (no internet connected) this contains two issues. (1) Bootloader error post-install "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." (2) Strange behavior with Xubuntu's greeter/DM login ** edited ISO.qa.ubuntu report On first reboot, bootup is not as expected. First message is at least two lines, first being "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. On second boot, the "System Bootloader not found... (error continues again I'm not quick enough)" but it's NOT followed by he flashing FSCK/VAIO screen this time.. DM/greeter has appeared, HOWEVER no background logo, characters at top are just BOXES. Once I'm logged in all looks good though again??!! Third boot and different behavior again, more normal than 2nd time... but 3 boots have resulted in 3 different behaviors at the greeter/DM & not what I except from a Xubuntu install. Fourth boot, and back to black screen at greeter/DM, BOXES instead of charaters again in the top panel... This issue has to be related to Xubuntu software and not installer is my feeling ** Expected Results (1) No boot loader error messages are expected (2) Consistent greeter, with background, and letters in the top panel (not boxes). Once logged in session is good, this is a Xubuntu issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc 834 F pulseaudio /dev/snd/controlC1: guiverc 834 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Oct 1 22:37:33 2020 InstallationDate: Installed on 2020-10-01 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: Sony Corporation SVP11216CGB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=c10da064-d98b-4678-94af-c267fe1c3b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898041] Re: Xubuntu groovy QA-test install, strange behavior first boot
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1898041 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898041 Title: Xubuntu groovy QA-test install, strange behavior first boot Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu groovy QA-test install on sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (no internet connected) this contains two issues. (1) Bootloader error post-install "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." (2) Strange behavior with Xubuntu's greeter/DM login ** edited ISO.qa.ubuntu report On first reboot, bootup is not as expected. First message is at least two lines, first being "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. On second boot, the "System Bootloader not found... (error continues again I'm not quick enough)" but it's NOT followed by he flashing FSCK/VAIO screen this time.. DM/greeter has appeared, HOWEVER no background logo, characters at top are just BOXES. Once I'm logged in all looks good though again??!! Third boot and different behavior again, more normal than 2nd time... but 3 boots have resulted in 3 different behaviors at the greeter/DM & not what I except from a Xubuntu install. Fourth boot, and back to black screen at greeter/DM, BOXES instead of charaters again in the top panel... This issue has to be related to Xubuntu software and not installer is my feeling ** Expected Results (1) No boot loader error messages are expected (2) Consistent greeter, with background, and letters in the top panel (not boxes). Once logged in session is good, this is a Xubuntu issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc 834 F pulseaudio /dev/snd/controlC1: guiverc 834 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Oct 1 22:37:33 2020 InstallationDate: Installed on 2020-10-01 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: Sony Corporation SVP11216CGB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=c10da064-d98b-4678-94af-c267fe1c3b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898041] Re: Xubuntu groovy QA-test install, strange behavior first boot
This bug is consequence of tested related to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991 (refer comment #7 which refers to this install) This install however had what I considered a different issue "System Bootloader not found. Initializing defaults\n..." which is filed here I also clouded this bug report/issue by including two issues. I filed against linux/kernel as I couldn't decide on package; & kernel sure is wrong. If the bootloader is related to 1897991, it should be removed from this report & package changed to xubuntu-desktop|meta -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898041 Title: Xubuntu groovy QA-test install, strange behavior first boot Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu groovy QA-test install on sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (no internet connected) this contains two issues. (1) Bootloader error post-install "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." (2) Strange behavior with Xubuntu's greeter/DM login ** edited ISO.qa.ubuntu report On first reboot, bootup is not as expected. First message is at least two lines, first being "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. On second boot, the "System Bootloader not found... (error continues again I'm not quick enough)" but it's NOT followed by he flashing FSCK/VAIO screen this time.. DM/greeter has appeared, HOWEVER no background logo, characters at top are just BOXES. Once I'm logged in all looks good though again??!! Third boot and different behavior again, more normal than 2nd time... but 3 boots have resulted in 3 different behaviors at the greeter/DM & not what I except from a Xubuntu install. Fourth boot, and back to black screen at greeter/DM, BOXES instead of charaters again in the top panel... This issue has to be related to Xubuntu software and not installer is my feeling ** Expected Results (1) No boot loader error messages are expected (2) Consistent greeter, with background, and letters in the top panel (not boxes). Once logged in session is good, this is a Xubuntu issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc 834 F pulseaudio /dev/snd/controlC1: guiverc 834 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Oct 1 22:37:33 2020 InstallationDate: Installed on 2020-10-01 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: Sony Corporation SVP11216CGB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=c10da064-d98b-4678-94af-c267fe1c3b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Comment bridged from LTC Bugzilla
--- Comment From mihaj...@de.ibm.com 2020-10-01 09:43 EDT--- Took me a bit longer than expected, as I ran into some other unrelated issue. Unfortunately I was not successful. What I did on a pristine Ubuntu 20.04.1 install with a luks-encrypted setup was: $ add-apt-repository ppa:cascardo/kdump2 $ apt update $ apt install kexec-tools $ apt install kdump-tools The initrd was rebuild and the zipl was run, however zipl.conf wasn't updated with a new crashkernel value and after rebooting it was still the old value of 196 in the kernel command line. Here's the output of dpkg -l for kexec-tools and kdump-tools ii kexec-tools1:2.0.18-1ubuntu1 s390xtools to support fast kexec r ii kdump-tools1:1.6.7-4ubuntu1+cascardo2 s390xscripts and tools fo Here's my cryptab content: vda6_crypt UUID=3b1c23fa-0cc4-4ba1-b47e-974f79db1b5c none luks,discard fstab: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # /dev/mapper/vgubuntu-root / ext4errors=remount-ro 0 1 # /boot was on /dev/vda5 during installation UUID=44950dee-686a-4946-b64e-8b54976d254a /boot ext4defaults 0 2 /dev/mapper/vgubuntu-swap_1 noneswapsw 0 0 lsblk output: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:006G 0 disk ??vda1252:10 512M 0 part ??vda2252:201K 0 part ??vda5252:50 731M 0 part /boot ??vda6252:60 4.8G 0 part ??vda6_crypt253:00 4.8G 0 crypt ??vgubuntu-root 253:10 3.8G 0 lvm / ??vgubuntu-swap_1 253:20 976M 0 lvm [SWAP] Maybe I did something wrong. Let me know. -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897942] Re: crash on brcmfmac
this brcmfmac is in linux-firmware and not in linux-raspi ** Package changed: linux-raspi (Ubuntu) => linux-firmware (Ubuntu) -- 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/1897942 Title: crash on brcmfmac Status in linux-firmware package in Ubuntu: New Bug description: I have Ubuntu 20.04 64bit, ubuntu desktop, network-manager on RPI4 8GB wifi work well for some time but then all gone very slow and system is unusable. to me it seems a brcmfmac module problem. My power configuration do not go well if switch off "wi-fi can be turn off to power save": all wifi crash. Rest of my power conf: automatic suspend = no action on turn off supply button = nothing black screen = never To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1897942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898041] Re: Xubuntu groovy QA-test install, strange behavior first (& subsequent) boot(s)
** Summary changed: - Xubuntu groovy QA-test install, strange behavior first boot + Xubuntu groovy QA-test install, strange behavior first (& subsequent) boot(s) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898041 Title: Xubuntu groovy QA-test install, strange behavior first (& subsequent) boot(s) Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu groovy QA-test install on sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (no internet connected) this contains two issues. (1) Bootloader error post-install "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." (2) Strange behavior with Xubuntu's greeter/DM login ** edited ISO.qa.ubuntu report On first reboot, bootup is not as expected. First message is at least two lines, first being "System Bootloader not found. Initializing defaults" "Creating Boot Entry BOOT..." Second line relates to the reconstruction of bootloader but it's too quick for me to recall/type.. This is followed by of flashing between FSCK like screen & VAIO logo, many times and looks like it's having issues, or a 'fight'? once DM/greeter appears, the session is as expected. ctrl+alt+T and terminal & all disk space utilized and system looks as expected, install appears good now. On second boot, the "System Bootloader not found... (error continues again I'm not quick enough)" but it's NOT followed by he flashing FSCK/VAIO screen this time.. DM/greeter has appeared, HOWEVER no background logo, characters at top are just BOXES. Once I'm logged in all looks good though again??!! Third boot and different behavior again, more normal than 2nd time... but 3 boots have resulted in 3 different behaviors at the greeter/DM & not what I except from a Xubuntu install. Fourth boot, and back to black screen at greeter/DM, BOXES instead of charaters again in the top panel... This issue has to be related to Xubuntu software and not installer is my feeling ** Expected Results (1) No boot loader error messages are expected (2) Consistent greeter, with background, and letters in the top panel (not boxes). Once logged in session is good, this is a Xubuntu issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-20-generic 5.8.0-20.21 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc 834 F pulseaudio /dev/snd/controlC1: guiverc 834 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Oct 1 22:37:33 2020 InstallationDate: Installed on 2020-10-01 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: Sony Corporation SVP11216CGB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=c10da064-d98b-4678-94af-c267fe1c3b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898057] [NEW] Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4
You have been subscribed to a public bug: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] __do_softirq+0xe4/0x2da kernel: [52642.480278] irq_exit+0xae/0xb0 kernel: [52642.480282] smp_apic_timer_interrupt+0x79/0x130 kernel: [52642.480285] apic_timer_interrupt+0xf/0x20 kernel: [52642.480286] kernel: [52642.480292] RIP: 0010:cpuidle_enter_state+0xbc/0x440 kernel: [52642.480294] Code: ff e8 98 f6 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 2b 74 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Any information needed about my configuration or some log? -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I can confirm this behavior with by JBL TUNE750TNC. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898057] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416153/+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/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] __d
[Kernel-packages] [Bug 1898057] Re: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4
apport information ** Package changed: linux-hwe-5.4 (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected bionic ** Description changed: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] __do_softirq+0xe4/0x2da kernel: [52642.480278] irq_exit+0xae/0xb0 kernel: [52642.480282] smp_apic_timer_interrupt+0x79/0x130 kernel: [52642.480285] apic_timer_interrupt+0xf/0x20 kernel: [52642.480286] kernel: [52642.480292] RIP: 0010:cpuidle_enter_state+0xbc/0x440 kernel
[Kernel-packages] [Bug 1898057] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416155/+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/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642
[Kernel-packages] [Bug 1898057] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416156/+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/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel:
[Kernel-packages] [Bug 1898057] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416151/+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/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [526
[Kernel-packages] [Bug 1898057] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416158/+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/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] _
[Kernel-packages] [Bug 1898057] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416154/+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/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30
[Kernel-packages] [Bug 1898057] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416157/+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/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642
[Kernel-packages] [Bug 1898057] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416159/+files/WifiSyslog.txt ** Description changed: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] - Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] - Kernel driver in use: mlx4_core + Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] + Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] __do_softirq+0xe4/0x2da kernel: [52642.480278] irq_exit+0xae/0xb0 kernel: [52642.480282] smp_apic_timer_interrupt+0x79/0x130 kernel
[Kernel-packages] [Bug 1898057] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1898057/+attachment/5416152/+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/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] __d
[Kernel-packages] [Bug 1898057] Re: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4
** 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/1898057 Title: Infiniband transmit queue timeouts after upgrading to linux-hwe-5.4 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading 3 servers from linux-image-5.3.0-40-generic to linux- image-5.4.0-48-generic I have started seeing the following queue timeouts from IP-over-Infiniband (ipoib) devices. The devices in question are (with newest available firmware, 2.42.5000): # lspci -nnk -s 83:00.0 83:00.0 Network controller [0280]: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:1003] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] [15b3:0027] Kernel driver in use: mlx4_core Below is the WARN from one machine's syslog. The others are practically identical. When the WARN happens on any of the machines, other 2 will _also_ exhibit queue timeouts. Additionally, other (unrelated) machines connected to the same infiniband fabric will exhibit a 12-second transmission delay. This could conceivably be caused by these 3 servers also being Subnet Managers (opensm package). The infiniband fabric is partitioned, with the affected partition (8011) seeing most of the traffic. kernel: [52642.480066] [ cut here ] kernel: [52642.480092] NETDEV WATCHDOG: ib0.8011 (): transmit queue 0 timed out kernel: [52642.480120] WARNING: CPU: 13 PID: 0 at /build/linux-hwe-5.4-8m2I8l/linux-hwe-5.4-5.4.0/net/sched/sch_generic.c:448 dev_watchdog+0x264/0x270 kernel: [52642.480121] Modules linked in: aufs overlay ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_tables nfnetlink cfg80211 ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter mst_pciconf(OE) mst_pci(OE) 8021q garp mrp stp llc nls_iso8859_1 intel_rapl_msr lz4 lz4_compress intel_rapl_common ib_iser rdma_cm sb_edac iw_cm iscsi_tcp libiscsi_tcp libiscsi x86_pkg_temp_thermal scsi_transport_iscsi intel_powerclamp zram veth vhost_net tap coretemp vhost kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel kvm openvswitch nsh nf_conncount nf_nat nf_conntrack rapl nf_defrag_ipv6 nf_defrag_ipv4 joydev input_leds intel_cstate ib_ipoib mei_me mei ib_cm ioatdma ib_umad lpc_ich acpi_pad acpi_power_meter mac_hid ipmi_si ipmi_ssif ipmi_devintf ipmi_msghandler kyber_iosched sch_fq_codel tcp_highspeed ip_tables x_tables autofs4 zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) zlua(POE) btrfs zstd_compress raid10 raid456 kernel: [52642.480182] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear dm_mirror dm_region_hash dm_log mlx4_ib ib_uverbs ib_core hid_generic raid1 ses enclosure usbhid hid ast drm_vram_helper i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops ixgbe glue_helper mpt3sas nvme xfrm_algo crypto_simd ahci raid_class dca cryptd mlx4_core drm megaraid_sas nvme_core libahci scsi_transport_sas mdio wmi kernel: [52642.480221] CPU: 13 PID: 0 Comm: swapper/13 Tainted: P OE 5.4.0-48-generic #52~18.04.1-Ubuntu kernel: [52642.480223] Hardware name: Supermicro Super Server/X10DRW-iT, BIOS 2.0b 04/13/2017 kernel: [52642.480226] RIP: 0010:dev_watchdog+0x264/0x270 kernel: [52642.480229] Code: 48 85 c0 75 e6 eb a0 4c 89 ef c6 05 42 c1 e7 00 01 e8 30 b8 fa ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 50 05 63 ae e8 4c 31 71 ff <0f> 0b eb 82 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 kernel: [52642.480230] RSP: 0018:b4998c970e48 EFLAGS: 00010282 kernel: [52642.480233] RAX: RBX: RCX: 083f kernel: [52642.480234] RDX: RSI: 00f6 RDI: 083f kernel: [52642.480235] RBP: b4998c970e78 R08: 08fd R09: 0003 kernel: [52642.480237] R10: b4998c970ee8 R11: 0001 R12: 0001 kernel: [52642.480238] R13: 93d302465000 R14: 93d302465480 R15: 93f2d293c880 kernel: [52642.480240] FS: () GS:93f33f64() knlGS: kernel: [52642.480242] CS: 0010 DS: ES: CR0: 80050033 kernel: [52642.480243] CR2: f90140127000 CR3: 002a26e0a004 CR4: 001626e0 kernel: [52642.480245] Call Trace: kernel: [52642.480247] kernel: [52642.480252] ? pfifo_fast_reset+0x110/0x110 kernel: [52642.480255] call_timer_fn+0x32/0x130 kernel: [52642.480258] run_timer_softirq+0x443/0x480 kernel: [52642.480262] ? ktime_get+0x43/0xa0 kernel: [52642.480268] ? lapic_next_deadline+0x26/0x30 kernel: [52642.480273] __do_softirq+0xe4/0x2da kernel: [52642.480278] irq_exit+0xae/0xb0 ker
[Kernel-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
I have the same problem. On wired connection it constantly disconnects and connects. I am running Ubuntu VM inside vmware with NAT network adapter setting. It had been stable for a long time, but this last week has been incredible horrible. Linux ubuntu 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in linux package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 pr500k-9912ec-1 36301ded-0ac5-4a86-9621-87290ef159af /org/freedesktop/NetworkManager/ActiveConnection/5 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/De
[Kernel-packages] [Bug 1898076] [NEW] Groovy update: v5.8.13 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.8.13 upstream stable release from git://git.kernel.org/ Linux 5.8.13 clocksource/drivers/timer-ti-dm: Do reset before enable dm: fix bio splitting and its bio completion order for regular IO KVM: arm64: Assume write fault on S1PTW permission fault on instruction fetch io_uring: ensure open/openat2 name is cleaned on cancelation s390/zcrypt: Fix ZCRYPT_PERDEV_REQCNT ioctl mm: don't rely on system state to detect hot-plug operations mm: replace memmap_context by meminit_context mm/gup: fix gup_fast with dynamic page table folding mm, THP, swap: fix allocating cluster for swapfile by mistake dmabuf: fix NULL pointer dereference in dma_buf_release() MIPS: Loongson2ef: Disable Loongson MMI instructions media: cec-adap.c: don't use flush_scheduled_work() btrfs: fix overflow when copying corrupt csums for a message btrfs: fix put of uninitialized kobject after seed device delete kprobes: tracing/kprobes: Fix to kill kprobes on initmem after boot kprobes: Fix to check probe enabled before disarm_kprobe_ftrace() lib/bootconfig: Fix to remove tailing spaces after value lib/bootconfig: Fix a bug of breaking existing tree nodes mt76: mt7615: use v1 MCU API on MT7615 to fix issues with adding/removing stations s390/dasd: Fix zero write for FBA devices tracing: fix double free lib/string.c: implement stpcpy ALSA: hda/realtek: Enable front panel headset LED on Lenovo ThinkStation P520 ALSA: hda/realtek - Couldn't detect Mic if booting with headset plugged ALSA: usb-audio: Add delay quirk for H570e USB headsets scsi: lpfc: Fix initial FLOGI failure due to BBSCN not supported x86/ioapic: Unbreak check_timer() x86/irq: Make run_on_irqstack_cond() typesafe arch/x86/lib/usercopy_64.c: fix __copy_user_flushcache() cache writeback mm: validate pmd after splitting KVM: SVM: Add a dedicated INVD intercept routine KVM: x86: Reset MMU context if guest toggles CR4.SMAP or CR4.PKE spi: bcm-qspi: Fix probe regression on iProc platforms regulator: axp20x: fix LDO2/4 description MIPS: Add the missing 'CPU_1074K' into __get_cpu_type() PM / devfreq: tegra30: Disable clock on error in probe MIPS: Loongson-3: Fix fp register access if MSA enabled net/mlx5e: mlx5e_fec_in_caps() returns a boolean regmap: fix page selection for noinc writes regmap: fix page selection for noinc reads SUNRPC: Fix svc_flush_dcache() io_uring: fix openat/openat2 unified prep handling ALSA: asihpi: fix iounmap in error handler mac80211: fix 80 MHz association to 160/80+80 AP on 6 GHz cfg80211: fix 6 GHz channel conversion mac80211: do not disable HE if HT is missing on 2.4 GHz lib80211: fix unmet direct dependendices config warning when !CRYPTO bpf: Fix a rcu warning for bpffs map pretty-print batman-adv: mcast: fix duplicate mcast packets from BLA backbone to mesh batman-adv: mcast: fix duplicate mcast packets in BLA backbone from mesh batman-adv: mcast: fix duplicate mcast packets in BLA backbone from LAN nvme-tcp: fix kconfig dependency warning when !CRYPTO xsk: Fix number of pinned pages/umem size discrepancy batman-adv: Add missing include for in_interrupt() RDMA/core: Fix ordering of CQ pool destruction spi: spi-fsl-dspi: use XSPI mode instead of DMA for DPAA2 SoCs hv_netvsc: Switch the data path at the right time during hibernation drm/sun4i: sun8i-csc: Secondary CSC register correction igc: Fix not considering the TX delay for timestamps igc: Fix wrong timestamp latency numbers net: qed: RDMA personality shouldn't fail VF load net: qede: Disable aRFS for NPAR and 100G net: qed: Disable aRFS for NPAR and 100G drm/vc4/vc4_hdmi: fill ASoC card owner tools/libbpf: Avoid counting local symbols in ABI check bpf: Fix clobbering of r2 in bpf_gen_ld_abs mac802154: tx: fix use-after-free netfilter: nft_meta: use socket user_ns to retrieve skuid and skgid netfilter: conntrack: nf_conncount_init is failing with IPv6 disabled netfilter: ctnetlink: fix mark based dump filtering regression netfilter: ctnetlink: add a range check for l3/l4 protonum batman-adv: mcast/TT: fix wrongly dropped or rerouted packets atm: eni: fix the missed pci_disable_device() for eni_init_one() libbpf: Fix build failure from uninitialized variable warning batman-adv: bla: fix type misuse for backbone_gw hash indexing mwifiex: Increase AES key storage size to 256 bits clocksource/drivers/h8300_timer8: Fix wrong return value in h8300_8timer_init() ieee802154/adf7242: check status of adf7242_read_reg ieee802154: fix one possible memleak in ca8210_dev_com_init riscv: Fix Kendryte K210 device tree i2c:
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
Where does that 196 value come from? Was it present on zipl.conf after a pristine install? I wouldn't expect that on a pristine Ubuntu 20.04.1 install, so we would need to investigate where that value comes from. I know s390-tools itself used to add that crashkernel value there, but that only worked for upgrades from pre-16.04 to 16.04, AFAIU. So, it would not apply on such recent installs. Was it manually added there? Thanks. Cascardo. -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896904] Re: Intel 9560 WLAN (8086:9df0) producing computer hanging and wifi breakdown
I can confirm this issue with a 9260 on on Kernel .48, booting back into .47 works. ** Attachment added: "Dmesg output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896904/+attachment/5416228/+files/9260.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896904 Title: Intel 9560 WLAN (8086:9df0) producing computer hanging and wifi breakdown Status in linux package in Ubuntu: Confirmed Bug description: If I do video conferences for example my wifi breaks down. I'm preety sure the it happens since I updated my WiFi router (FritzBox 7590 to Firmware 7.20). I was in contact with the manufacturer. They don't know any problems. I checked dmesg and saw a lot of error messages. So i thought I should report a bug here. Some times WiFi breaks down and comes up again after a few seconds, sometimes it will not come back and I have to restart the computer. Sometimes I can't even turn of WiFi in the Ubuntu menu. Settings telling me something link "network manager not available" (not sure what the exact message is). All firmware updates are installed, I updated to the latest kernel and had the problem again. The logs generated with "ubuntu-bug linux" in this ticket are with symptom "recovers after some seconds" with massive hanging of hole Ubuntu (was not able to move mouse / press strg+alt+t to open terminal). Before I learned how to generate proper logs I saved output of dmesg. I will append some of this to this ticket. There are different error messages. Some without recovering. I will append more proper generated logs (ubuntu-bug linux) to this ticket if I get similar problems and if you would like to see them. It's a ThinkPad T490, it's Ubuntu 20.04.1 LTS, it's a "Intel Corp. Intel 9560 WLAN (8086:9df0)" WiFi card. fnpk@cl003287:~$ uname -a Linux cl003287 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux fnpk@cl003287:~$ fwupdmgr get-updates • Thunderbolt Controller has the latest available firmware version • Prometheus has the latest available firmware version • Prometheus IOTA Config has the latest available firmware version • SAMSUNG MZVLB512HBJQ-000L7 has no available firmware updates • System Firmware has the latest available firmware version • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 24 09:06:55 2020 InstallationDate: Installed on 2020-01-10 (257 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20N2000KGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-12 (134 days ago) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N2000KGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N2000KGE:pvrThinkPadT490:rvnLENOVO:rn20N2000KGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N2000KGE dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
When I first installed 20.04 I had no problem at all. I have been having this problem since 5.4.0-47-generic #51 I have to turn off or reboot 2, 3 times to get sound back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Comment bridged from LTC Bugzilla
--- Comment From mihaj...@de.ibm.com 2020-10-01 12:49 EDT--- The zipl.conf content was there right after the installation, before even installing the kdump tools. Hmm ... but I was using the legacy di installer from http://ports.ubuntu.com/dists/focal/main/installer-s390x/current/legacy-images/generic/. Are you saying that with the new installer there should be no crashkernel in the command line? Can I force the command line to be changed by removing the crashkernel parameter and re-running kdump-tools installation? -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
There should be no difference between using di or the new installer, unless there is something the installer is doing that is causing this. If you remove the crashkernel line from zipl.conf and run dpkg- reconfigure kdump-tools, it should add the new configuration value. Otherwise, it will keep whatever other value is there. The only exception is when you are upgrading from an older version of kdump-tools and it finds the value that old kdump-tools would put in there. There is a chance I am misreading the code from s390-tools package (the one with zipl). It used to add the crashkernel parameter there, but only when upgrading from versions pre-Xenial. I even tested that on a new system, when removing and reinstalling s390-tools, there was no crashkernel line in there. We are trying to reproduce this locally and will investigate what may be causing this. One other option would be to also replace that specific value. I would rather not do it unless really necessary, because otherwise we might replace a value put there by a user. Cascardo. -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897983] Re: cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15
This appears to have cleared up on B/aws-4.15 4.15.0-1084.88 after re- triggering the tests. Confirmed this is also showing up on the current cycle's F/aws (4.15.0-1084.88) too. Re-triggering tests to see if it will now pass on Focal as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1897983 Title: cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15 Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Bionic: New Bug description: 99224.09/10 19:12:56 DEBUG| utils:0153| [stdout] startup='Thu Sep 10 19:09:04 2020' 99225.09/10 19:12:56 DEBUG| utils:0153| [stdout] /opt/ltp/testcases/bin/cpuset_inherit_testset.sh: 109: /opt/ltp/testcases/bin/cpuset_inherit_testset.sh: let: not found 99226.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 1 TPASS: cpus: Inherited information is right! 99227.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 3 TPASS: cpus: Inherited information is right! 99228.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 5 TPASS: cpus: Inherited information is right! 99229.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 7 TPASS: cpus: Inherited information is right! 99230.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 9 TPASS: cpus: Inherited information is right! 99231.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 11 TFAIL: cpus: Test result - 0-7 Expected string - "0-" 99232.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 13 TPASS: mems: Inherited information is right! 99233.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 15 TPASS: mems: Inherited information is right! 99234.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 17 TPASS: mems: Inherited information is right! 99235.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 19 TPASS: mems: Inherited information is right! 99236.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 21 TPASS: mems: Inherited information is right! 99237.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 23 TPASS: mems: Inherited information is right! 99238.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 25 TPASS: cpu_exclusive: Inherited information is right! 99239.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 27 TPASS: cpu_exclusive: Inherited information is right! 99240.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 29 TPASS: mem_exclusive: Inherited information is right! 99241.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 31 TPASS: mem_exclusive: Inherited information is right! 99242.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 33 TPASS: mem_hardwall: Inherited information is right! 99243.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 35 TPASS: mem_hardwall: Inherited information is right! 99244.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 37 TPASS: memory_migrate: Inherited information is right! 99245.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 39 TPASS: memory_migrate: Inherited information is right! 99246.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 41 TPASS: memory_spread_page: Inherited information is right! 99247.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 43 TPASS: memory_spread_page: Inherited information is right! 99248.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 45 TPASS: memory_spread_slab: Inherited information is right! 99249.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 47 TPASS: memory_spread_slab: Inherited information is right! 99250.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 49 TPASS: sched_load_balance: Inherited information is right! 99251.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 51 TPASS: sched_load_balance: Inherited information is right! 99252.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 53 TPASS: sched_relax_domain_level: Inherited information is right! 99253.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 55 TPASS: sched_relax_domain_level: Inherited information is right! 99254.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 57 TPASS: sched_relax_domain_level: Inherited information is right! 99255.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 59 TPASS: sched_relax_domain_level: Inherited information is right! 99256.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 61 TPASS: sched_relax_domain_level: Inherited information is right! 9925
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
So, after some investigation, it looks like the zipl-installer d-i component is responsible for creating /etc/zipl.conf with the default crashkernel parameter with value 196M. With that into consideration, one wonders how kdump-tools would previously set its default value of "384M-:128M" in there. In any case, 196M would work better for most users anyway. But I still wonder how this was not reported before. Maybe other installation methods or upgrades would lead to a different situation. But as we understand the current situation now, and it would be too late to fix d-i at this point, I believe it is acceptable to replace that value when installing or upgrading kdump-tools. I will work on a new test version of the package. Thanks. Cascardo. -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I'm still seeing this issue, and it now sometimes appears on boot without me having done anything. What can I do to help move this forward? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8
[Kernel-packages] [Bug 1898091] [NEW] Multiple random crashes for the past week
You have been subscribed to a public bug: For the past week or so, I have started to have random crashes. Somtimes it is just an app that crashes, sometimes the machine freezes up completely and sometimes it just reboots. I ran a memory test for about 8 hours over the weekend and it found no issues. Looking through some of the crash dmesg files I see: 202009290318/dmesg.202009290318:1186:[ 5527.345666] BUG: unable to handle kernel paging request at ab1bd511 202009291228/dmesg.202009291228:1194:[12423.898689] BUG: unable to handle kernel paging request at ff8e 202009301804/dmesg.202009301804:1386:[31355.601321] BUG: unable to handle kernel paging request at b2cbb6cf 202010011046/dmesg.202010011046:1200:[ 3081.774984] BUG: unable to handle kernel paging request at a0bd8f625a50 Which still leads to think a memory issue. Going to run a longer memtest. I am usually pretty good and figuring out what is going on but this time I need some help to make sure I am on the right track or tell me I am completely wrong. Thanks in advance. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3921 F pulseaudio /dev/snd/controlC1: chris 3921 F pulseaudio Date: Tue Sep 29 16:09:48 2020 InstallationDate: Installed on 2019-01-07 (632 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7693 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=65a42e57-56c3-47ce-beb9-73c0f182e1d4 ro sbcore.autosuspend=-1 amd_iommu=on iommu=pt crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) 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.:bvrV2.6:bd10/08/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kernelcrash bionic bot-comment -- Multiple random crashes for the past week https://bugs.launchpad.net/bugs/1898091 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 1898091] Re: Multiple random crashes for the past week
** Package changed: 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/1898091 Title: Multiple random crashes for the past week Status in linux package in Ubuntu: New Bug description: For the past week or so, I have started to have random crashes. Somtimes it is just an app that crashes, sometimes the machine freezes up completely and sometimes it just reboots. I ran a memory test for about 8 hours over the weekend and it found no issues. Looking through some of the crash dmesg files I see: 202009290318/dmesg.202009290318:1186:[ 5527.345666] BUG: unable to handle kernel paging request at ab1bd511 202009291228/dmesg.202009291228:1194:[12423.898689] BUG: unable to handle kernel paging request at ff8e 202009301804/dmesg.202009301804:1386:[31355.601321] BUG: unable to handle kernel paging request at b2cbb6cf 202010011046/dmesg.202010011046:1200:[ 3081.774984] BUG: unable to handle kernel paging request at a0bd8f625a50 Which still leads to think a memory issue. Going to run a longer memtest. I am usually pretty good and figuring out what is going on but this time I need some help to make sure I am on the right track or tell me I am completely wrong. Thanks in advance. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3921 F pulseaudio /dev/snd/controlC1: chris 3921 F pulseaudio Date: Tue Sep 29 16:09:48 2020 InstallationDate: Installed on 2019-01-07 (632 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7693 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=65a42e57-56c3-47ce-beb9-73c0f182e1d4 ro sbcore.autosuspend=-1 amd_iommu=on iommu=pt crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) 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.:bvrV2.6:bd10/08/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898091] 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/1898091 Title: Multiple random crashes for the past week Status in linux package in Ubuntu: Confirmed Bug description: For the past week or so, I have started to have random crashes. Somtimes it is just an app that crashes, sometimes the machine freezes up completely and sometimes it just reboots. I ran a memory test for about 8 hours over the weekend and it found no issues. Looking through some of the crash dmesg files I see: 202009290318/dmesg.202009290318:1186:[ 5527.345666] BUG: unable to handle kernel paging request at ab1bd511 202009291228/dmesg.202009291228:1194:[12423.898689] BUG: unable to handle kernel paging request at ff8e 202009301804/dmesg.202009301804:1386:[31355.601321] BUG: unable to handle kernel paging request at b2cbb6cf 202010011046/dmesg.202010011046:1200:[ 3081.774984] BUG: unable to handle kernel paging request at a0bd8f625a50 Which still leads to think a memory issue. Going to run a longer memtest. I am usually pretty good and figuring out what is going on but this time I need some help to make sure I am on the right track or tell me I am completely wrong. Thanks in advance. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 3921 F pulseaudio /dev/snd/controlC1: chris 3921 F pulseaudio Date: Tue Sep 29 16:09:48 2020 InstallationDate: Installed on 2019-01-07 (632 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7693 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=65a42e57-56c3-47ce-beb9-73c0f182e1d4 ro sbcore.autosuspend=-1 amd_iommu=on iommu=pt crashkernel=512M-:192M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) 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.:bvrV2.6:bd10/08/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897983] Re: cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15
This is also getting resolved on F/aws after retriggering the test. Removing the blocker and marking invalid. ** Tags removed: kqa-blocker ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux-aws (Ubuntu) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1897983 Title: cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15 Status in ubuntu-kernel-tests: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Invalid Bug description: 99224.09/10 19:12:56 DEBUG| utils:0153| [stdout] startup='Thu Sep 10 19:09:04 2020' 99225.09/10 19:12:56 DEBUG| utils:0153| [stdout] /opt/ltp/testcases/bin/cpuset_inherit_testset.sh: 109: /opt/ltp/testcases/bin/cpuset_inherit_testset.sh: let: not found 99226.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 1 TPASS: cpus: Inherited information is right! 99227.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 3 TPASS: cpus: Inherited information is right! 99228.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 5 TPASS: cpus: Inherited information is right! 99229.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 7 TPASS: cpus: Inherited information is right! 99230.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 9 TPASS: cpus: Inherited information is right! 99231.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 11 TFAIL: cpus: Test result - 0-7 Expected string - "0-" 99232.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 13 TPASS: mems: Inherited information is right! 99233.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 15 TPASS: mems: Inherited information is right! 99234.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 17 TPASS: mems: Inherited information is right! 99235.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 19 TPASS: mems: Inherited information is right! 99236.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 21 TPASS: mems: Inherited information is right! 99237.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 23 TPASS: mems: Inherited information is right! 99238.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 25 TPASS: cpu_exclusive: Inherited information is right! 99239.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 27 TPASS: cpu_exclusive: Inherited information is right! 99240.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 29 TPASS: mem_exclusive: Inherited information is right! 99241.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 31 TPASS: mem_exclusive: Inherited information is right! 99242.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 33 TPASS: mem_hardwall: Inherited information is right! 99243.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 35 TPASS: mem_hardwall: Inherited information is right! 99244.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 37 TPASS: memory_migrate: Inherited information is right! 99245.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 39 TPASS: memory_migrate: Inherited information is right! 99246.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 41 TPASS: memory_spread_page: Inherited information is right! 99247.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 43 TPASS: memory_spread_page: Inherited information is right! 99248.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 45 TPASS: memory_spread_slab: Inherited information is right! 99249.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 47 TPASS: memory_spread_slab: Inherited information is right! 99250.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 49 TPASS: sched_load_balance: Inherited information is right! 99251.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 51 TPASS: sched_load_balance: Inherited information is right! 99252.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 53 TPASS: sched_relax_domain_level: Inherited information is right! 99253.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 55 TPASS: sched_relax_domain_level: Inherited information is right! 99254.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 57 TPASS: sched_relax_domain_level: Inherited information is right! 99255.09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 59 TPASS: sched_relax_domain_level: Inherited information is right! 99256.09/10 19:12:56 DEBUG|
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Affected by this also. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 hi @thiagocmarcello Sorry to hear that... The day my headset all of a sudden started working, ie. 2020-09-16, it happened right after my dayly sudo apt-get update... Must have been another package that dealt with it... As a matter a fact, the linux kernel update took place on 2020-09-01... Must have been distracted Here is the list of updates I had that day: fdisk:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), cryptsetup-bin:amd64 (2:2.2.2-3ubuntu2, 2:2.2.2-3ubuntu2.2), cry ptsetup-initramfs:amd64 (2:2.2.2-3ubuntu2, 2:2.2.2-3ubuntu2.2), firmware-manager-notify:amd64 (0.1.1~1585248044~20.04~5b047 86, 0.1.1~1599764521~20.04~f6b394a), uuid-runtime:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), libfdisk1:amd64 (2.34-0.1ubun tu9, 2.34-0.1ubuntu9.1), popsicle-gtk:amd64 (1.1.0~1596832906~20.04~903614f, 1.1.0~1600184897~20.04~c093c67), libmount1:amd 64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), libpop-upgrade-gtk:amd64 (0.1.0~1598294830~20.04~eb2eb9d, 0.1.0~1600134377~20.04~9 c2a95e), popsicle:amd64 (1.1.0~1596832906~20.04~903614f, 1.1.0~1600184897~20.04~c093c67), gir1.2-accountsservice-1.0:amd64 (0.6.55-0ubuntu12~20.04.1pop0, 0.6.55-0ubuntu12pop0~1599854970~20.04~bfe7ef3), util-linux:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), libgupnp-1.2-0:amd64 (1.2.2-1, 1.2.3-0ubuntu0.20.04.1), cryptsetup-run:amd64 (2:2.2.2-3ubuntu2, 2:2.2.2-3ubuntu2.2), initramfs-tools-bin:amd64 (0.136ubuntu6.2, 0.136ubuntu6.3), libmount-dev:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), mount:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), libblkid1:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), im-config:amd64 (0.44-1ubuntu1.1, 0.44-1ubuntu1.2), libuuid1:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), libsmartcols1:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), rfkill:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), uuid-dev:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), bsdutils:amd64 (1:2.34-0.1ubuntu9, 1:2.34-0.1ubuntu9.1), libgssdp-1.2-0:amd64 (1.2.2-1, 1.2.3-0ubuntu0.20.04.1), libfirmware-manager:amd64 (0.1.1~1585248044~20.04~5b04786, 0.1.1~1599764521~20.04~f6b394a), libcryptsetup12:amd64 (2:2.2.2-3ubuntu2, 2:2.2.2-3ubuntu2.2), linux-firmware:amd64 (1.187.1+system76~1597425559~20.04~3cf919d, 1.190+system76~1599667136~20.04~5b2179a), pop-shell:amd64 (0.1.0~1599583364~20.04~017c92e, 0.1.0~1600180966~20.04~e5a80ea), accountsservice:amd64 (0.6.55-0ubuntu12~20.04.1pop0, 0.6.55-0ubuntu12pop0~1599854970~20.04~bfe7ef3), pop-upgrade:amd64 (0.1.0~1598294830~20.04~eb2eb9d, 0.1.0~1600134377~20.04~9c2a95e), libblkid-dev:amd64 (2.34-0.1ubuntu9, 2.34-0.1ubuntu9.1), cryptsetup:amd64 (2:2.2.2-3ubuntu2, 2:2.2.2-3ubuntu2.2), firmware-manager-shared:amd64 (0.1.1~1585248044~20.04~5b04786, 0.1.1~1599764521~20.04~f6b394a), initramfs-tools-core:amd64 (0.136ubuntu6.2, 0.136ubuntu6.3), initramfs-tools:amd64 (0.136ubuntu6.2, 0.136ubuntu6.3), libaccountsservice0:amd64 (0.6.55-0ubuntu12~20.04.1pop0, 0.6.55-0ubuntu12pop0~1599854970~20.04~bfe7ef3), pop-shell-shortcuts:amd64 (0.1.0~1599143748~20.04~069276a, 0.1.0~1599845228~20.04~9280535) (from /var/log/apt/history.log) Hope someone smarter than me will figure out which package did unlock the HSP/HFP profile... dGo -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.
[Kernel-packages] [Bug 1898130] [NEW] oops in nvkm_udevice_info() [nouveau]
Public bug reported: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: groovy ** Attachment added: "dmesg.out" https://bugs.launchpad.net/bugs/1898130/+attachment/5416342/+files/dmesg.out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898130] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1898130 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898130] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416347/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12
[Kernel-packages] [Bug 1898130] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416349/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12: 9
[Kernel-packages] [Bug 1898130] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416351/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12: 994
[Kernel-packages] [Bug 1898130] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416353/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12:
[Kernel-packages] [Bug 1898130] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416348/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12: 99480824
[Kernel-packages] [Bug 1898130] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416352/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12: 994
[Kernel-packages] [Bug 1898130] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416359/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12: 9
[Kernel-packages] [Bug 1898130] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416355/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11:
[Kernel-packages] [Bug 1898130] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416354/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11:
[Kernel-packages] [Bug 1898130] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416358/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12: f
[Kernel-packages] [Bug 1898130] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416357/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12: 994808
[Kernel-packages] [Bug 1898130] Re: oops in nvkm_udevice_info() [nouveau]
apport information ** Description changed: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. + + [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) + [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) + [ 221.046328] BUG: kernel NULL pointer dereference, address: + [ 221.054098] #PF: supervisor read access in kernel mode + [ 221.059830] #PF: error_code(0x) - not-present page + [ 221.065559] PGD 0 P4D 0 + [ 221.068383] Oops: [#1] SMP NOPTI + [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu + [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 + [ 221.090729] Workqueue: events work_for_cpu_fn + [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] + [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 + [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 + [ 221.129058] RAX: RBX: 0068 RCX: 00c6 + [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 + [ 221.144979] RBP: a7c9dd153ba0 R08: R09: + [ 221.152939] R10: 0088 R11: R12: 994808245680 + [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: + [ 221.168862] FS: () GS:99484e00() knlGS: + [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 + [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 + [ 221.192259] Call Trace: + [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] + [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] + [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] + [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] + [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] + [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] + [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] + [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] + [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] + [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] + [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] + [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] + [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] + [ 221.265747] local_pci_probe+0x48/0x80 + [ 221.269926] work_for_cpu_fn+0x1a/0x30 + [ 221.274107] process_one_work+0x1e8/0x3b0 + [ 221.278577] worker_thread+0x218/0x370 + [ 221.282759] kthread+0x12f/0x150 + [ 221.286357] ? process_one_work+0x3b0/0x3b0 + [ 221.291023] ? __kthread_bind_mask+0x70/0x70 + [ 221.295788] ret_from_fork+0x22/0x30 + [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 + [ 221.389734] CR2: + [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- + [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] + [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 + [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 + [ 222.067491] RAX: RBX: 0068 RCX: 00c6 + [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 + [ 222.083409] RBP: a7c9dd153ba0 R08: R09: + [ 222.091369] R10: 0088 R11: R12: 994808245680 + [ 222.099329] R13: 994808386320 R14: 99483377f800 R15: + [ 222.107290] FS: () GS:99484e00() knlGS: + [ 222.116316] CS: 0010 DS: ES: CR0: 80050033 + [ 222.122723] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 ** Tags added: apport-collecte
[Kernel-packages] [Bug 1898130] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416350/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12: 99480824
[Kernel-packages] [Bug 1898130] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1898130/+attachment/5416356/+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/1898130 Title: oops in nvkm_udevice_info() [nouveau] Status in linux package in Ubuntu: Incomplete Bug description: The 5.8.0-20.21 reliably trips an Oops on startup when initializing the nouveau driver. [ 221.032875] nouveau :07:00.0: unknown chipset (17a1) [ 221.039893] nouveau :07:00.0: unknown chipset (17a1) [ 221.046328] BUG: kernel NULL pointer dereference, address: [ 221.054098] #PF: supervisor read access in kernel mode [ 221.059830] #PF: error_code(0x) - not-present page [ 221.065559] PGD 0 P4D 0 [ 221.068383] Oops: [#1] SMP NOPTI [ 221.072469] CPU: 32 PID: 1627 Comm: kworker/32:1 Not tainted 5.8.0-20-generic #21-Ubuntu [ 221.081497] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 221.090729] Workqueue: events work_for_cpu_fn [ 221.095865] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 221.102277] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 221.123232] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 221.129058] RAX: RBX: 0068 RCX: 00c6 [ 221.137020] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 221.144979] RBP: a7c9dd153ba0 R08: R09: [ 221.152939] R10: 0088 R11: R12: 994808245680 [ 221.160900] R13: 994808386320 R14: 99483377f800 R15: [ 221.168862] FS: () GS:99484e00() knlGS: [ 221.177890] CS: 0010 DS: ES: CR0: 80050033 [ 221.184299] CR2: CR3: 00b23ac0a000 CR4: 00340ee0 [ 221.192259] Call Trace: [ 221.195049] ? nvkm_object_init+0x8d/0x110 [nouveau] [ 221.200669] nvkm_udevice_mthd+0x51/0xb0 [nouveau] [ 221.206073] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 221.211373] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 221.216574] nvkm_ioctl+0xf0/0x190 [nouveau] [ 221.221418] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 221.226818] nvif_object_ioctl+0x4e/0x60 [nouveau] [ 221.232213] nvif_object_mthd+0x9f/0x150 [nouveau] [ 221.237609] ? nvif_object_init+0x10a/0x1a0 [nouveau] [ 221.243294] nvif_device_init+0x4f/0x60 [nouveau] [ 221.248618] nouveau_cli_init+0x199/0x450 [nouveau] [ 221.254127] nouveau_drm_device_init+0x54/0x2d0 [nouveau] [ 221.260215] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 221.265747] local_pci_probe+0x48/0x80 [ 221.269926] work_for_cpu_fn+0x1a/0x30 [ 221.274107] process_one_work+0x1e8/0x3b0 [ 221.278577] worker_thread+0x218/0x370 [ 221.282759] kthread+0x12f/0x150 [ 221.286357] ? process_one_work+0x3b0/0x3b0 [ 221.291023] ? __kthread_bind_mask+0x70/0x70 [ 221.295788] ret_from_fork+0x22/0x30 [ 221.299773] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm efi_pstore rapl ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul ast crc32_pclmul drm_vram_helper ghash_clmulni_intel drm_ttm_helper aesni_intel ttm drm_kms_helper crypto_simd syscopyarea sysfillrect cryptd glue_helper sysimgblt fb_sys_fops mlx5_core igb cec mpt3sas pci_hyperv_intf dca raid_class nvme rc_core i2c_algo_bit scsi_transport_sas tls xhci_pci nvme_core mlxfw drm xhci_pci_renesas i2c_piix4 [ 221.389734] CR2: [ 221.393431] ---[ end trace f0b36cab4e2bf100 ]--- [ 222.034293] RIP: 0010:nvkm_udevice_info+0x180/0x340 [nouveau] [ 222.034300] Code: 10 49 89 45 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 45 10 49 8b 86 c0 00 00 00 49 8d 7d 18 ba 10 00 00 00 <48> 8b 30 e8 58 bb ff d5 49 8b 76 28 49 8d 7d 28 ba 40 00 00 00 e8 [ 222.061663] RSP: 0018:a7c9dd153b70 EFLAGS: 00010246 [ 222.067491] RAX: RBX: 0068 RCX: 00c6 [ 222.075450] RDX: 0010 RSI: 994808386320 RDI: 994808386338 [ 222.083409] RBP: a7c9dd153ba0 R08: R09: [ 222.091369] R10: 0088 R11: R12:
[Kernel-packages] [Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds
I can confirm my specific failure was fixed with kernel 5.4.0-48 ... Question for original reporter Dan -- is this issue (slow btrfs scanning) still occuring for you? Now fixed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460447 Title: Boot slow, "scanning for btrfs filesystems" takes 100 seconds Status in linux package in Ubuntu: Confirmed Bug description: I installed 14.10 and used btrfs for /home. Later, I did a clean install of 15.04, using the same /home partition. Ever since then, boots have been agonizingly slow; all the delay appears to be while the message "scanning for btrfs filesystems" is diplayed early in boot. The system is an i7 with one disk: root@i7:~# fdisk /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x7f84 Device Boot StartEndSectors Size Id Type /dev/sda1 * 2048 117186559 117184512 55.9G 83 Linux /dev/sda2 117186560 234373119 117186560 55.9G 83 Linux /dev/sda3 234375166 1953523711 1719148546 819.8G 5 Extended /dev/sda5 234375168 273434623 39059456 18.6G 82 Linux swap / Solaris /dev/sda6 273436672 1953523711 1680087040 801.1G 83 Linux root@i7:~# df -T | grep sd /dev/sda2 ext4 57542652 10103624 44492980 19% / /dev/sda6 btrfs840043520 172076728 665321064 21% /home I'll attach a bootchart, but I suspect the btrfs delay happens before the bootchart starts? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-16-generic 3.19.0-16.16 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dank 2176 F pulseaudio /dev/snd/controlC0: dank 2176 F pulseaudio CurrentDesktop: Unity Date: Sun May 31 08:53:37 2015 HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223 InstallationDate: Installed on 2015-05-16 (14 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=270a0d36-9ed9-4e58-b909-175db447838d ro quiet splash init=/lib/systemd/systemd-bootchart RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: X58 Extreme dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898130] Re: oops in nvkm_udevice_info() [nouveau]
Also impacts latest upstream: [ 213.131657] nouveau :07:00.0: unknown chipset (17a1) [ 213.138547] nouveau :07:00.0: unknown chipset (17a1) [ 213.144938] BUG: kernel NULL pointer dereference, address: [ 213.152704] #PF: supervisor read access in kernel mode [ 213.158433] #PF: error_code(0x) - not-present page [ 213.164162] PGD 0 P4D 0 [ 213.166985] Oops: [#1] SMP NOPTI [ 213.171068] CPU: 32 PID: 206 Comm: kworker/32:0 Not tainted 5.9.0-rc7+ #1 [ 213.178639] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.25 06/30/2020 [ 213.187866] Workqueue: events work_for_cpu_fn [ 213.192761] RIP: 0010:nvkm_udevice_mthd+0x1ed/0x7d0 [nouveau] [ 213.199170] Code: 10 49 89 47 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 47 10 49 8b 86 c0 00 00 00 49 8d 7f 18 ba 10 00 00 00 <48> 8b 30 e8 6b 91 89 c0 49 8b 76 28 49 8d 7f 28 ba 40 00 00 00 e8 [ 213.220121] RSP: 0018:ae0619d47b48 EFLAGS: 00010246 [ 213.225948] RAX: RBX: 9cefab819580 RCX: 00c6 [ 213.233907] RDX: 0010 RSI: RDI: 9cef988f0578 [ 213.241864] RBP: ae0619d47b80 R08: R09: [ 213.249813] R10: 0088 R11: 01320122 R12: [ 213.257762] R13: 0068 R14: 9cef6107c400 R15: 9cef988f0560 [ 213.265721] FS: () GS:9cefce00() knlGS: [ 213.274747] CS: 0010 DS: ES: CR0: 80050033 [ 213.281153] CR2: CR3: 007f3019c000 CR4: 00350ee0 [ 213.289104] Call Trace: [ 213.291854] ? nvkm_object_insert+0x6f/0x80 [nouveau] [ 213.297509] nvkm_object_mthd+0x1a/0x30 [nouveau] [ 213.302773] nvkm_ioctl_mthd+0x65/0x70 [nouveau] [ 213.307940] nvkm_ioctl+0xf0/0x190 [nouveau] [ 213.312735] nvkm_client_ioctl+0x12/0x20 [nouveau] [ 213.318097] nvif_object_ioctl+0x4f/0x60 [nouveau] [ 213.323460] nvif_object_mthd+0x9f/0x150 [nouveau] [ 213.328822] ? nvif_object_ctor+0x14b/0x1d0 [nouveau] [ 213.334473] nvif_device_ctor+0x61/0x70 [nouveau] [ 213.339749] nouveau_cli_init+0x1a3/0x460 [nouveau] [ 213.345215] ? nouveau_drm_device_init+0x3e/0x780 [nouveau] [ 213.351454] nouveau_drm_device_init+0x77/0x780 [nouveau] [ 213.357479] ? pci_read_config_word+0x27/0x40 [ 213.362337] ? pci_enable_device_flags+0x14f/0x170 [ 213.367705] nouveau_drm_probe+0x132/0x1f0 [nouveau] [ 213.373241] local_pci_probe+0x48/0x80 [ 213.377419] work_for_cpu_fn+0x1a/0x30 [ 213.381598] process_one_work+0x1e8/0x3b0 [ 213.386068] worker_thread+0x53/0x420 [ 213.390149] kthread+0x12f/0x150 [ 213.393745] ? process_one_work+0x3b0/0x3b0 [ 213.398406] ? __kthread_bind_mask+0x70/0x70 [ 213.403169] ret_from_fork+0x22/0x30 [ 213.407153] Modules linked in: nouveau(+) mxm_wmi wmi video nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd amd_energy kvm_amd kvm rapl efi_pstore ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure hid_generic usbhid uas hid usb_storage ib_uverbs ib_core crct10dif_pclmul crc32_pclmul ast ghash_clmulni_intel drm_vram_helper aesni_intel drm_ttm_helper crypto_simd ttm cryptd drm_kms_helper glue_helper syscopyarea sysfillrect sysimgblt mlx5_core fb_sys_fops pci_hyperv_intf igb cec mpt3sas dca rc_core raid_class nvme tls i2c_algo_bit scsi_transport_sas drm mlxfw xhci_pci nvme_core xhci_pci_renesas i2c_piix4 [ 213.497060] CR2: [ 213.500755] ---[ end trace eed3a19f1f25ca74 ]--- [ 213.616704] RIP: 0010:nvkm_udevice_mthd+0x1ed/0x7d0 [nouveau] [ 213.623113] Code: 10 49 89 47 08 4d 85 c9 74 10 48 85 c0 74 0b 41 8b 51 70 48 29 d0 49 89 47 10 49 8b 86 c0 00 00 00 49 8d 7f 18 ba 10 00 00 00 <48> 8b 30 e8 6b 91 89 c0 49 8b 76 28 49 8d 7f 28 ba 40 00 00 00 e8 [ 213.644066] RSP: 0018:ae0619d47b48 EFLAGS: 00010246 [ 213.649892] RAX: RBX: 9cefab819580 RCX: 00c6 [ 213.657851] RDX: 0010 RSI: RDI: 9cef988f0578 [ 213.665808] RBP: ae0619d47b80 R08: R09: [ 213.673757] R10: 0088 R11: 01320122 R12: [ 213.681708] R13: 0068 R14: 9cef6107c400 R15: 9cef988f0560 [ 213.689668] FS: () GS:9cefce00() knlGS: [ 213.698693] CS: 0010 DS: ES: CR0: 80050033 [ 213.705100] CR2: CR3: 007f3019c000 CR4: 00350ee0 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subsc
[Kernel-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
This bug was fixed in the package procps - 2:3.3.16-5ubuntu2 --- procps (2:3.3.16-5ubuntu2) groovy; urgency=medium * debian/sysctl.d/10-kernel-hardening.conf: - Add documentation for DMESG_RESTRICT feature, and allow users to disable by uncommenting kernel.dmesg_restrict=0. (LP: #1886112) -- Matthew Ruffell Thu, 23 Jul 2020 16:59:38 +1200 ** Changed in: procps (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Released Status in procps package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Released Status in procps source package in Groovy: Fix Released Status in util-linux source package in Groovy: Won't Fix Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by cha
[Kernel-packages] [Bug 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!
Filed as https://gitlab.freedesktop.org/drm/amd/-/issues/1318 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1318 https://gitlab.freedesktop.org/drm/amd/-/issues/1318 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883493 Title: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out! Status in linux package in Ubuntu: Incomplete Bug description: un 15 08:30:42 alhazen kernel: [ 1566.155810] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1566.159792] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1571.020144] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=535493, emitted seq=535495 Jun 15 08:30:47 alhazen kernel: [ 1571.020216] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 3664 thread Xorg:cs0 pid 3694 Jun 15 08:30:47 alhazen kernel: [ 1571.020218] [drm] GPU recovery disabled. Mouse pointer still moves, but apart from that the display is frozen. Music keeps playing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 09:09:56 2020 InstallationDate: Installed on 2020-05-28 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi-enforce-resources=lax vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/02/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890050] Re: Mouse malfunction when launching steam
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890050 Title: Mouse malfunction when launching steam Status in linux package in Ubuntu: Expired Bug description: When launching Steam mouse automatically stops working. Only way to fix it is closing Steam and plugging the mouse again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 19:30:32 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d6] InstallationDate: Installed on 2020-01-29 (185 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A15 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1555f7ff-6084-4156-b1cd-6e9c57ec0e76 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VD PLUS (MS-7A15) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd10/28/2016:svnMSI:pnMS-7A15:pvr1.0:rvnMSI:rnH110MPRO-VDPLUS(MS-7A15):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A15 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808736] Re: Saving crash report failed
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808736 Title: Saving crash report failed Status in Ubuntu MATE: Expired Status in linux package in Ubuntu: Expired Bug description: In response to a error window stating that there is a problem with Caja (other than the memory leak that eats up move than 8GB of RAM). I clicked report to developers. See additional screen shot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2807 F pulseaudio /dev/snd/controlC0: robert 2807 F pulseaudio CurrentDesktop: MATE Date: Sun Dec 16 22:06:41 2018 InstallationDate: Installed on 2018-12-16 (0 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1808736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808736] Re: Saving crash report failed
[Expired for Ubuntu MATE because there has been no activity for 60 days.] ** Changed in: ubuntu-mate Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808736 Title: Saving crash report failed Status in Ubuntu MATE: Expired Status in linux package in Ubuntu: Expired Bug description: In response to a error window stating that there is a problem with Caja (other than the memory leak that eats up move than 8GB of RAM). I clicked report to developers. See additional screen shot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2807 F pulseaudio /dev/snd/controlC0: robert 2807 F pulseaudio CurrentDesktop: MATE Date: Sun Dec 16 22:06:41 2018 InstallationDate: Installed on 2018-12-16 (0 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1808736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] [NEW] No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352
Public bug reported: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in linux package in Ubuntu: New Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352
** Attachment added: "lspci log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898154/+attachment/5416429/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in linux package in Ubuntu: Incomplete Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352
** Attachment added: "version log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898154/+attachment/5416430/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in linux package in Ubuntu: Incomplete Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352
LSB: Description:Ubuntu 20.04.1 LTS Release:20.04 ** Tags added: hwe-networking-wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in linux package in Ubuntu: Incomplete Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1898154 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in linux package in Ubuntu: Incomplete Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352
apport information ** Tags added: apport-collected staging ** Description changed: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ravindran 1652 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-06 (179 days ago) + InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) + MachineType: Dell Inc. XPS 15 9560 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-48-lowlatency N/A + linux-backports-modules-5.4.0-48-lowlatency N/A + linux-firmware 1.187.3 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + StagingDrivers: r8188eu + Tags: focal staging + Uname: Linux 5.4.0-48-lowlatency x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/21/2020 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.20.0 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 15 9560 + dmi.product.sku: 07BE + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416439/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416451/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416453/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416445/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416446/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416442/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416450/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416449/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416452/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416455/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416448/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416440/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416447/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416454/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416441/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416443/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416444/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352
Temporarily attached USB wireless adapter to report info (which works) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1898154/+attachment/5416456/+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/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898154] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352
** Also affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1898154 Title: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: The Wireless adapter Broadcom/Dell BCM4352 802.11ac Wireless Network Adapter does not work starting kernel versions 5.4.0-47-lowlatency and 5.4.0-48-lowlatency Works fine in 5.4.0-45-lowlatency. As I dont have wifi/network, in the newer kernels, logging this bug now from 5.4.0-45-lowlatency I will attach the required logs in a bit. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravindran 1652 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (179 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-lowlatency root=UUID=2c90e861-0f50-4525-ad3a-f8d5ce594cb1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-48.52-lowlatency 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-lowlatency N/A linux-backports-modules-5.4.0-48-lowlatency N/A linux-firmware 1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no StagingDrivers: r8188eu Tags: focal staging Uname: Linux 5.4.0-48-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805806 Title: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: This issue can be found on 2 different ARM64 node, TunderX Cavium node "starmie" and Moonshot "ms10-34-mcdivittB0-kernel" Running test_maps bpf test.. Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Failed sockmap unexpected timeout ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0
[Kernel-packages] [Bug 1891421] Re: kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with "FAIL: can't add fou port 7777, skipping test"
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891421 Title: kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with "FAIL: can't add fou port , skipping test" Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Bug description: The kci_test_encap_fou() from kci_test_encap() in rtnetlink.sh of kselftests/net will fail with non-zero return value, and print: "FAIL: can't add fou port , skipping test" How to reproduce this: devdummy="test-dummy0" testns="testns" ip netns add "$testns" ip netns exec "$testns" ip link set lo up ip netns exec "$testns" ip link add name "$devdummy" type dummy ip netns exec "$testns" ip link set "$devdummy" up ip netns exec "$testns" ip fou add port ipproto 47 RTNETLINK answers: No such file or directory Error talking to the kernel This is not a regression, it's the real test result after bug 1890136 has been fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1 This failure is similar to bug 1884234, however, this test didn't fail on ADT with focal/linux before 5.4.0-44.48. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892213/+subscriptions -- Mailing list: https
[Kernel-packages] [Bug 1851619] Re: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1851619 Title: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 Status in ubuntu-kernel-tests: Triaged Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-aws source package in Eoan: New Status in linux-gcp source package in Eoan: New Bug description: The test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 (5.3.0-1007.7~18.04.1-gcp) # selftests: net: test_blackhole_dev.sh # test_blackhole_dev: [FAIL] not ok 13 selftests: net: test_blackhole_dev.sh Need to run this manually to see what's going on there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
*** This bug is a duplicate of bug 1829984 *** https://bugs.launchpad.net/bugs/1829984 ** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 05:58:50 2019' memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821 memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 30821 memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 4194304 expected memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855 memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 30855 memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 4194304 expected memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 expected memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 core=no cu=8 cs=7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:06:31 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: Triaged Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01
[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829983 Title: memcg_stat from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: memcg_stat_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168 memcg_stat_test 1 TINFO: Warming up pid: 31352 memcg_stat_test 1 TINFO: Process is still here after warm up: 31352 memcg_stat_test 1 TPASS: cache is 135168 as expected memcg_stat_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168 memcg_stat_test 2 TINFO: Warming up pid: 31380 memcg_stat_test 2 TINFO: Process is still here after warm up: 31380 memcg_stat_test 2 TPASS: mapped_file is 135168 as expected memcg_stat_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096 memcg_stat_test 3 TINFO: Warming up pid: 31409 memcg_stat_test 3 TINFO: Process is still here after warm up: 31409 memcg_stat_test 3 TPASS: unevictable is 4096 as expected memcg_stat_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096 memcg_stat_test 4 TINFO: Warming up pid: 31434 memcg_stat_test 4 TINFO: Process is still here after warm up: 31434 memcg_stat_test 4 TPASS: unevictable is 4096 as expected memcg_stat_test 5 TINFO: Starting test 5 sh: echo: I/O error memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected memcg_stat_test 6 TINFO: Starting test 6 sh: echo: I/O error memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed sh: echo: I/O error memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected memcg_stat_test 7 TINFO: Starting test 7 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled memcg_stat_test 7 TINFO: Starting test 8 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: p
