[Kernel-packages] [Bug 1883536] Re: Wifi does not work after suspend
** Tags added: hwe-networking-wifi ** Summary changed: - Wifi does not work after suspend + Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535] WiFi does not work after suspend -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883536 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535] WiFi does not work after suspend Status in linux package in Ubuntu: Confirmed Bug description: After I resume from suspend, Wifi does not work. I have to reload the module (ath10k_pci) to make it work. It used to work with 5.4.0-33. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent1800 F pulseaudio /dev/snd/controlC1: laurent1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 15:31:21 2020 InstallationDate: Installed on 2020-05-25 (21 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash 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: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 02MJVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883536/+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 1883010] Re: Lenovo-ThinkBook-14-IIL Touchpad not working
*** This bug is a duplicate of bug 1853277 *** https://bugs.launchpad.net/bugs/1853277 ** This bug has been marked a duplicate of bug 1853277 Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883010 Title: Lenovo-ThinkBook-14-IIL Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: The touchpad of this laptop does not seem to be supported. OS: Ubuntu 20.04 LTS Related: https://askubuntu.com/questions/1248939/lenovo-thinkbook-14-iil-touchpad-not-working https://askubuntu.com/questions/1215236/touch-pad-not-working-on-lenovo-thinkbook-14-iml https://askubuntu.com/questions/1245632/lenovo-thinkbook-iml-touchpad-not-recognized cat /proc/bus/input/devices does not list a device. This is the output: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=1d57 Product=0005 Version=0110 N: Name="HID 1d57:0005" P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:1D57:0005.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=5986 Product=2130 Version=5609 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA
[Kernel-packages] [Bug 1872198] Re: [HP Pavilion 17] Lost the use of the numeric keypad
[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/1872198 Title: [HP Pavilion 17] Lost the use of the numeric keypad Status in gnome-shell package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 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/gnome-shell/+bug/1872198/+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 1811236] Re: System wakes from suspend without user initialization
[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/1811236 Title: System wakes from suspend without user initialization Status in linux package in Ubuntu: Expired Bug description: I use `systemctl suspend` for taking my laptop to sleep. Suspend seems to work fine, but after a random amount of time, the system resumes without me pressing any buttons, moving a mouse etc. Some other methods have been attempted, but all end up with the same result, ie. system resumes unwanted. Here is a /var/log/syslog excerpt, hope I managed to grab everything valuable. The bug was filed with `ubuntu-bug linux- image-4.18.0-13-generic`, which is the linux image currently in use. Please let me know if something is missing due to incorrect package selection or otherwise. --- Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3067] manager: sleep: sleep requested (sleeping: no enabled: yes) Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3069] device (enp0s20f0u2c2): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3126] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3415] device (enp0s20f0u4): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Jan 10 13:48:35 caolila NetworkManager[869]: [1547120915.3453] manager: NetworkManager state is now ASLEEP Jan 10 13:48:35 caolila systemd[1]: Reached target Sleep. Jan 10 13:48:35 caolila systemd[1]: Starting Suspend... Jan 10 13:48:35 caolila whoopsie[1352]: [13:48:35] offline Jan 10 13:48:35 caolila systemd-sleep[32606]: Suspending system... Jan 10 13:48:35 caolila kernel: [19604.933999] PM: suspend entry (deep) Jan 10 13:48:35 caolila kernel: [19604.934001] PM: Syncing filesystems ... done. Jan 10 13:48:35 caolila wpa_supplicant[868]: nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0 Jan 10 13:53:55 caolila kernel: [19607.067269] Freezing user space processes ... (elapsed 0.004 seconds) done. Jan 10 13:53:55 caolila kernel: [19607.071592] OOM killer disabled. Jan 10 13:53:55 caolila kernel: [19607.071593] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 10 13:53:55 caolila kernel: [19607.072971] Suspending console(s) (use no_console_suspend to debug) Jan 10 13:53:55 caolila kernel: [19607.160541] e1000e: EEE TX LPI TIMER: 0011 Jan 10 13:53:55 caolila kernel: [19607.502557] thunderbolt :07:00.0: stopping RX ring 0 Jan 10 13:53:55 caolila kernel: [19607.502575] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) Jan 10 13:53:55 caolila kernel: [19607.502581] thunderbolt :07:00.0: stopping TX ring 0 Jan 10 13:53:55 caolila kernel: [19607.502605] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) Jan 10 13:53:55 caolila kernel: [19607.502608] thunderbolt :07:00.0: control channel stopped Jan 10 13:53:55 caolila kernel: [19607.502808] ACPI: EC: interrupt blocked Jan 10 13:53:55 caolila kernel: [19607.684603] ACPI: Preparing to enter system sleep state S3 Jan 10 13:53:55 caolila kernel: [19607.688265] ACPI: EC: event blocked Jan 10 13:53:55 caolila kernel: [19607.688267] ACPI: EC: EC stopped Jan 10 13:53:55 caolila kernel: [19607.688268] PM: Saving platform NVS memory Jan 10 13:53:55 caolila kernel: [19607.688301] Disabling non-boot CPUs ... Jan 10 13:53:55 caolila kernel: [19607.704406] IRQ 122: no longer affine to CPU1 Jan 10 13:53:55 caolila kernel: [19607.704426] IRQ 187: no longer affine to CPU1 Jan 10 13:53:55 caolila kernel: [19607.705447] smpboot: CPU 1 is now offline Jan 10 13:53:55 caolila kernel: [19607.728394] IRQ 189: no longer affine to CPU2 Jan 10 13:53:55 caolila kernel: [19607.729415] smpboot: CPU 2 is now offline Jan 10 13:53:55 caolila kernel: [19607.752349] IRQ 177: no longer affine to CPU3 Jan 10 13:53:55 caolila kernel: [19607.753377] smpboot: CPU 3 is now offline Jan 10 13:53:55 caolila kernel: [19607.780410] IRQ 179: no longer affine to CPU4 Jan 10 13:53:55 caolila kernel: [19607.781438] smpboot: CPU 4 is now offline Jan 10 13:53:55 caolila kernel: [19607.804344] IRQ 185: no longer affine to CPU5 Jan 10 13:53:55 caolila kernel: [19607.805385] smpboot: CPU 5 is now offline Jan 10 13:53:55 caolila kernel: [19607.828255] IRQ 183: no longer affine to CPU6 Jan 10 13:53:55 caolila kernel: [19607.828271] IRQ 195: no longer affine to CPU6 Jan 10 13:53:55 caolila kernel: [19607.830230] smpboot: CPU 6 is
[Kernel-packages] [Bug 1872375] Re: AMDGPU driver crashes when resuming from sleep if a ffmpeg-vaapi encoding backend is being used
[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/1872375 Title: AMDGPU driver crashes when resuming from sleep if a ffmpeg-vaapi encoding backend is being used Status in linux package in Ubuntu: Expired Bug description: Good morning, I'm writing this because is pretty much easily reproduceable in this hardware I discovered this when I set up an automatic permanent replay- recording in OBS, using FFMPEG VAAPI backend I usually put the system to sleep, and pretty much 100% of the times so far when OBS is recording something AND is using the ffmpeg-vaapi backend, putting the system to sleep and then waking it back, causes the amdgpu driver to crash no matter what Any other sleep/standby test made without recording using ffmpeg-vaapi (even using default ffmpeg software x264 backend) has not made the driver crash so far My setup: CPU: AMD Ryzen 5 1600 GPU: AMD Sapphire RX 580 8GB RAM: 12GB DDR4 (3x4GB) System: Ubuntu 20.04 Focal Fossa Desktop: GNOME 3.36.1 Kernel: 5.4.0-21-generic #25-Ubuntu Display server: X.org Here is the system crashing logs dmesg (Don't mind the hostname, it's a desktop PC not a thinkpad) Apr 13 01:49:02 haru-ThinkPad-T440s kernel: [ 64.100393] PM: suspend entry (deep) Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.108441] Filesystems sync: 0.008 seconds Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.108716] Freezing user space processes ... (elapsed 0.002 seconds) done. Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.111290] OOM killer disabled. Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.111291] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.112125] printk: Suspending console(s) (use no_console_suspend to debug) Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.113085] serial 00:04: disabled Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.113317] parport_pc 00:03: disabled Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151545] sd 0:0:0:0: [sda] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151713] sd 1:0:0:0: [sdc] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151720] sd 10:0:0:0: [sdd] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151724] sd 11:0:0:0: [sdb] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151807] sd 0:0:0:0: [sda] Stopping disk Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.152043] sd 1:0:0:0: [sdc] Stopping disk Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.157544] sd 10:0:0:0: [sdd] Stopping disk Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.612461] ACPI: Preparing to enter system sleep state S3 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.925094] PM: Saving platform NVS memory Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.925117] Disabling non-boot CPUs ... Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.927049] smpboot: CPU 1 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.931788] smpboot: CPU 2 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.934941] IRQ 37: no longer affine to CPU3 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.935968] smpboot: CPU 3 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.940098] smpboot: CPU 4 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.943503] IRQ 27: no longer affine to CPU5 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.943510] IRQ 28: no longer affine to CPU5 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.944533] smpboot: CPU 5 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.947662] IRQ 44: no longer affine to CPU6 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.948697] smpboot: CPU 6 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.952180] IRQ 30: no longer affine to CPU7 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.953216] smpboot: CPU 7 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.957820] smpboot: CPU 8 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.961177] IRQ 39: no longer affine to CPU9 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.961187] IRQ 63: no longer affine to CPU9 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.962201] smpboot: CPU 9 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.965160] IRQ 40: no longer affine to CPU10 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.966184] smpboot: CPU 10 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.970189]
[Kernel-packages] [Bug 1872198] Re: [HP Pavilion 17] Lost the use of the numeric keypad
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (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/1872198 Title: [HP Pavilion 17] Lost the use of the numeric keypad Status in gnome-shell package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 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/gnome-shell/+bug/1872198/+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 1883010] Re: Lenovo-ThinkBook-14-IIL Touchpad not working
** Tags added: hwe-touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883010 Title: Lenovo-ThinkBook-14-IIL Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: The touchpad of this laptop does not seem to be supported. OS: Ubuntu 20.04 LTS Related: https://askubuntu.com/questions/1248939/lenovo-thinkbook-14-iil-touchpad-not-working https://askubuntu.com/questions/1215236/touch-pad-not-working-on-lenovo-thinkbook-14-iml https://askubuntu.com/questions/1245632/lenovo-thinkbook-iml-touchpad-not-recognized cat /proc/bus/input/devices does not list a device. This is the output: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=1d57 Product=0005 Version=0110 N: Name="HID 1d57:0005" P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:1D57:0005.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=5986 Product=2130 Version=5609 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=11" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=
[Kernel-packages] [Bug 1883610] Re: Realtek RTL8821CE Wireless Adapter [10ec:c821] Subsystem [1a3b:3041] not found
It's currently driven by rtl8821ce-dkms. Please try install it by: $ sudo apt update && sudo apt install rtl8821ce-dkms ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: rtl8821ce (Ubuntu) Importance: Undecided Status: New ** Changed in: rtl8821ce (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/1883610 Title: Realtek RTL8821CE Wireless Adapter [10ec:c821] Subsystem [1a3b:3041] not found Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: Incomplete Bug description: I cant connect to wifi ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: percy 1087 F pulseaudio /dev/snd/controlC1: percy 1087 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Jun 16 00:53:54 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX705DT_FX705DT ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1eda916a-ff56-4d62-b848-244a474e6bcb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX705DT.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX705DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX705DT.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX705DT_FX705DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX705DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX705DT_FX705DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883610/+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 1883610] Re: Realtek RTL8821CE Wireless Adapter [10ec:c821] Subsystem [1a3b:3041] not found
** Summary changed: - No WIFI + Realtek RTL8821CE Wireless Adapter [10ec:c821] Subsystem [1a3b:3041] not found -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883610 Title: Realtek RTL8821CE Wireless Adapter [10ec:c821] Subsystem [1a3b:3041] not found Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: Incomplete Bug description: I cant connect to wifi ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: percy 1087 F pulseaudio /dev/snd/controlC1: percy 1087 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Jun 16 00:53:54 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX705DT_FX705DT ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1eda916a-ff56-4d62-b848-244a474e6bcb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX705DT.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX705DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX705DT.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX705DT_FX705DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX705DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX705DT_FX705DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883610/+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 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed
Found on Focal KVM 5.4.0-1016.16 ** Tags added: sru-20200608 ** Tags added: 5.4 focal -- 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/1834006 Title: cpuset_hotplug from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux source package in Disco: New Status in linux-aws source package in Disco: New Bug description: Issue found on node amaura: <<>> tag=cpuset_hotplug stime=1561372131 cmdline="cpuset_hotplug_test.sh" contacts="" analysis=exit <<>> incrementing stop cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, Expect: 0-7) cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, Expect: 0-7). cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded. cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded. <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=19 cstime=81 <<>> Test script: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 24 10:25 seq crw-rw 1 root audio 116, 33 Jun 24 10:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 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: Date: Mon Jun 24 10:30:59 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+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 1834417] Re: EDAC driver support for Idaville
18344171dc78f1ffa3a386b986b659884952d816021f38f
5c5d3ac2064ae2466c81d40186bcc09b2d5b7892
c4a1dd9e83ceceef6ffba82b8b274ab9b929ea14
Fix patches have been merged to v5.8-rc1. So close the JIRA.
ee5340abab3b ("EDAC, {skx,i10nm}: Make some configurations CPU model specific")
ce20670828c1 ("EDAC/i10nm: Update driver to support different bus number config
register offsets")
v5.8-rc1
** Changed in: intel
Status: Fix Released => Fix Committed
** Description changed:
Description:
Provide detailed memory topology and configuration information as well as
translating error addresses to physical DIMM addresses.
- Target Release: 19.10
- Target Kernel:5.3
+ Target Release: 20.10
+ Target Kernel:5.8
** Tags removed: intel-kernel-19.10
** Tags added: intel-kernel-20.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834417
Title:
EDAC driver support for Idaville
Status in intel:
Fix Committed
Status in linux package in Ubuntu:
Incomplete
Bug description:
Description:
Provide detailed memory topology and configuration information as well as
translating error addresses to physical DIMM addresses.
Target Release: 20.10
Target Kernel:5.8
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1834417/+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 1875456] Re: Azure diagnostic/serviceability improvement
Cover letter for the SRU submission: https://lists.ubuntu.com/archives
/kernel-team/2020-June/111061.html
--
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/1875456
Title:
Azure diagnostic/serviceability improvement
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
New
Bug description:
Microsoft would like to request the inclusion of commits in all
releases supported on Azure. These commits will enable reporting 4
Kbytes of dmesg information to Hyper-V when Linux takes a panic.
Microsoft would like to get all releases reporting this information,
so that we can automatically get a rich picture of Linux panics in
Azure. This will limit the need get serial console logs or other
steps to manually acquire debug info.
We would like to request the folloiwng commits to enable the
diagnostic/serviceability improvement:
f3a99e761efa ("x86/Hyper-V: Report crash data in die() when panic_on_oops is
set")
040026df7088 ("x86/Hyper-V: Report crash register data when
sysctl_record_panic_msg is not set")
a11589563e96 ("x86/Hyper-V: Report crash register data or kmsg before running
crash kernel")
73f26e526f19 ("x86/Hyper-V: Trigger crash enlightenment only once during
system crash.")
7f11a2cc10a4 ("x86/Hyper-V: Free hv_panic_page when fail to register kmsg
dump")
74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback")
8afc06dd75c0 ("Drivers: hv: vmbus: Fix the issue with freeing up
hv_ctl_table_hdr")
ddcaf3ca4c3c ("Drivers: hv: vmus: Fix the check for return value from kmsg
get dump buffer")
81b18bce48af ("Drivers: HV: Send one page worth of kmsg dump over Hyper-V
during panic")
7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1875456/+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 1875456] Re: Azure diagnostic/serviceability improvement
The changes are only necessary for 4.15. 5.4 and 5.3 already have all
the chances via mainline or upstream stable updates.
** Also affects: linux-azure-4.15 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-azure-4.15 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Bionic)
Status: New => Invalid
--
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/1875456
Title:
Azure diagnostic/serviceability improvement
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
New
Bug description:
Microsoft would like to request the inclusion of commits in all
releases supported on Azure. These commits will enable reporting 4
Kbytes of dmesg information to Hyper-V when Linux takes a panic.
Microsoft would like to get all releases reporting this information,
so that we can automatically get a rich picture of Linux panics in
Azure. This will limit the need get serial console logs or other
steps to manually acquire debug info.
We would like to request the folloiwng commits to enable the
diagnostic/serviceability improvement:
f3a99e761efa ("x86/Hyper-V: Report crash data in die() when panic_on_oops is
set")
040026df7088 ("x86/Hyper-V: Report crash register data when
sysctl_record_panic_msg is not set")
a11589563e96 ("x86/Hyper-V: Report crash register data or kmsg before running
crash kernel")
73f26e526f19 ("x86/Hyper-V: Trigger crash enlightenment only once during
system crash.")
7f11a2cc10a4 ("x86/Hyper-V: Free hv_panic_page when fail to register kmsg
dump")
74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback")
8afc06dd75c0 ("Drivers: hv: vmbus: Fix the issue with freeing up
hv_ctl_table_hdr")
ddcaf3ca4c3c ("Drivers: hv: vmus: Fix the check for return value from kmsg
get dump buffer")
81b18bce48af ("Drivers: HV: Send one page worth of kmsg dump over Hyper-V
during panic")
7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1875456/+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 1883610] Re: No WIFI
** 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/1883610 Title: No WIFI Status in linux package in Ubuntu: Confirmed Bug description: I cant connect to wifi ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: percy 1087 F pulseaudio /dev/snd/controlC1: percy 1087 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Jun 16 00:53:54 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX705DT_FX705DT ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1eda916a-ff56-4d62-b848-244a474e6bcb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX705DT.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX705DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX705DT.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX705DT_FX705DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX705DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX705DT_FX705DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883610/+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 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
** Changed in: oem-priority Status: In Progress => 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/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Incomplete Status in gnome-session package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+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 1853061] Re: Connection to USB-C hub frequently drops when charging over it
I am now running Ubuntu 20.04 with kernel version 5.4.0-37-generic and have reproduced the bug after running the command # echo "file drivers/pci/* +p" > /sys/kernel/debug/dynamic_debug/control as was requested. Attached is the dmesg log. Attached to the Thunderbolt hub are an iphone and an external monitor. The connection drops a couple times over the period of the log. ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853061/+attachment/5384224/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853061 Title: Connection to USB-C hub frequently drops when charging over it Status in linux package in Ubuntu: Confirmed Bug description: I am running Ubuntu 19.10 on a Lenovo Thinkpad X1 Extreme. I have a CalDigit TS3 Plus USB-C hub connected to one of the laptop's USB-C/Thunderbolt ports. The laptop supports charging over USB-C. When I try to charge from the hub over USB-C, Ubuntu seems to frequently "drop" the connection to the hub and loses connection to the stuff attached to the hub (e.g., an external monitor connected to the hub by USB-C to displayport, an ethernet connection, and USB devices). After a few seconds, the computer reconnects to these devices. I disabled TLP but the problem persists. When I have the laptop's power adapter attached in addition to the USB-C hub, the problem does not appear and the computer does not lose connection to the peripherals. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: matt 2211 F pulseaudio /dev/snd/controlC1: matt 2211 F pulseaudio /dev/snd/controlC0: matt 2211 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 13:44:33 2019 InstallationDate: Installed on 2019-09-04 (75 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20MGS1YW00 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=3a5c73f9-5be3-4590-88a9-e362d949931c ro quiet splash resume=UUID=d464672d-224c-4149-a105-3a0cad515692 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-21 (28 days ago) dmi.bios.date: 08/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET42W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MGS1YW00 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:bvrN2EET42W(1.24):bd08/06/2019:svnLENOVO:pn20MGS1YW00:pvrThinkPadX1Extreme:rvnLENOVO:rn20MGS1YW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MGS1YW00 dmi.product.sku: LENOVO_MT_20MG_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853061/+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 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
I'll have to give the computer to it's user in a few days. After that I won't have the possibility to do extensive debugging. So if you have any ideas for testing, please tell me! I just tested Linux-5.8.0-rc1 but it didn't solved the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA=ABD=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 9YN58EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881494/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1831587] Re: brightness control not work with OLED panel
@Adam, Egbert What kernel version are you using? I'd expect 5.4 in Focal or Bionic should have already fixed this issue. ** Changed in: linux (Ubuntu) Status: Triaged => 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/1831587 Title: brightness control not work with OLED panel Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: image: disco 19.04 kernel: 5.0.0-15-generic also verified failed on linux-image-unsigned-5.2.0-050200rc2-generic also refer to : - https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness - https://bugs.freedesktop.org/show_bug.cgi?id=97883 Linux can not control the brightness on the OLED panel in the traditional way [1]. Although there's a workaround from the community [2] that to execute script while brightness hotkey event is triggered. But if we want to upstream it, it's still a problem to recognize the OLED panel so that the system knows when to go workaround. - EDID of my laptop which has OLED: https://paste.ubuntu.com/p/w7rVqJTYDy/ - EDID of the same model without OLED: https://paste.ubuntu.com/p/P3ChhX9yBJ/ there's a kernel patch related OLED for reference: - https://patchwork.kernel.org/patch/6133471/ [1] https://wiki.ubuntu.com/Kernel/Debugging/Backlight [2] https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831587/+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 1871589] Re: Add DCPD backlight support for HP CML system
** Changed in: hwe-next Status: New => 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/1871589 Title: Add DCPD backlight support for HP CML system Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: [Impact] PWM backlight doesn't work on an upcoming HP CML system. [Fix] Use DPCD to control backlight instead of PWM. [Test] With this patch applied, changing backlight sysfs can change the brightness. [Regression Potential] Low. This is specific to panel ID, which is unique. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1871589/+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 1883610] [NEW] No WIFI
Public bug reported: I cant connect to wifi ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: percy 1087 F pulseaudio /dev/snd/controlC1: percy 1087 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Jun 16 00:53:54 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX705DT_FX705DT ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1eda916a-ff56-4d62-b848-244a474e6bcb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX705DT.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX705DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX705DT.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX705DT_FX705DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX705DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX705DT_FX705DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883610 Title: No WIFI Status in linux package in Ubuntu: Confirmed Bug description: I cant connect to wifi ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: percy 1087 F pulseaudio /dev/snd/controlC1: percy 1087 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Jun 16 00:53:54 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX705DT_FX705DT ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1eda916a-ff56-4d62-b848-244a474e6bcb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX705DT.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX705DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX705DT.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX705DT_FX705DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX705DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX705DT_FX705DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883610/+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 1883610] 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/1883610 Title: No WIFI Status in linux package in Ubuntu: Confirmed Bug description: I cant connect to wifi ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: percy 1087 F pulseaudio /dev/snd/controlC1: percy 1087 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Jun 16 00:53:54 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX705DT_FX705DT ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1eda916a-ff56-4d62-b848-244a474e6bcb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX705DT.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX705DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX705DT.308:bd09/19/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX705DT_FX705DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX705DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX705DT_FX705DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883610/+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 1882823] Re: int3403 thermal INT3403:00
A patch was sent for reviews: https://marc.info/?l=linux- pm=159226080621530=2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882823 Title: int3403 thermal INT3403:00 Status in linux package in Ubuntu: Confirmed Bug description: [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91] [ 10.121722] int3403 thermal INT3403:00: Unsupported event [0x91] [ 12.165233] int3403 thermal INT3403:00: Unsupported event [0x91] Is constantly flooding my dmesg. I believe this is also due to missing audio drivers as well. Which is another issue that I am facing. Realtek ALC1220 Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882823/+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 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298
** Package changed: alsa-driver (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/1834566 Title: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298 Status in linux package in Ubuntu: Confirmed Bug description: Unable to get system speakers working running 19.04. At max volume, sound is barely perceptible through headphones. Pavucontrol shows sounds is present, but no amount of adjustments makes a difference. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 3355 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 28 00:44:13 2019 InstallationDate: Installed on 2019-06-05 (22 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AHK.029.190425.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP930MBE-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: Notebook 9 Series dmi.product.name: 930MBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK dmi.product.version: P02AHK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834566/+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 1883597] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384164/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic
[Kernel-packages] [Bug 1883597] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384170/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384162/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384174/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384165/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384168/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384176/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384171/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384173/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic
[Kernel-packages] [Bug 1883597] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384166/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384179/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions:
[Kernel-packages] [Bug 1883597] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384177/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic
[Kernel-packages] [Bug 1883597] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384172/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384169/+files/WifiSyslog.txt ** Description changed: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro + --- + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq + crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.23 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a + InstallationDate: Installed on 2019-02-22 (479 days ago) + InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd + Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub + Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Supermicro SSG-6029P-E1CR12L + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M + ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-184-generic N/A + linux-backports-modules-4.4.0-184-generic N/A + linux-firmware 1.157.23 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.4.0-184-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + +
[Kernel-packages] [Bug 1883597] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384163/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384178/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A
[Kernel-packages] [Bug 1883597] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384167/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPH-T dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: dmi.product.name: SSG-6029P-E1CR12L dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic
[Kernel-packages] [Bug 1883597] Re: Kernel 4.4.0-184 hangs when issuing tc qdisc command
apport information ** Tags added: apport-collected xenial ** Description changed: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. + --- + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq + crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.23 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a + InstallationDate: Installed on 2019-02-22 (479 days ago) + InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd + Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub + Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Supermicro SSG-6029P-E1CR12L + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0 nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M + ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-184-generic N/A + linux-backports-modules-4.4.0-184-generic N/A + linux-firmware 1.157.23 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.4.0-184-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 02/27/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2.0b + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: X11DPH-T + dmi.board.vendor: Supermicro + dmi.board.version: 1.01 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 1 + dmi.chassis.vendor: Supermicro + dmi.chassis.version: 0123456789 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789: + dmi.product.name: SSG-6029P-E1CR12L + dmi.product.version: 0123456789 + dmi.sys.vendor: Supermicro ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1883597/+attachment/5384161/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Confirmed Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a InstallationDate: Installed on 2019-02-22 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro SSG-6029P-E1CR12L Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic
[Kernel-packages] [Bug 1834566] [NEW] Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298
You have been subscribed to a public bug: Unable to get system speakers working running 19.04. At max volume, sound is barely perceptible through headphones. Pavucontrol shows sounds is present, but no amount of adjustments makes a difference. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 3355 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 28 00:44:13 2019 InstallationDate: Installed on 2019-06-05 (22 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AHK.029.190425.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP930MBE-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: Notebook 9 Series dmi.product.name: 930MBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK dmi.product.version: P02AHK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298 https://bugs.launchpad.net/bugs/1834566 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 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
Hi Guilherme,
Thanks for your reply.
No need for an exact ETA, but can you give me some sort of feeling, maybe how
often do these amis get released? once a month? 2 months?
Cheers,
Arthur
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/187
Title:
Bionic ubuntu ethtool doesn't check ring parameters boundaries
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
* There's a bad behavior in the ena driver ringparam setting on kernels 4.4
and 4.15, if an invalid ringparam is provided to ethtool.
* Upstream Linux kernel implemented ring parameter boundaries check in
commit: 37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds
during SRINGPARAM") [ git.kernel.org/linus/37e2d99b59c4 ].
Due to this commit, the community doesn't usually allow ring parameter
boundary checks in driver code.
* Xenial/Bionic kernels don't include this patch, and some network
drivers (like ena) rely on this patch for boundary checking of ring
params. So, we are hereby requesting the commit inclusion in these
kernel versions.
[Test case]
1. In AWS, create a new c5.4xlarge instance with the Ubuntu 18.04 official
ami (uses the ENA network driver) and update to latest kernel/reboot.
2. Run ethtool -g ens5
output:
Ring parameters for ens5:
Pre-set maximums:
RX: 16384
RX Mini: 0
RX Jumbo: 0
TX: 1024
Current hardware settings:
RX: 1024
RX Mini: 0
RX Jumbo: 0
TX: 1024
3. Change the TX/RX ring size to a legal number within boundaries -
works!
4. Change the TX/RX ring size to an illegal number (such as 2048 for
TX) with the command - "sudo ethtool -G ens5 tx 2048".
Expected behavior - "Cannot set device ring parameters: Invalid argument"
Actual behavior - causes a driver hang since boundaries are not checked by
ethtool, effectively hanging the instance (given that AWS has no console to
allow system manipulation).
[Regression Potential]
Since that the commit is present in kernels v4.16+ (including Ubuntu)
and is quite small and self-contained, the regression risk is very
reduced.
One potential "regression" would be if some driver has bugs and
provide bad values on get_ringparams, then the validation would be
broken (allowing illegal values or refusing legal ones), but this
wouldn't be a regression in the hereby proposed patch itself, it'd be
only exposed by the patch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+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 1883597] 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 1883597 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: Incomplete Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883597/+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 1883598] 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 1883598 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883598 Title: efi: Restrict efivar_ssdt_load when the kernel is locked down Status in linux package in Ubuntu: Incomplete Bug description: Upstream git commit 1957a85b0032 needs to be backported to older releases: efi: Restrict efivar_ssdt_load when the kernel is locked down efivar_ssdt_load allows the kernel to import arbitrary ACPI code from an EFI variable, which gives arbitrary code execution in ring 0. Prevent that when the kernel is locked down. Code introduced in 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f break-fix: 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f 1957a85b0032a81e6482ca4aab883643b8dae06e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883598/+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 1883598] Re: efi: Restrict efivar_ssdt_load when the kernel is locked down
** Description changed: Upstream git commit 1957a85b0032 needs to be backported to older releases: efi: Restrict efivar_ssdt_load when the kernel is locked down efivar_ssdt_load allows the kernel to import arbitrary ACPI code from an EFI variable, which gives arbitrary code execution in ring 0. Prevent that when the kernel is locked down. + + Code introduced in 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f + + break-fix: 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f + 1957a85b0032a81e6482ca4aab883643b8dae06e -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883598 Title: efi: Restrict efivar_ssdt_load when the kernel is locked down Status in linux package in Ubuntu: New Bug description: Upstream git commit 1957a85b0032 needs to be backported to older releases: efi: Restrict efivar_ssdt_load when the kernel is locked down efivar_ssdt_load allows the kernel to import arbitrary ACPI code from an EFI variable, which gives arbitrary code execution in ring 0. Prevent that when the kernel is locked down. Code introduced in 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f break-fix: 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f 1957a85b0032a81e6482ca4aab883643b8dae06e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883598/+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 1883597] [NEW] Kernel 4.4.0-184 hangs when issuing tc qdisc command
Public bug reported: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apport.linux-image-4.4.0-184-generic.5fnlmlqp.apport" https://bugs.launchpad.net/bugs/1883597/+attachment/5384147/+files/apport.linux-image-4.4.0-184-generic.5fnlmlqp.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: New Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883597/+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 1883598] [NEW] efi: Restrict efivar_ssdt_load when the kernel is locked down
*** This bug is a security vulnerability *** Public security bug reported: Upstream git commit 1957a85b0032 needs to be backported to older releases: efi: Restrict efivar_ssdt_load when the kernel is locked down efivar_ssdt_load allows the kernel to import arbitrary ACPI code from an EFI variable, which gives arbitrary code execution in ring 0. Prevent that when the kernel is locked down. Code introduced in 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f break-fix: 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f 1957a85b0032a81e6482ca4aab883643b8dae06e ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Upstream git commit 1957a85b0032 needs to be backported to older releases: - efi: Restrict efivar_ssdt_load when the kernel is locked down + efi: Restrict efivar_ssdt_load when the kernel is locked down - efivar_ssdt_load allows the kernel to import arbitrary ACPI code from an - EFI variable, which gives arbitrary code execution in ring 0. Prevent - that when the kernel is locked down. + efivar_ssdt_load allows the kernel to import arbitrary ACPI code from an + EFI variable, which gives arbitrary code execution in ring 0. Prevent + that when the kernel is locked down. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883598 Title: efi: Restrict efivar_ssdt_load when the kernel is locked down Status in linux package in Ubuntu: New Bug description: Upstream git commit 1957a85b0032 needs to be backported to older releases: efi: Restrict efivar_ssdt_load when the kernel is locked down efivar_ssdt_load allows the kernel to import arbitrary ACPI code from an EFI variable, which gives arbitrary code execution in ring 0. Prevent that when the kernel is locked down. Code introduced in 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f break-fix: 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f 1957a85b0032a81e6482ca4aab883643b8dae06e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883598/+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 1883597] Re: Kernel 4.4.0-184 hangs when issuing tc qdisc command
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883597/+attachment/5384149/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: New Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883597/+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 1883597] Re: Kernel 4.4.0-184 hangs when issuing tc qdisc command
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883597/+attachment/5384148/+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/1883597 Title: Kernel 4.4.0-184 hangs when issuing tc qdisc command Status in linux package in Ubuntu: New Bug description: On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate 25mbit" causes CPU lockup (NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394]) This does not occur on 4.4.0.179 or earlier. Happens on both a intel i40e driver and ixgbe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
Hi @chenrongwen and @tonihu, thanks for the reports! Could you please try makedumpfile version 1:1.6.7-1ubuntu2.1, available on -proposed pocket? There's an ARM64-specific fix there that might solve your problem. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! Guilherme ** Changed in: makedumpfile (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Bug description: OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+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 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
Gentle bump to raise visibility. If more information is needed, please let me know. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+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 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake
What else is needed here? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1874933 Title: Performance workaround for Dell 7390 2-in-1 Ice Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Incomplete Bug description: == SRU justification focal == As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4 kernel. The 5.4 kernel added support for "Processor thermal device", for Ice Lake, which will expose the power tables (via PPCC). This system default "max RAPL long term power limit" is 15W. But this power table is specifying as 9W. So thermald will limit power to 9W. If dptfxtract is executed, then power limit will be higher than power up value, but most of the users will use out of the box setup. So this need a workaround. This workaround will ignore any power limit less than the power up power limit. This is addressed in thermald 2.1 with two commits: https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861 I know 20.04 LTS uses 1.9.1. I can assist in backport if required. == Fix == Two upstream commits to ease backporting: - eeadf7d2efe Restore to min state on deactivation without depending on hardware state - 9a6dc27879a Clean up the code and documentation Two upstream commits for the fix: - f7db4342933 Avoid polling power in non PPCC case - c3461690eaf Ignore invalid PPCC max power limit == Test case == As reported here: https://www.phoronix.com/forums/forum/linux- graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice- lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream == Regression Potential == This fix involves changing the power limits logic so there is a potential that this may affect change the throttling behaviour of other systems with poorly defined PPCC power tables because it now ignores the power limits less than the power up limits. Users will see their machines run faster and hence active cooling may crank up (e.g. fans) but I think the speed improvement outweighs the noise factor. Note that these changes are already in thermald 2.1 that is now in Ubuntu Groovy 20.10. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1874933/+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 1869465] Autopkgtest regression report (makedumpfile/1:1.6.5-1ubuntu1~18.04.5)
All autopkgtests for the newly accepted makedumpfile (1:1.6.5-1ubuntu1~18.04.5) for bionic have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.5-1ubuntu1~18.04.5 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+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 1869465] Autopkgtest regression report (makedumpfile/1:1.6.6-2ubuntu2.1)
All autopkgtests for the newly accepted makedumpfile (1:1.6.6-2ubuntu2.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.6-2ubuntu2.1 (ppc64el, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#makedumpfile [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+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 1877955] Comment bridged from LTC Bugzilla
--- Comment From naynj...@ibm.com 2020-06-15 13:48 EDT---
Would start to test it today.
Thanks & Regards,
- Nayna
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877955
Title:
Fix for secure boot rules in IMA arch policy on powerpc
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Currently the kernel module appended signature is verified twice
(finit_module) - once by the module_sig_check() and again by IMA.
* To prevent this the powerpc secure boot rules define an IMA
architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
not enabled.
* But this doesn't take the ability into account of enabling
"sig_enforce" at the boot command line (module.sig_enforce=1).
* Including the IMA module appraise rule results in failing the
finit_module syscall, unless the module signing public key is loaded
onto the IMA keyring.
* This patch fixes secure boot policy rules to be based on
CONFIG_MODULE_SIG instead.
[Fix]
* fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
Fix secure boot rules in ima arch policy"
[Test Case]
* Perform a secure boot on a powerpc system with
'module.sig_enforce=1' set at the boot command.
* If the IMA module appraise rule is included, the finit_module
syscall will fail (unless the module signing public key got loaded
onto the IMA keyring) without having the patch in place.
* The verification needs to be done by the IBM Power team.
[Regression Potential]
* There is (always) a certain regression risk with having code
changes, especially in the secure boot area.
* But this patch is limited to the powerpc platform and will not
affect any other architecture.
* It got discussed at
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
before it became finally upstream accepted with kernel 5.7-rc7.
* The secure boot code itself wasn't really touched, rather than it's basis
for execution.
The IMA policy rule for module appraisal is now added only if
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
Hence the change is very limited and straightforward.
[Other]
* Since the patch got upstream with 5.7-rc7, it is already in groovy, hence
this SRU is for focal only.
__
== Comment: #0 - Michael Ranweiler - 2020-04-22
14:44:31 ==
+++ This bug was initially created as a clone of Bug #184073 +++
This bug is a follow on to LP 1866909 to address a missing piece -
only half the following patch was included in 5.4.0-24.28.
The upstream patch has an additional fix but it?s not critical for GA.
It can get included as part of bug fixes. It also affects only power.
The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
posted to linux-integrity and linuxppc-dev mailing list
(https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
email-na...@linux.ibm.com/T/#u)
If there are any issues identified during further testing, they will
get opened as separate issue to be addressed later.
Thanks & Regards,
- Nayna
== Comment: #4 - Michael Ranweiler - 2020-05-11
02:23:35 ==
Updated posting:
https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
email-na...@linux.ibm.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1877955/+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 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
Hi Arthur, I discussed this topic today with the responsible for AMIs on
AWS, and I was then told that new AMIs should be built for testing next
hours. After internal testing, they should get released, I don't have an
ETA.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/187
Title:
Bionic ubuntu ethtool doesn't check ring parameters boundaries
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
* There's a bad behavior in the ena driver ringparam setting on kernels 4.4
and 4.15, if an invalid ringparam is provided to ethtool.
* Upstream Linux kernel implemented ring parameter boundaries check in
commit: 37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds
during SRINGPARAM") [ git.kernel.org/linus/37e2d99b59c4 ].
Due to this commit, the community doesn't usually allow ring parameter
boundary checks in driver code.
* Xenial/Bionic kernels don't include this patch, and some network
drivers (like ena) rely on this patch for boundary checking of ring
params. So, we are hereby requesting the commit inclusion in these
kernel versions.
[Test case]
1. In AWS, create a new c5.4xlarge instance with the Ubuntu 18.04 official
ami (uses the ENA network driver) and update to latest kernel/reboot.
2. Run ethtool -g ens5
output:
Ring parameters for ens5:
Pre-set maximums:
RX: 16384
RX Mini: 0
RX Jumbo: 0
TX: 1024
Current hardware settings:
RX: 1024
RX Mini: 0
RX Jumbo: 0
TX: 1024
3. Change the TX/RX ring size to a legal number within boundaries -
works!
4. Change the TX/RX ring size to an illegal number (such as 2048 for
TX) with the command - "sudo ethtool -G ens5 tx 2048".
Expected behavior - "Cannot set device ring parameters: Invalid argument"
Actual behavior - causes a driver hang since boundaries are not checked by
ethtool, effectively hanging the instance (given that AWS has no console to
allow system manipulation).
[Regression Potential]
Since that the commit is present in kernels v4.16+ (including Ubuntu)
and is quite small and self-contained, the regression risk is very
reduced.
One potential "regression" would be if some driver has bugs and
provide bad values on get_ringparams, then the validation would be
broken (allowing illegal values or refusing legal ones), but this
wouldn't be a regression in the hereby proposed patch itself, it'd be
only exposed by the patch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+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 1869465] Please test proposed package
Hello chenrongwen, or anyone else affected, Accepted makedumpfile into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.3-2~16.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+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 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Hello chenrongwen, or anyone else affected, Accepted makedumpfile into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.7-1ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: makedumpfile (Ubuntu Eoan) Status: New => Fix Committed ** Tags added: verification-needed-eoan -- 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/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1869465] Please test proposed package
Hello chenrongwen, or anyone else affected, Accepted makedumpfile into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- 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/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+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 1869465] Please test proposed package
Hello chenrongwen, or anyone else affected, Accepted makedumpfile into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.6-2ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- 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/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
> Before you have to scrap the notebook... > http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/current/grubx64.efi.signed > is much newer, but should also work. For the moment this is true. But it is not guaranteed that the latest published grub in xenial-updates will support booting unsigned kernels. The intention is that in the near future it will NOT support booting unsigned kernels when SecureBoot is enabled. So it is probably better to grab the one from the release pocket: http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed ** Description changed: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. + If you have applied updates, and find that you can not boot the above + fixed kernel because of Secure Boot and that the kernel is unsigned, but + can still boot another kernel for your system; here's what you can do: - If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: - - 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed: - $ wget http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed - + 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: + $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
still using llvmpipe, if there is any debugging i could do just tell me -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+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 1883472] Re: linux-image-5.4.0-37-generic freezes on idle. linux-image-5.4.0-33-generic works fine.
After some more testing I verified this only happens when it tries to power off the monitor. I can confirm that disabling the quick monitor power-off and the power management in the screensaver settings makes the kernel work stable. Again, this feature works OK on linux- image-5.4.0-33-generic ** Description changed: linux-image-5.4.0-33-generic Works OK linux-image-5.4.0-37-generic Freezes when leaving idle for some time. Ubuntu 20.04LTS 64 bits. Fully updated. Hardware: AMD Ryzen 7 1800X 32GB RAM (two sticks: Part number KHX2666C16/16G) Asus PRIME A320M-K - latest BIOS installed AMD Radeon R9 390X 8GB NVMe SSD 512GB (I don't recall the brand) Tried AMDGPU and RADEON drivers for the video card. The issue persists. I was not able to find any logs nor kernel panics on the usual log files. Booting the older kernel makes the machine work perfectly stable as before. Most of the time I come back to a black screen. Other times is partially dimmed, like when entering into power save mode, when the screensaver kicks in to shut down the monitor. - Disabling power management did not fix the issue. I will try disabling - the ability to shut down the monitor. + WORKAROUND: + Disabling the ability to shut down the monitor "fixes" the problem. + + In the xscreensaver settings I disabled quick power-off and also + disabled power management, so it never tries to power off the monitor. + Now the system is stable again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1883472 Title: linux-image-5.4.0-37-generic freezes on idle. linux- image-5.4.0-33-generic works fine. Status in linux-signed package in Ubuntu: New Bug description: linux-image-5.4.0-33-generic Works OK linux-image-5.4.0-37-generic Freezes when leaving idle for some time. Ubuntu 20.04LTS 64 bits. Fully updated. Hardware: AMD Ryzen 7 1800X 32GB RAM (two sticks: Part number KHX2666C16/16G) Asus PRIME A320M-K - latest BIOS installed AMD Radeon R9 390X 8GB NVMe SSD 512GB (I don't recall the brand) Tried AMDGPU and RADEON drivers for the video card. The issue persists. I was not able to find any logs nor kernel panics on the usual log files. Booting the older kernel makes the machine work perfectly stable as before. Most of the time I come back to a black screen. Other times is partially dimmed, like when entering into power save mode, when the screensaver kicks in to shut down the monitor. WORKAROUND: Disabling the ability to shut down the monitor "fixes" the problem. In the xscreensaver settings I disabled quick power-off and also disabled power management, so it never tries to power off the monitor. Now the system is stable again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1883472/+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 1878271] Re: rpi: no uboot or kernel boot mesages on console during boot on core20
Based on Daves comment I set this to invalid. ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1878271 Title: rpi: no uboot or kernel boot mesages on console during boot on core20 Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: Invalid Bug description: I'm currently testing the image from http://cdimage.ubuntu.com/ubuntu- core/20/beta/20200512.3/ on rpi4-4GB. Normally, we would expect to see uboot prompt on screen, as well as kernel boot messages - as well as on serial. I see all of this coming over serial, but nothing on the screen until the system is completely booted. Current kernel version and snaps in this image are: $ uname -a Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux $ snap list Name VersionRev Tracking Publisher Notes core20 20 635 latest/beta canonical✓ base pi 20-1 5820/beta canonical✓ gadget pi-kernel 5.4.0-1011.11 154 20/beta canonical✓ kernel snapd 2.45 7780 latest/beta canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1878271/+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 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
Please test the v2 kernel: https://people.canonical.com/~hwang4/lp1850876/v2/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+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 1883553] [NEW] Groovy update: v5.7.2 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.7.2 upstream stable release from git://git.kernel.org/ Linux 5.7.2 uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned x86/speculation: Add Ivy Bridge to affected list x86/speculation: Add SRBDS vulnerability and mitigation documentation x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation x86/cpu: Add 'table' argument to cpu_matches() x86/cpu: Add a steppings field to struct x86_cpu_id nvmem: qfprom: remove incorrect write support CDC-ACM: heed quirk also in error handling staging: rtl8712: Fix IEEE80211_ADDBA_PARAM_BUF_SIZE_MASK tty: hvc_console, fix crashes on parallel open/close vt: keyboard: avoid signed integer overflow in k_ascii serial: 8250: Enable 16550A variants by default on non-x86 usb: musb: jz4740: Prevent lockup when CONFIG_SMP is set usb: musb: Fix runtime PM imbalance on error usb: musb: start session in resume for host port iio: adc: stm32-adc: fix a wrong error message when probing interrupts iio:chemical:pms7003: Fix timestamp alignment and prevent data leak. iio: vcnl4000: Fix i2c swapped word reading. iio:chemical:sps30: Fix timestamp alignment USB: serial: ch341: fix lockup of devices with limited prescaler USB: serial: ch341: add basis for quirk detection USB: serial: option: add Telit LE910C1-EUX compositions USB: serial: usb_wwan: do not resubmit rx urb on fatal errors USB: serial: qcserial: add DW5816e QDL support ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: 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/1883553 Title: Groovy update: v5.7.2 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: 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.7.2 upstream stable release from git://git.kernel.org/ Linux 5.7.2 uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned x86/speculation: Add Ivy Bridge to affected list x86/speculation: Add SRBDS vulnerability and mitigation documentation x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation x86/cpu: Add 'table' argument to cpu_matches() x86/cpu: Add a steppings field to struct x86_cpu_id nvmem: qfprom: remove incorrect write support CDC-ACM: heed quirk also in error handling staging: rtl8712: Fix IEEE80211_ADDBA_PARAM_BUF_SIZE_MASK tty: hvc_console, fix crashes on parallel open/close vt: keyboard: avoid signed integer overflow in k_ascii serial: 8250: Enable 16550A variants by default on non-x86 usb: musb: jz4740: Prevent lockup when CONFIG_SMP is set usb: musb: Fix runtime PM imbalance on error usb: musb: start session in resume for host port iio: adc: stm32-adc: fix a wrong error message when probing interrupts iio:chemical:pms7003: Fix timestamp alignment and prevent data leak. iio: vcnl4000: Fix i2c swapped word reading. iio:chemical:sps30: Fix timestamp alignment USB: serial: ch341: fix lockup of devices with limited prescaler USB: serial: ch341: add basis for quirk detection USB: serial: option: add Telit LE910C1-EUX compositions USB: serial: usb_wwan: do not resubmit rx urb on fatal errors USB: serial: qcserial: add DW5816e QDL support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883553/+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 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
the clk_raspberrypi is not enabled in the kernel, let me build a new testing kernel to enable it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+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 1883536] 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/1883536 Title: Wifi does not work after suspend Status in linux package in Ubuntu: Confirmed Bug description: After I resume from suspend, Wifi does not work. I have to reload the module (ath10k_pci) to make it work. It used to work with 5.4.0-33. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent1800 F pulseaudio /dev/snd/controlC1: laurent1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 15:31:21 2020 InstallationDate: Installed on 2020-05-25 (21 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash 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: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 02MJVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883536/+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 1879290] Re: pc: no message on the screen for ~30s on fast HW
Result of systemd-analyze in both systems on the Thinkcentre machine: uc18: Startup finished in 30.880s (kernel) + 4.727s (userspace) = 35.608s graphical.target reached after 4.721s in userspace uc20: Startup finished in 38.338s (kernel) + 17.902s (userspace) = 56.240s graphical.target reached after 17.892s in userspace -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879290 Title: pc: no message on the screen for ~30s on fast HW Status in linux package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: The boot on real HW (ARock B450, Ryzen, NVME 240Gb) takes a long time without any visible feedback. Video: https://photos.app.goo.gl/RmaLviXNorjeh5BP7 With grub debug: https://photos.app.goo.gl/PJuXdxp8uedr7fWp9 (google photos has degraded quality quite a bit, may upload the originals if too bad) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879290/+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 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
ok i tested it. it is still using llvmpipe but i think i found the relevant issue because the driver is there, i checked. issue: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+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 1883536] [NEW] Wifi does not work after suspend
Public bug reported: After I resume from suspend, Wifi does not work. I have to reload the module (ath10k_pci) to make it work. It used to work with 5.4.0-33. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent1800 F pulseaudio /dev/snd/controlC1: laurent1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 15:31:21 2020 InstallationDate: Installed on 2020-05-25 (21 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash 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: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 02MJVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883536 Title: Wifi does not work after suspend Status in linux package in Ubuntu: New Bug description: After I resume from suspend, Wifi does not work. I have to reload the module (ath10k_pci) to make it work. It used to work with 5.4.0-33. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent1800 F pulseaudio /dev/snd/controlC1: laurent1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 15:31:21 2020 InstallationDate: Installed on 2020-05-25 (21 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash 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: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 02MJVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883536/+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 1873809] Re: Make linux-kvm bootable in LXD VMs
** Changed in: linux-kvm (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018 0FFF, TR - FXSAVE_STATE - 3FF1C290
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
** Also affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-kvm (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Focal) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: In Progress Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 -
[Kernel-packages] [Bug 1788928] Re: psmouse: after sleep/suspend thinkpad touchpad not functional
*** This bug is a duplicate of bug 1786574 *** https://bugs.launchpad.net/bugs/1786574 >From Kai-Heng Feng (kaihengfeng): > Please try kernel parameter "psmouse.synaptics_intertouch=0". Thank you. This solved my wake up problem on Lenovo Helix Tablet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788928 Title: psmouse: after sleep/suspend thinkpad touchpad not functional Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Summary: The touchpad after sleep/suspend of my ThinkPad X1 will not function correctly. Expected Behavior: After sleep/suspend scroll works correctly. Actual Behavior: Unable to scroll or correctly click on a window and move it without reloading the driver Steps to reproduce: 1. Install Bionic on Thinkpad X1 (4.15.0-32-generic) 2. Open something to scroll (e.g. browser, terminal, etc.) 3. Close lid 4. Re-open lid once sleeping/suspended 5. Try to scroll and note that it does not work Workaround: Run the following after re-opening the lid $ sudo modprobe psmouse -r; sudo modprobe psmouse dmesg on reload: [12753.847050] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [12753.879362] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [12753.879375] psmouse serio1: synaptics: Trying to set up SMBus access [12753.882246] psmouse serio1: synaptics: SMbus companion is not ready yet [12753.944774] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 1795685 [12753.944791] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [12753.985102] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24 [12754.619594] psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [12754.823238] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio5/input/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2506 F pulseaudio /dev/snd/controlC0: powersj2506 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (185 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788928/+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 1879658] Re: Cannot create ipvlans with > 1500 MTU on recent Bionic kernels
Packages tested linux-gcp (4.15.0-1078.88~16.04.1) xenial; linux-hwe (4.15.0-107.108~16.04.1) xenial; linux-gcp-4.15 (4.15.0-1078.88) bionic; linux (4.15.0-107.108) bionic; -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879658 Title: Cannot create ipvlans with > 1500 MTU on recent Bionic kernels Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [IMPACT] Setting an MTU larger than the default 1500 results in an error on the recent (4.15.0-92+) Bionic/Xenial -hwe kernels when attempting to create ipvlan interfaces: # ip link add test0 mtu 9000 link eno1 type ipvlan mode l2 RTNETLINK answers: Invalid argument This breaks Docker and other applications which use a Jumbo MTU (9000) when using ipvlans. The bug is caused by the following recent commit to Bionic & Xenial-hwe; which is pulled in via the stable patchset below, which enforces a strict min/max MTU when MTUs are being set up via rtnetlink for ipvlans: Breaking commit: --- Ubuntu-hwe-4.15.0-92.93~16.04.1 * Bionic update: upstream stable patchset 2020-02-21 (LP: #1864261) * net: rtnetlink: validate IFLA_MTU attribute in rtnl_create_link() The above patch applies checks of dev->min_mtu and dev->max_mtu to avoid a malicious user from crashing the kernel with a bad value. It was patching the original patchset to centralize min/max MTU checking from various different subsystems of the networking kernel. However, in that patchset, the max_mtu had not been set to the largest phys (64K) or jumbo (9000 bytes), and defaults to 1500. The recent commit above which enforces strict bounds checking for MTU size exposes the bug of the max mtu not being set correctly for the ipvlan driver (this has been previously fixed in bonding, teaming drivers). Fix: --- This was fixed in the upstream kernel as of v4.18-rc2 for ipvlans, but was not backported to Bionic along with other patches. The missing commit in the Bionic backport: ipvlan: use ETH_MAX_MTU as max mtu commit 548feb33c598dfaf9f8e066b842441ac49b84a8a [Test Case] 1. Install any kernel earlier than 4.15.0-92 (Bionic/Xenial-hwe) 2. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2 (where test1 eno1 is the physical interface you are adding the ipvlan on) 3. # ip link ... 14: test1@eno1: mtu 9000 qdisc noop state DOWN mode DEFAULT group default qlen 1000 ... // check that your test1 ipvlan is created with mtu 9000 4. Install 4.15.0-92 kernel or later 5. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2 RTNETLINK answers: Invalid argument 6. With the above fix commit backported to the xenial-hwe/Bionic, the jumbo mtu ipvlan creation works again, identical to before 92. [Regression Potential] This commit is in upstream mainline as of v4.18-rc2, and hence is already in Cosmic and later, i.e. all post Bionic releases currently. Hence there's low regression potential here. It only impacts ipvlan functionality, and not other networking systems, so core systems should not be affected by this. And affects on setup so it either works or doesn't. Patch is trivial. It only impacts Bionic/Xenial-hwe 4.15.0-92 onwards versions (where the latent bug got exposed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879658/+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 1883521] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384028/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. - Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released and continues happening. - --- + Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. + --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: - Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub - Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: - /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M - /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M - |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M - /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M + /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M + /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M + |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: - linux-restricted-modules-5.4.0-37-generic N/A - linux-backports-modules-5.4.0-37-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-37-generic N/A + linux-backports-modules-5.4.0-37-generic N/A + linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - + _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3
[Kernel-packages] [Bug 1880012] Re: ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS
Since then, I more or less remember the operations I performed with my laptop Ubuntu 20.04 install, I think it might be: - uninstall and purge NVidia proprietary driver - (re-)install the NVidia proprietary driver - downgrade then re-upgrade the Linux kernel and the overheating and fan off problem mysteriously vanished. Now I find the temperature of my ASUS UX533F is fine, even with high workload, and I can hear the fan running when needed (when the temp. is higher than 50°C or so). But I still have the following (minor in my opinion) issue: sensors still shows the fan RPM 0 all the time. Since I don't know how the problem disappeared, I cannot say it is "fixed" and it might come back. Still, I thought it was worth mentioning. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1880012 Title: ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New Bug description: After installing Ubuntu 20.04 LTS, my laptop's temperature goes fairly high without intensive CPU activity. The fan(s) remain **off** under heavy CPU load and the temperature goes very high. I don't suspect a material failure since I didn't notice such overheating issues anymore with my previous Ubuntu (19.04) (after using sudo prime-select intel). **Config** - ASUS UX533FN - BIOS version 304 (up-to-date) - Kernel: 5.4.0-31-generic (same issue with 5.4.0-29) - NVIDIA GeForce MX150 (with latest NVIDIA driver) Low CPU load Without running anything special, I get the following figures with `sensors` command: ... pch_cannonlake-virtual-0 Adapter: Virtual device temp1:+49.0°C BAT0-acpi-0 Adapter: ACPI interface in0: 15.60 V asus-isa- Adapter: ISA adapter cpu_fan:0 RPM coretemp-isa- Adapter: ISA adapter Package id 0: +50.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+49.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+48.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+48.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+50.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+49.0°C (crit = +103.0°C) These figures are a too high in my opinion for low CPU load with a room temperature of 20°C. But here come's worse: Heavy CPU load == When the CPU is under load, for instance when running `sysbench cpu run` in loop, the temperature increases to 90°C, and no fan is triggered! To get a repeatable CPU load test, I run while true; do echo "One more time..." && sysbench cpu run; done Here are the figures I get in this case (from `sensors` command): ... pch_cannonlake-virtual-0 Adapter: Virtual device temp1:+65.0°C BAT0-acpi-0 Adapter: ACPI interface in0: 15.60 V asus-isa- Adapter: ISA adapter cpu_fan:0 RPM coretemp-isa- Adapter: ISA adapter Package id 0: +88.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+88.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+70.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+72.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+72.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+86.0°C (crit = +103.0°C) Note 1: The temperature in the room for this test is 20°C. Note 2: I got almost the same issue one year ago with Ubuntu 19.04 and used the sudo prime-select intel workaround. What I already tried - installing the latest NVIDIA driver, including selecting `intel` with `prime-select` ameliorated the situation but didn't tackle the issue - running `sensors-detect` (YES to all questions) resulted in `coretemp` to be added to `/etc/modules` - running `pwmconfig` didn't work: /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sylvain1710 F pulseaudio /dev/snd/pcmC0D0p: sylvain1710 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 20:58:45 2020 InstallationDate: Installed on 2020-05-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam Bus 001 Device 003: ID 8087:0aaa Intel Corp.
[Kernel-packages] [Bug 1883521] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384019/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384021/+files/PciMultimedia.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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384018/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384017/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384020/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384022/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384014/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384027/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] Card1.Codecs.codec.0.txt
apport information ** Attachment added: "Card1.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384016/+files/Card1.Codecs.codec.0.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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384026/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384024/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384025/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384015/+files/Card0.Codecs.codec.0.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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384023/+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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released for other kernel version and I tested in bionic and continues happening. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: AOPEN Inc. DE6340 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.name: aVKx-DE R1.02 dmi.board.vendor: AOPEN Inc. dmi.board.version: 55DEL10001P dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: dmi.product.name: DE6340 dmi.product.sku: DE6340 dmi.product.version: RYZEN V1000 dmi.sys.vendor: AOPEN Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] Re: Hang on shutdown/restart
apport information ** Tags added: apport-collected uec-images ** Description changed: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. - Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta- - hwe/+bug/1880041 because there are a lot of coincidences, but the fix is - released and continues happening. + Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released and continues happening. + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' + Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-06-15 (0 days ago) + InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 1M + /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M + |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M + MachineType: AOPEN Inc. DE6340 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=68b38bec-b005-4f3a-bc41-b88bb5d98d1d ro + ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 + 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: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.4.0-37-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 01/28/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 5.13 + dmi.board.name: aVKx-DE R1.02 + dmi.board.vendor: AOPEN Inc. + dmi.board.version: 55DEL10001P + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd01/28/2019:svnAOPENInc.:pnDE6340:pvrRYZENV1000:rvnAOPENInc.:rnaVKx-DER1.02:rvr55DEL10001P:cvn:ct3:cvr: + dmi.product.name: DE6340 + dmi.product.sku: DE6340 + dmi.product.version: RYZEN V1000 + dmi.sys.vendor: AOPEN Inc. ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1883521/+attachment/5384013/+files/AlsaDevices.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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Confirmed Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with
[Kernel-packages] [Bug 1883521] 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 1883521 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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: Incomplete Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta- hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released and continues happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 1883521] [NEW] Hang on shutdown/restart
Public bug reported: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta- hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released and continues happening. ** 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/1883521 Title: Hang on shutdown/restart Status in linux package in Ubuntu: New Bug description: I installed ubuntu 20.04 in an Aopen DE6340 which contains an "AMD Ryzen Embedded V1807B with Radeon Vega Gfx" and the installation went correctly, but at the end at the moment of unplugging the iso and restarting the computer never restarts, appears periodically about hung task timeout and never restarts. I tried in the installed system with Ubuntu 5.4.0-37.41-generic 5.4.41 and linux-image-5.4.0-28-generic and it's happening in both versions. With mainline kernel its working correctly until linux-image- unsigned-5.4.21-050421-generic_5.4.21-050421.202002191431_amd64.deb from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.21/, after 5.4.22 it's starting to happen the same. Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux-meta- hwe/+bug/1880041 because there are a lot of coincidences, but the fix is released and continues happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883521/+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 918769] Re: X blink with Vostro 360 and Ubuntu Oneiric and Precise
** Changed in: linux (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/918769 Title: X blink with Vostro 360 and Ubuntu Oneiric and Precise Status in xf86-video-intel: Fix Released Status in linux package in Ubuntu: Won't Fix Status in linux source package in Precise: Won't Fix Bug description: I can't actually manage to have X working correctly with my Vostro 360. The X session start but the screen blink every ~10s (and stay back most of the time). I found a lot of people having similar problem, but no solution can be applied to my case. X logs for Ubuntu 11.10 (i386 but same issue for amd64): 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) I will attach a kernel and Xorg dump. The only way for me to have correct resolution (1920x1080) was in using the Live CDROM of elementary OS (based on Ubuntu Maverick 10.10) which use: - linux-headers-2.6.35-28-generic 2.6.35-28.49 - xserver-xorg-video-intel 2:2.12.0-1ubuntu5.2 .. but once the system installed, the black screen problem come back. I can't actually undestand the difference between the live OS and the installed one (after the installation, the kernel is slightly different; but after installing exactly the same than the one used in the live CD, the problem persist). I also tried other Ubuntu release, even the latest Ubuntu 12.04 precise (alpha version): same issue. Booting with nomodeset helps also, but lead to a low resolution. Any idea on what could explain that eveything is working correctly with the livecd, and nothing once the system installed ? More generaly, how can i help to have a working solution ? Packages installed: --- ii libdrm-intel1 2.4.30-1ubuntu1 ii xserver-xorg-video-intel 2:2.15.901-1ubuntu4 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-9.16-generic-pae 3.2.1 Uname: Linux 3.2.0-9-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Jan 19 17:07:41 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0512] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120112) MachineType: Dell Inc. Vostro 360 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-9-generic-pae root=UUID=4f9a709d-de4a-4cc6-a27b-0c6e05a2cde2 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 07K1DC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: PRAndrews_2H03P_A01.SDR dmi.modalias: dmi:bvnDellInc.:bvrA06:bd12/22/2011:svnDellInc.:pnVostro360:pvr00:rvnDellInc.:rn07K1DC:rvrA00:cvnDellInc.:ct13:cvrPRAndrews_2H03P_A01.SDR: dmi.product.name: Vostro 360 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8 version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.10.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/918769/+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 1876684] Re: fanotify09 case 3 from ubuntu_ltp_syscalls failed
Fix applied on Focal via stable-update (bug 1879759) Verified and passed. ** Also affects: linux (Ubuntu Bionic) 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/1876684 Title: fanotify09 case 3 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is a new test case added 7 days ago [1] Test failed on Focal 5.4.0-29.33 with: fanotify09.c:150: FAIL: group 1 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint fanotify09.c:150: FAIL: group 2 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint [1] https://github.com/linux-test-project/ltp/commit/70ca1e8806d227d47c6801262d3f7983652159a4#diff-234c27c769cf07468a81748a0e7330dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876684/+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 1883511] 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/1883511 Title: High load from process irq/65-i2c-INT3 - kernel module tps6598x Status in linux package in Ubuntu: Confirmed Bug description: There seems to be an issue with the kernel module tps6598x which puts the CPU on a high load: https://forums.intel.com/s/question/0D50P4fWnUeSAK/nuc10i3-irq- problem As soon as the module is unloaded, cpu load is back to normal. According to a post in the link above the issue is the following: "My guess is that the IRQ resource is not correct for the PD controller causing you to see irq flood. The problem is that the ACPI device entry (the node) on this platform has 4 I2CSerialBus resources and 4 IRQ resources. The idea is that the single ACPI device entry can represent up to 4 USB PD controllers. The problem is that there is no way to know which IRQ resource belongs to which I2CSerialBus resource :-(. Andy, this is one of those multi-instantiate I2C slave devices with HID INT3515. The only solution I can think of is that we start maintaining DMI quirk table in drivers/platform/x86/i2c-multi-instantiate.c where we supply the correct i2c to irq resource mapping for every platform that has this device(s)." Description: Ubuntu 20.04 LTS Release: 20.04 Hardware: Intel NUC10i5FNK 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass Date: Mon Jun 15 11:04:57 2020 InstallationDate: Installed on 2020-04-26 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel(R) Client Systems NUC10i5FNK ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro 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: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0041.2020.0518.1045 dmi.board.asset.tag: Default string dmi.board.name: NUC10i5FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61361-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0041.2020.0518.1045:bd05/18/2020:svnIntel(R)ClientSystems:pnNUC10i5FNK:pvrK61339-302:rvnIntelCorporation:rnNUC10i5FNB:rvrK61361-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i5FNK dmi.product.sku: BXNUC10i5FNK dmi.product.version: K61339-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883511/+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 1876684] Re: fanotify09 case 3 from ubuntu_ltp_syscalls failed
Fix applied on Eoan via stable-update (bug 1881657) Verified and passed. ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Focal) 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/1876684 Title: fanotify09 case 3 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is a new test case added 7 days ago [1] Test failed on Focal 5.4.0-29.33 with: fanotify09.c:150: FAIL: group 1 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint fanotify09.c:150: FAIL: group 2 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint [1] https://github.com/linux-test-project/ltp/commit/70ca1e8806d227d47c6801262d3f7983652159a4#diff-234c27c769cf07468a81748a0e7330dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876684/+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 1878748] Re: fanotify15 from ubuntu_ltp_syscalls failed with E/F
Patch applied on Eoan with stable update (bug 1880758)
Passed on Eoan.
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Released
** Changed in: ubuntu-kernel-tests
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/1878748
Title:
fanotify15 from ubuntu_ltp_syscalls failed with E/F
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
== SRU Justification ==
The fanotify15 from ubuntu_ltp_syscalls will fail on differenet
filesystems with Eoan kernel:
fanotify15.c:223: FAIL: Got event: mask=2 (expected 43c0) pid=16744
fd=-1
fanotify15.c:223: FAIL: Got event: mask=2 (expected 4400) pid=16744
fd=-1
fanotify15.c:210: FAIL: got unnecessary event: mask=2 pid=16744 fd=-1
fanotify15.c:210: FAIL: got unnecessary event: mask=43c0 pid=16744 fd=-1
fanotify15.c:210: FAIL: got unnecessary event: mask=4400 pid=16744 fd=-1
== Fix ==
* f367a62a7cad ("fanotify: merge duplicate events on parent and child")
This patch has been applied to Focal via stable update process, and
this test will be skipped on Disco and older kernels with
"FAN_REPORT_FID not supported in kernel".
Thus Eoan will be the only kernel that needs this patch. It needs to be
backported because of missing commit dfc2d2594e4 ("fsnotify: replace
inode pointer with an object id")
== Test ==
A test kernel could be found here:
https://people.canonical.com/~phlin/kernel/lp-1878748-fanotify15/
This faontify15 test will pass with this patch applied.
Also tested with the whole ubuntu_ltp_syscalls test suite, no new
failures were reported.
== Regression Potential ==
Low, it's just a minor bug according to the patch author [1] and it's
testable with positive result.
[1] https://lwn.net/Articles/812675/
== Original Bug Report ==
This is a new sub test case added to fanotify15.
<<>>
incrementing stop
tst_device.c:262: INFO: Using test device LTP_DEV='/dev/loop4'
tst_supported_fs_types.c:59: INFO: Kernel supports ext2
tst_supported_fs_types.c:43: INFO: mkfs.ext2 does exist
tst_supported_fs_types.c:59: INFO: Kernel supports ext3
tst_supported_fs_types.c:43: INFO: mkfs.ext3 does exist
tst_supported_fs_types.c:59: INFO: Kernel supports ext4
tst_supported_fs_types.c:43: INFO: mkfs.ext4 does exist
tst_supported_fs_types.c:59: INFO: Kernel supports xfs
tst_supported_fs_types.c:43: INFO: mkfs.xfs does exist
tst_supported_fs_types.c:59: INFO: Kernel supports btrfs
tst_supported_fs_types.c:43: INFO: mkfs.btrfs does exist
tst_supported_fs_types.c:59: INFO: Kernel supports vfat
tst_supported_fs_types.c:43: INFO: mkfs.vfat does exist
tst_supported_fs_types.c:82: INFO: Filesystem exfat is not supported
tst_test.c:1307: INFO: Testing on ext2
tst_mkfs.c:89: INFO: Formatting /dev/loop4 with ext2 opts='' extra opts=''
mke2fs 1.45.3 (14-Jul-2019)
tst_test.c:1244: INFO: Timeout per run is 0h 05m 00s
fanotify15.c:86: INFO: Test #0: FAN_REPORT_FID on filesystem including
FAN_DELETE_SELF
fanotify.h:183: INFO: fid(mntpoint/test_dir) =
e0b13469.adbaecba.8001.5c9458d0.0...
fanotify.h:183: INFO: fid(mntpoint/test_dir/file1) =
e0b13469.adbaecba.8002.c2539281.0...
fanotify.h:183: INFO: fid(mntpoint/test_dir/dir1) =
e0b13469.adbaecba.8002.aec0582b.0...
fanotify15.c:266: PASS: Got event: mask=3c0, pid=1479,
fid=e0b13469.adbaecba.5c9458d08001 values
fanotify15.c:266: PASS: Got event: mask=402, pid=1479,
fid=e0b13469.adbaecba.c25392818002 values
fanotify15.c:266: PASS: Got event: mask=400, pid=1479,
fid=e0b13469.adbaecba.c25392818002 values
fanotify15.c:266: PASS: Got event: mask=43c0, pid=1479,
fid=e0b13469.adbaecba.5c9458d08001 values
fanotify15.c:266: PASS: Got event: mask=4400, pid=1479,
fid=e0b13469.adbaecba.aec0582b8002 values
fanotify15.c:86: INFO: Test #1: FAN_REPORT_FID on directory with
FAN_EVENT_ON_CHILD
fanotify.h:183: INFO: fid(mntpoint/test_dir) =
e0b13469.adbaecba.8001.5c9458d0.0...
fanotify.h:183: INFO: fid(mntpoint/test_dir/file1) =
e0b13469.adbaecba.8002.8610b51a.0...
fanotify.h:183: INFO: fid(mntpoint/test_dir/dir1) =
e0b13469.adbaecba.8002.15288504.0...
fanotify15.c:266: PASS: Got event: mask=3c0, pid=1479,
fid=e0b13469.adbaecba.5c9458d08001 values
fanotify15.c:266: PASS: Got event: mask=2, pid=1479,
fid=e0b13469.adbaecba.8610b51a8002 values
fanotify15.c:266: PASS: Got event: mask=402, pid=1479,
fid=e0b13469.adbaecba.8610b51a8002 values
fanotify15.c:223: FAIL: Got event: mask=2 (expected 43c0) pid=1479 fd=-1
fanotify15.c:223: FAIL: Got event: mask=2 (expected 4400) pid=1479 fd=-1
fanotify15.c:210: FAIL: got
