[Kernel-packages] [Bug 1925126] 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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925126/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1925126] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490019/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490020/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490013/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490017/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490012/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490011/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490016/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490018/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490014/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490015/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490005/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490010/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490009/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490008/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490006/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925126/+attachment/5490007/+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/1925126 Title: Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome-terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925126] [NEW] Intel video driver i915 - Repeated GPU HANG's, jitter, freeze-ups 5.8.0-50
Public bug reported: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome- terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: deactivate vga console [Mon Apr 19 22:01:39 2021] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 19 22:01:39 2021] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [Mon Apr 19 22:01:39 2021] fbcon: i915drmfb (fb0) is primary device [Mon Apr 19 22:01:40 2021] i915 :00:02.0: fb0: i915drmfb frame buffer device [Mon Apr 19 22:02:12 2021] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:0: [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:24 2021] i915 :00:02.0: [drm] gnome-shell[3417] context reset due to GPU hang [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff, in gnome-shell [3417] [Mon Apr 19 22:02:27 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:ccddeeff [Mon Apr 19 22:02:39 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:003f003f, in Renderer [11805] [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:17 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU hang [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:40d84443, in Renderer [11805] [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [Mon Apr 19 22:05:28 2021] i915 :00:02.0: [drm] Renderer[11805] context reset due to GPU han --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev4268 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (74 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: LENOVO 2436CTO Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=5d036090-3f9e-4adf-a198-e0db3da45582 ro rootflags=subvol=@ luks.crypttab=no quiet ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/11/2018 dmi.bios.release: 2.72 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:br2.72:efr1.13:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 2436CTO dmi.product.sku: LENOVO_MT_2436 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected focal ** Tags added: apport-collected focal ** Description changed: dmesg output with GPU HANGs, below. While running, it's fairly easy to cause flashing of text within a window, flipping between one window and another (eg. two tabs in gnome- terminal), or even complete freeze-ups, by moving a window or switching between windows, a little too quickly. This is a basically new install of Ubuntu 20.04 on a ThinkPad W530 running Intel graphics and with kernel 5.8.0-50-generic. -- $ dmesg -T | grep -i i915 [Mon Apr 19 22:01:39 2021] i915
[Kernel-packages] [Bug 1925124] Re: panic in ipt_do_table+0x621/0x640
** Description changed: 1.This bug has happened on the following kernel version: - 4.4.0-104-generic - 4.15.0-88-generic - 4.15.0-13-generic - 5.4.0-42-generic - 5.4.0-47-generic + 4.4.0-104-generic + 4.15.0-88-generic + 4.15.0-13-generic + 5.4.0-42-generic + 5.4.0-47-generic 2.we cannot reliably reproduce this issue. 3.this patch seems to fix this issue. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/netfilter/x_tables.c?id=175e476b8cdf2a4de7432583b49c871345e4f8a1 4.the following crash dmesg from 5.4.0-47-generic: [2021-03-19 12:17:53][3581678.514072] audit: audit_lost=1 audit_rate_limit=1 audit_backlog_limit=1024 [2021-03-23 21:57:06][3962019.737898] general protection fault: [#1] SMP PTI [2021-03-23 21:57:06][3962019.739019] CPU: 4 PID: 0 Comm: swapper/4 Kdump: loaded Not tainted 5.4.0-47-generic #51~18.04.1-Ubuntu [2021-03-23 21:57:06][3962019.740433] Hardware name: Tencent Cloud CVM, BIOS seabios-1.9.1-qemu-project.org 04/01/2014 [2021-03-23 21:57:06][3962019.741829] RIP: 0010:ipt_do_table+0x621/0x640 [ip_tables] [2021-03-23 21:57:06][3962019.742587] Code: ff ff ff 45 31 d2 48 89 85 50 ff ff ff e9 7e fe ff ff 83 ad 70 ff ff ff 01 48 8b bd 78 ff ff ff 8b 85 70 ff ff ff 4c 8b 34 c7 <41> 0f b7 46 5a 49 01 c6 e9 [2021-03-23 21:57:06]18 fb ff ff c7 45 a4 00 00 00 00 e9 e9 [2021-03-23 21:57:06][3962019.745295] RSP: 0018:bcd080184c18 EFLAGS: 00010246 [2021-03-23 21:57:06][3962019.745988] RAX: RBX: 96b7e9b717b0 RCX: dcd07f70a150 [2021-03-23 21:57:06][3962019.747025] RDX: 0001ab6a RSI: 96b7e1d98d80 RDI: 96b7e1d98d80 [2021-03-23 21:57:06][3962019.748015] RBP: bcd080184d08 R08: 0008 R09: 96b82aca2980 [2021-03-23 21:57:06][3962019.748988] R10: 0d38 R11: 96b7cacaa380 R12: 96b833fea000 [2021-03-23 21:57:06][3962019.749927] R13: 96b7ebb4a04e R14: 3f13d7139e6d8ccb R15: 96b7d2c28f00 [2021-03-23 21:57:06][3962019.750873] FS: () GS:96b83fb0() knlGS: [2021-03-23 21:57:06][3962019.751919] CS: 0010 DS: ES: CR0: 80050033 [2021-03-23 21:57:06][3962019.752720] CR2: 7fee206258f0 CR3: 000f9c428001 CR4: 003606e0 [2021-03-23 21:57:06][3962019.753603] DR0: DR1: DR2: [2021-03-23 21:57:06][3962019.754619] DR3: DR6: fffe0ff0 DR7: 0400 [2021-03-23 21:57:06][3962019.755606] Call Trace: [2021-03-23 21:57:06][3962019.755984] [2021-03-23 21:57:06][3962019.756282] iptable_filter_hook+0x1f/0x30 [iptable_filter] [2021-03-23 21:57:06][3962019.757199] nf_hook_slow+0x48/0xc0 [2021-03-23 21:57:06][3962019.757753] ip_forward+0x410/0x480 [2021-03-23 21:57:06][3962019.758350] ? ip4_key_hashfn+0xc0/0xc0 [2021-03-23 21:57:06][3962019.758907] ip_rcv_finish+0x84/0xa0 [2021-03-23 21:57:06][3962019.759469] ip_rcv+0xbc/0xd0 [2021-03-23 21:57:06][3962019.760543] ? ip_rcv_finish_core.isra.18+0x3b0/0x3b0 [2021-03-23 21:57:06][3962019.761916] __netif_receive_skb_one_core+0x86/0xa0 [2021-03-23 21:57:06][3962019.763210] __netif_receive_skb+0x18/0x60 [2021-03-23 21:57:06][3962019.764341] process_backlog+0xa0/0x170 [2021-03-23 21:57:06][3962019.765600] net_rx_action+0x140/0x3c0 [2021-03-23 21:57:06][3962019.766550] __do_softirq+0xe4/0x2da [2021-03-23 21:57:06][3962019.767792] irq_exit+0xae/0xb0 [2021-03-23 21:57:06][3962019.768857] smp_call_function_single_interrupt+0x48/0xd0 [2021-03-23 21:57:06][3962019.770140] call_function_single_interrupt+0xf/0x20 [2021-03-23 21:57:06][3962019.771315] [2021-03-23 21:57:06][3962019.772038] RIP: 0010:native_safe_halt+0x12/0x20 - [2021-03-23 21:57:06][3962019.773239] Code: 00 0f 00 2d 32 98 53 00 f4 5d c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d 12 98 53 00 fb f4 <5d> c3 90 90 90 90 90 90 90 [2021-03-23 21:57:06]90 90 90 90 90 0f 1f 44 00 00 55 48 89 - [2021-03-23 21:57:06][3962019.776646] RSP: 0018:bcd080093e70 EFLAGS: 0246 ORIG_RAX: ff04 - [2021-03-23 21:57:06][3962019.778015] RAX: 93ad22f0 RBX: 0004 RCX: 0001 - [2021-03-23 21:57:06][3962019.779356] RDX: 96b83fb2ba80 RSI: bcd080093e40 RDI: - [2021-03-23 21:57:06][3962019.780633] RBP: bcd080093e70 R08: 0010e421e97a71a1 R09: 0001 - [2021-03-23 21:57:06][3962019.782033] R10: 007e8c00 R11: 0fca3b36 R12: 0004 - [2021-03-23 21:57:06][3962019.783373] R13: R14: R15: - [2021-03-23 21:57:06][3962019.784725] ? ldsem_down_write+0x230/0x230 - [2021-03-23 21:57:06][3962019.785741] default_idle+0x22/0x150 - [2021-03-23 21:57:06][3962019.786673] arch_cpu_idle+0x15/0x20 - [2021-03-23 21:57:06][3962019.787667]
[Kernel-packages] [Bug 1925124] 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 1925124 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: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925124 Title: panic in ipt_do_table+0x621/0x640 Status in linux package in Ubuntu: Incomplete Bug description: 1.This bug has happened on the following kernel version: 4.4.0-104-generic 4.15.0-88-generic 4.15.0-13-generic 5.4.0-42-generic 5.4.0-47-generic 2.we cannot reliably reproduce this issue. 3.this patch seems to fix this issue. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/netfilter/x_tables.c?id=175e476b8cdf2a4de7432583b49c871345e4f8a1 4.the following crash dmesg from 5.4.0-47-generic: [2021-03-19 12:17:53][3581678.514072] audit: audit_lost=1 audit_rate_limit=1 audit_backlog_limit=1024 [2021-03-23 21:57:06][3962019.737898] general protection fault: [#1] SMP PTI [2021-03-23 21:57:06][3962019.739019] CPU: 4 PID: 0 Comm: swapper/4 Kdump: loaded Not tainted 5.4.0-47-generic #51~18.04.1-Ubuntu [2021-03-23 21:57:06][3962019.740433] Hardware name: Tencent Cloud CVM, BIOS seabios-1.9.1-qemu-project.org 04/01/2014 [2021-03-23 21:57:06][3962019.741829] RIP: 0010:ipt_do_table+0x621/0x640 [ip_tables] [2021-03-23 21:57:06][3962019.742587] Code: ff ff ff 45 31 d2 48 89 85 50 ff ff ff e9 7e fe ff ff 83 ad 70 ff ff ff 01 48 8b bd 78 ff ff ff 8b 85 70 ff ff ff 4c 8b 34 c7 <41> 0f b7 46 5a 49 01 c6 e9 [2021-03-23 21:57:06]18 fb ff ff c7 45 a4 00 00 00 00 e9 e9 [2021-03-23 21:57:06][3962019.745295] RSP: 0018:bcd080184c18 EFLAGS: 00010246 [2021-03-23 21:57:06][3962019.745988] RAX: RBX: 96b7e9b717b0 RCX: dcd07f70a150 [2021-03-23 21:57:06][3962019.747025] RDX: 0001ab6a RSI: 96b7e1d98d80 RDI: 96b7e1d98d80 [2021-03-23 21:57:06][3962019.748015] RBP: bcd080184d08 R08: 0008 R09: 96b82aca2980 [2021-03-23 21:57:06][3962019.748988] R10: 0d38 R11: 96b7cacaa380 R12: 96b833fea000 [2021-03-23 21:57:06][3962019.749927] R13: 96b7ebb4a04e R14: 3f13d7139e6d8ccb R15: 96b7d2c28f00 [2021-03-23 21:57:06][3962019.750873] FS: () GS:96b83fb0() knlGS: [2021-03-23 21:57:06][3962019.751919] CS: 0010 DS: ES: CR0: 80050033 [2021-03-23 21:57:06][3962019.752720] CR2: 7fee206258f0 CR3: 000f9c428001 CR4: 003606e0 [2021-03-23 21:57:06][3962019.753603] DR0: DR1: DR2: [2021-03-23 21:57:06][3962019.754619] DR3: DR6: fffe0ff0 DR7: 0400 [2021-03-23 21:57:06][3962019.755606] Call Trace: [2021-03-23 21:57:06][3962019.755984] [2021-03-23 21:57:06][3962019.756282] iptable_filter_hook+0x1f/0x30 [iptable_filter] [2021-03-23 21:57:06][3962019.757199] nf_hook_slow+0x48/0xc0 [2021-03-23 21:57:06][3962019.757753] ip_forward+0x410/0x480 [2021-03-23 21:57:06][3962019.758350] ? ip4_key_hashfn+0xc0/0xc0 [2021-03-23 21:57:06][3962019.758907] ip_rcv_finish+0x84/0xa0 [2021-03-23 21:57:06][3962019.759469] ip_rcv+0xbc/0xd0 [2021-03-23 21:57:06][3962019.760543] ? ip_rcv_finish_core.isra.18+0x3b0/0x3b0 [2021-03-23 21:57:06][3962019.761916] __netif_receive_skb_one_core+0x86/0xa0 [2021-03-23 21:57:06][3962019.763210] __netif_receive_skb+0x18/0x60 [2021-03-23 21:57:06][3962019.764341] process_backlog+0xa0/0x170 [2021-03-23 21:57:06][3962019.765600] net_rx_action+0x140/0x3c0 [2021-03-23 21:57:06][3962019.766550] __do_softirq+0xe4/0x2da [2021-03-23 21:57:06][3962019.767792] irq_exit+0xae/0xb0 [2021-03-23 21:57:06][3962019.768857] smp_call_function_single_interrupt+0x48/0xd0 [2021-03-23 21:57:06][3962019.770140] call_function_single_interrupt+0xf/0x20 [2021-03-23 21:57:06][3962019.771315] [2021-03-23 21:57:06][3962019.772038] RIP: 0010:native_safe_halt+0x12/0x20 [2021-03-23 21:57:06][3962019.773239] Code: 00 0f 00 2d 32 98 53 00 f4 5d c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d 12 98 53 00 fb f4 <5d> c3 90 90 90 90 90 90 90 [2021-03-23 21:57:06]90 90 90 90 90 0f 1f 44 00 00 55 48 89 [2021-03-23 21:57:06][3962019.776646] RSP: 0018:bcd080093e70 EFLAGS: 0246 ORIG_RAX: ff04 [2021-03-23
[Kernel-packages] [Bug 1925124] [NEW] panic in ipt_do_table+0x621/0x640
Public bug reported: 1.This bug has happened on the following kernel version: 4.4.0-104-generic 4.15.0-88-generic 4.15.0-13-generic 5.4.0-42-generic 5.4.0-47-generic 2.we cannot reliably reproduce this issue. 3.this patch seems to fix this issue. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/netfilter/x_tables.c?id=175e476b8cdf2a4de7432583b49c871345e4f8a1 4.the following crash dmesg from 5.4.0-47-generic: [2021-03-19 12:17:53][3581678.514072] audit: audit_lost=1 audit_rate_limit=1 audit_backlog_limit=1024 [2021-03-23 21:57:06][3962019.737898] general protection fault: [#1] SMP PTI [2021-03-23 21:57:06][3962019.739019] CPU: 4 PID: 0 Comm: swapper/4 Kdump: loaded Not tainted 5.4.0-47-generic #51~18.04.1-Ubuntu [2021-03-23 21:57:06][3962019.740433] Hardware name: Tencent Cloud CVM, BIOS seabios-1.9.1-qemu-project.org 04/01/2014 [2021-03-23 21:57:06][3962019.741829] RIP: 0010:ipt_do_table+0x621/0x640 [ip_tables] [2021-03-23 21:57:06][3962019.742587] Code: ff ff ff 45 31 d2 48 89 85 50 ff ff ff e9 7e fe ff ff 83 ad 70 ff ff ff 01 48 8b bd 78 ff ff ff 8b 85 70 ff ff ff 4c 8b 34 c7 <41> 0f b7 46 5a 49 01 c6 e9 [2021-03-23 21:57:06]18 fb ff ff c7 45 a4 00 00 00 00 e9 e9 [2021-03-23 21:57:06][3962019.745295] RSP: 0018:bcd080184c18 EFLAGS: 00010246 [2021-03-23 21:57:06][3962019.745988] RAX: RBX: 96b7e9b717b0 RCX: dcd07f70a150 [2021-03-23 21:57:06][3962019.747025] RDX: 0001ab6a RSI: 96b7e1d98d80 RDI: 96b7e1d98d80 [2021-03-23 21:57:06][3962019.748015] RBP: bcd080184d08 R08: 0008 R09: 96b82aca2980 [2021-03-23 21:57:06][3962019.748988] R10: 0d38 R11: 96b7cacaa380 R12: 96b833fea000 [2021-03-23 21:57:06][3962019.749927] R13: 96b7ebb4a04e R14: 3f13d7139e6d8ccb R15: 96b7d2c28f00 [2021-03-23 21:57:06][3962019.750873] FS: () GS:96b83fb0() knlGS: [2021-03-23 21:57:06][3962019.751919] CS: 0010 DS: ES: CR0: 80050033 [2021-03-23 21:57:06][3962019.752720] CR2: 7fee206258f0 CR3: 000f9c428001 CR4: 003606e0 [2021-03-23 21:57:06][3962019.753603] DR0: DR1: DR2: [2021-03-23 21:57:06][3962019.754619] DR3: DR6: fffe0ff0 DR7: 0400 [2021-03-23 21:57:06][3962019.755606] Call Trace: [2021-03-23 21:57:06][3962019.755984] [2021-03-23 21:57:06][3962019.756282] iptable_filter_hook+0x1f/0x30 [iptable_filter] [2021-03-23 21:57:06][3962019.757199] nf_hook_slow+0x48/0xc0 [2021-03-23 21:57:06][3962019.757753] ip_forward+0x410/0x480 [2021-03-23 21:57:06][3962019.758350] ? ip4_key_hashfn+0xc0/0xc0 [2021-03-23 21:57:06][3962019.758907] ip_rcv_finish+0x84/0xa0 [2021-03-23 21:57:06][3962019.759469] ip_rcv+0xbc/0xd0 [2021-03-23 21:57:06][3962019.760543] ? ip_rcv_finish_core.isra.18+0x3b0/0x3b0 [2021-03-23 21:57:06][3962019.761916] __netif_receive_skb_one_core+0x86/0xa0 [2021-03-23 21:57:06][3962019.763210] __netif_receive_skb+0x18/0x60 [2021-03-23 21:57:06][3962019.764341] process_backlog+0xa0/0x170 [2021-03-23 21:57:06][3962019.765600] net_rx_action+0x140/0x3c0 [2021-03-23 21:57:06][3962019.766550] __do_softirq+0xe4/0x2da [2021-03-23 21:57:06][3962019.767792] irq_exit+0xae/0xb0 [2021-03-23 21:57:06][3962019.768857] smp_call_function_single_interrupt+0x48/0xd0 [2021-03-23 21:57:06][3962019.770140] call_function_single_interrupt+0xf/0x20 [2021-03-23 21:57:06][3962019.771315] [2021-03-23 21:57:06][3962019.772038] RIP: 0010:native_safe_halt+0x12/0x20 [2021-03-23 21:57:06][3962019.773239] Code: 00 0f 00 2d 32 98 53 00 f4 5d c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d 12 98 53 00 fb f4 <5d> c3 90 90 90 90 90 90 90 [2021-03-23 21:57:06]90 90 90 90 90 0f 1f 44 00 00 55 48 89 [2021-03-23 21:57:06][3962019.776646] RSP: 0018:bcd080093e70 EFLAGS: 0246 ORIG_RAX: ff04 [2021-03-23 21:57:06][3962019.778015] RAX: 93ad22f0 RBX: 0004 RCX: 0001 [2021-03-23 21:57:06][3962019.779356] RDX: 96b83fb2ba80 RSI: bcd080093e40 RDI: [2021-03-23 21:57:06][3962019.780633] RBP: bcd080093e70 R08: 0010e421e97a71a1 R09: 0001 [2021-03-23 21:57:06][3962019.782033] R10: 007e8c00 R11: 0fca3b36 R12: 0004 [2021-03-23 21:57:06][3962019.783373] R13: R14: R15: [2021-03-23 21:57:06][3962019.784725] ? ldsem_down_write+0x230/0x230 [2021-03-23 21:57:06][3962019.785741] default_idle+0x22/0x150 [2021-03-23 21:57:06][3962019.786673] arch_cpu_idle+0x15/0x20 [2021-03-23 21:57:06][3962019.787667] default_idle_call+0x23/0x30 [2021-03-23 21:57:06][3962019.788803] do_idle+0x1bd/0x270 [2021-03-23 21:57:06][3962019.789875] cpu_startup_entry+0x1d/0x20 [2021-03-23 21:57:06][3962019.790990] start_secondary+0x166/0x1c0 [2021-03-23
[Kernel-packages] [Bug 1924997] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489970/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489973/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489974/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489975/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489977/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489971/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489976/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489978/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489969/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489979/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489972/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489968/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489981/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] Re: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80%
apport information ** Tags added: apport-collected focal ** Description changed: A cracking noises is noticed when doing audio playback from the built-in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 1444 F pulseaudio + CasperMD5CheckResult: skip + 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-proposed-release+X90 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-04-13 (6 days ago) + InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD + Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint + Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. Vostro 3500 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.10.0-1020-oem N/A + linux-backports-modules-5.10.0-1020-oem N/A + linux-firmware 1.187.10 + Tags: focal + Uname: Linux 5.10.0-1020-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 02/02/2021 + dmi.bios.release: 1.2 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.2.2 + dmi.board.name: 09YKK0 + dmi.board.vendor: Dell Inc. + dmi.board.version: X00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: + dmi.product.family: Vostro + dmi.product.name: Vostro 3500 + dmi.product.sku: 0A24 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489967/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem
[Kernel-packages] [Bug 1924997] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489980/+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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1924997/+attachment/5489982/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip 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-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924611] Re: setting extended attribute may cause memory leak
This bug was fixed in the package linux-raspi2-5.3 - 5.3.0-1040.42 --- linux-raspi2-5.3 (5.3.0-1040.42) bionic; urgency=medium * bionic/linux-raspi2-5.3: 5.3.0-1040.42 -proposed tracker (LP: #1924651) [ Ubuntu: 5.3.0-74.70 ] * bionic/linux-hwe: 5.3.0-74.70 -proposed tracker (LP: #1924647) * setting extended attribute may cause memory leak (LP: #1924611) - SAUCE: vfs_setxattr: free converted value if xattr_permission returns error -- Stefan Bader Fri, 16 Apr 2021 11:13:35 +0200 ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak Status in linux package in Ubuntu: Invalid Status in linux-gke-5.3 package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-raspi2-5.3 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux-gke-5.3 source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Invalid Status in linux-oem-5.6 source package in Xenial: Invalid Status in linux-raspi2-5.3 source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux-gke-5.3 source package in Bionic: Fix Released Status in linux-hwe source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-raspi2-5.3 source package in Bionic: Fix Released Status in linux source package in Focal: Invalid Status in linux-gke-5.3 source package in Focal: Invalid Status in linux-hwe source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-raspi2-5.3 source package in Focal: Invalid Bug description: [Impact] A memory leak may happen when an error happens when setting extended attributes. [Fix] The issue was introduced by an improper backport, so the fix is specific to Ubuntu, so a SAUCE patch. [Test case] Test setting attribute under a user namespace. [Regression potential] A double free bug might be introduced. Or setting extended attributes might fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924611] Re: setting extended attribute may cause memory leak
This bug was fixed in the package linux-hwe - 5.3.0-74.70 --- linux-hwe (5.3.0-74.70) bionic; urgency=medium * bionic/linux-hwe: 5.3.0-74.70 -proposed tracker (LP: #1924647) * setting extended attribute may cause memory leak (LP: #1924611) - SAUCE: vfs_setxattr: free converted value if xattr_permission returns error -- Stefan Bader Fri, 16 Apr 2021 10:22:31 +0200 ** Changed in: linux-raspi2-5.3 (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak Status in linux package in Ubuntu: Invalid Status in linux-gke-5.3 package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-raspi2-5.3 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux-gke-5.3 source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Invalid Status in linux-oem-5.6 source package in Xenial: Invalid Status in linux-raspi2-5.3 source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux-gke-5.3 source package in Bionic: Fix Released Status in linux-hwe source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-raspi2-5.3 source package in Bionic: Fix Released Status in linux source package in Focal: Invalid Status in linux-gke-5.3 source package in Focal: Invalid Status in linux-hwe source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-raspi2-5.3 source package in Focal: Invalid Bug description: [Impact] A memory leak may happen when an error happens when setting extended attributes. [Fix] The issue was introduced by an improper backport, so the fix is specific to Ubuntu, so a SAUCE patch. [Test case] Test setting attribute under a user namespace. [Regression potential] A double free bug might be introduced. Or setting extended attributes might fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924611] Re: setting extended attribute may cause memory leak
This bug was fixed in the package linux-gke-5.3 - 5.3.0-1043.46 --- linux-gke-5.3 (5.3.0-1043.46) bionic; urgency=medium * bionic/linux-gke-5.3: 5.3.0-1043.46 -proposed tracker (LP: #1924650) [ Ubuntu: 5.3.0-74.70 ] * bionic/linux-hwe: 5.3.0-74.70 -proposed tracker (LP: #1924647) * setting extended attribute may cause memory leak (LP: #1924611) - SAUCE: vfs_setxattr: free converted value if xattr_permission returns error -- Stefan Bader Fri, 16 Apr 2021 10:57:46 +0200 ** Changed in: linux-gke-5.3 (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: linux-hwe (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak Status in linux package in Ubuntu: Invalid Status in linux-gke-5.3 package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-raspi2-5.3 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux-gke-5.3 source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Invalid Status in linux-oem-5.6 source package in Xenial: Invalid Status in linux-raspi2-5.3 source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux-gke-5.3 source package in Bionic: Fix Released Status in linux-hwe source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-raspi2-5.3 source package in Bionic: Fix Released Status in linux source package in Focal: Invalid Status in linux-gke-5.3 source package in Focal: Invalid Status in linux-hwe source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-raspi2-5.3 source package in Focal: Invalid Bug description: [Impact] A memory leak may happen when an error happens when setting extended attributes. [Fix] The issue was introduced by an improper backport, so the fix is specific to Ubuntu, so a SAUCE patch. [Test case] Test setting attribute under a user namespace. [Regression potential] A double free bug might be introduced. Or setting extended attributes might fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924611] Re: setting extended attribute may cause memory leak
This bug was fixed in the package linux - 4.4.0-210.242 --- linux (4.4.0-210.242) xenial; urgency=medium * xenial/linux: 4.4.0-210.242 -proposed tracker (LP: #1924644) * setting extended attribute may cause memory leak (LP: #1924611) - SAUCE: vfs_setxattr: free converted value if xattr_permission returns error -- Stefan Bader Fri, 16 Apr 2021 11:33:09 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak Status in linux package in Ubuntu: Invalid Status in linux-gke-5.3 package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-raspi2-5.3 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux-gke-5.3 source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Invalid Status in linux-oem-5.6 source package in Xenial: Invalid Status in linux-raspi2-5.3 source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux-gke-5.3 source package in Bionic: Fix Released Status in linux-hwe source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-raspi2-5.3 source package in Bionic: Fix Released Status in linux source package in Focal: Invalid Status in linux-gke-5.3 source package in Focal: Invalid Status in linux-hwe source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-raspi2-5.3 source package in Focal: Invalid Bug description: [Impact] A memory leak may happen when an error happens when setting extended attributes. [Fix] The issue was introduced by an improper backport, so the fix is specific to Ubuntu, so a SAUCE patch. [Test case] Test setting attribute under a user namespace. [Regression potential] A double free bug might be introduced. Or setting extended attributes might fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1023.24 --- linux-oem-5.10 (5.10.0-1023.24) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1023.24 -proposed tracker (LP: #1924513) * Can't adjust brightness on HP ZBook Fury 17 G7 (LP: #1923000) - SAUCE: drm/i915/dp add a quirk for backlight issue * CIFS DFS entries not accessible with 5.4.0-71.74-generic (LP: #1923670) - Revert "cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag on setting cifs_sb->prepath." -- Stefan Bader Thu, 15 Apr 2021 15:12:17 +0200 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => 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/1923670 Title: CIFS DFS entries not accessible with 5.4.0-71.74-generic Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: When booting 5.4.0-71-generic I can not access DFS entries anymore, with 5.4.0-70-generic this still works. Some details: fstab entry: //example.com/public /home/user/remotecifs noauto,vers=default,noserverino,users,_netdev,user=remote_user,domain=example.com 00 shell session ~$ mount /home/user/remote Password for remote_user@//example.com/public: ~$ ls /home/user/remote/dfs-folder dfs-subfolder dfs-entry ~$ ls /home/user/remote/dfs-folder/dfs-entry ls: cannot access '/home/user/remote/dfs-folder/dfs-entry': No such file or directory dmesg excerpt [ 1219.568778] CIFS: Attempting to mount //DC01.example.com/Public/dfs-folder/dfs-entry [ 1219.584975] FS-Cache: Duplicate cookie detected [ 1219.584986] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.584990] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.584993] FS-Cache: O-key=[6] '5075626c6963' [ 1219.585001] FS-Cache: N-cookie c=a0608786 [p=f4725c61 fl=2 nc=0 na=1] [ 1219.585004] FS-Cache: N-cookie d=a11c1428 n=901f6a53 [ 1219.585007] FS-Cache: N-key=[6] '5075626c6963' [ 1219.725834] FS-Cache: Duplicate cookie detected [ 1219.725847] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.725851] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.725854] FS-Cache: O-key=[6] '5075626c6963' [ 1219.725864] FS-Cache: N-cookie c=0509709f [p=f4725c61 fl=2 nc=0 na=1] [ 1219.725868] FS-Cache: N-cookie d=a11c1428 n=556f158b [ 1219.725870] FS-Cache: N-key=[6] '5075626c6963' [ 1220.216524] CIFS VFS: cifs_read_super: get root inode failed The dmesg from 5.4.0-70-generic does not have the line CIFS VFS: cifs_read_super: get root inode failed ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release: ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release:20.04 20.04 ~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.71.74 Candidate: 5.4.0.71.74 Version table: *** 5.4.0.71.74 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dirk 2946 F pulseaudio /dev/snd/controlC1: dirk 2946 F pulseaudio /dev/snd/controlC0: dirk 2946 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2017-07-27 (1356 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20170614-00:52 MachineType: LENOVO 20HMS00T00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/vg00-lv_root ro intel_iommu=off ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.4.0-71-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: Upgraded to focal on 2020-11-22 (142 days ago) UserGroups: adm cdrom davfs2 dialout dip kvm libvirt lpadmin plugdev roccat sambashare scanner sudo vboxusers _MarkForUpload: False dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO
[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
5.8.0-51 is not in groovy-proposed - developer options (or focal-proposed I'd assume) It's available here: https://launchpad.net/~canonical-kernel-team -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Should be this one: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'
** Changed in: oem-priority Assignee: Yuan-Chen Cheng (ycheng-twn) => Alex Tu (alextu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1923150 Title: unexpected error pop-up after 'apt install nvidia-driver-455' Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Invalid Status in nvidia-graphics-drivers-455 package in Ubuntu: Invalid Bug description: Ubuntu info: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52) Release 20.04 Full reproduce step 1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first place, without all i386 pkg installed. 2. run update-manager to do upgrade. 3. it will show error after download deb and didn't upgrade anything. Per test with the command to do the upgrade, it will have an extra error message, but it will just upgrade and install recommended i386 debs. The error msgs are: E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) Short way to get the error: # apt-get install libgcc-s1:i386 --dry-run Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate Use 'apt autoremove' to remove them. The following additional packages will be installed: gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded. Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) [] Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) [] Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) [] Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, Ubuntu:20.04/focal-security [i386]) Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386]) Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386]) Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386]) E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) For now, we think the above Error is the root cause of update-manager failure. --- This happens as upgrade package nvidia-driver-455 from 455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1. for more detail, please check the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925075] Re: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode
** 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/1925075 Title: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode Status in linux package in Ubuntu: Confirmed Bug description: The Gigabyte R120-T33 platform provides both device-tree and ACPI hardware descriptions. By default, the Linux kernel will boot in device-tree mode. A user can override this and choose ACPI mode by passing acpi=force. This system boots fine in DTB mode, but fails when booted in ACPI mode with acpi=force. [7.936228] ACPI: Power Button [PWRB] [7.941359] ACPI GTDT: [Firmware Bug]: failed to get the Watchdog base address. [7.948807] Unable to handle kernel read from unreadable memory at virtual address 0028 [7.957843] Mem abort info: [7.960625] ESR = 0x9604 [7.963667] EC = 0x25: DABT (current EL), IL = 32 bits [7.968968] SET = 0, FnV = 0 [7.972010] EA = 0, S1PTW = 0 [7.975140] Data abort info: [7.978008] ISV = 0, ISS = 0x0004 [7.981832] CM = 0, WnR = 0 [7.984788] [0028] user address but active_mm is swapper [7.991131] Internal error: Oops: 9604 [#1] SMP [7.996000] Modules linked in: [7.999047] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.11.0-16-generic #17-Ubuntu [8.006606] Hardware name: GIGABYTE R120-T33/MT30-GS1, BIOS F02 08/06/2019 [8.013469] pstate: 40400085 (nZcv daIf +PAN -UAO -TCO BTYPE=--) [8.019465] pc : __ipi_send_mask+0x60/0x114 [8.023645] lr : smp_cross_call+0x3c/0xdc [8.027648] sp : 8000127a3c90 [8.030951] x29: 8000127a3c90 x28: 000a [8.036256] x27: 800011b60510 x26: 8000122e5108 [8.041560] x25: 0001 x24: [8.046864] x23: 8000122ee000 x22: 8000123f8448 [8.052168] x21: 800010fd9a28 x20: 800010fd9a28 [8.056864] Unable to handle kernel read from unreadable memory at virtual address 0028 [8.057472] x19: 000100157c60 x18: 0020 [8.067011] Mem abort info: [8.067013] ESR = 0x9604 [8.072308] [8.072310] x17: c2da3fd1 [8.075089] EC = 0x25: DABT (current EL), IL = 32 bits [8.078131] x16: 1b5980d2 [8.079609] SET = 0, FnV = 0 [8.082998] [8.082999] x15: [8.088295] EA = 0, S1PTW = 0 [8.091684] x14: [8.094725] Data abort info: [8.096203] [8.096204] x13: 003d0900 [8.099591] ISV = 0, ISS = 0x0004 [8.102719] x12: 3d09 [8.106108] CM = 0, WnR = 0 [8.108975] [8.108977] x11: [8.110453] [0028] user address but active_mm is swapper [8.113841] x10: 3d09 [8.138598] x9 : 800010028c80 x8 : 0001 [8.143902] x7 : x6 : 000ff61d7318 [8.149206] x5 : 800011620080 x4 : 800011620150 [8.154510] x3 : 800010fd99e8 x2 : [8.159815] x1 : 800010fd9a28 x0 : [8.165120] Call trace: [8.167556] __ipi_send_mask+0x60/0x114 [8.171383] smp_cross_call+0x3c/0xdc [8.175036] smp_send_reschedule+0x3c/0x50 [8.179123] resched_curr+0x5c/0xb0 [8.182603] check_preempt_curr+0x58/0x90 [8.186604] ttwu_do_wakeup+0x2c/0x1a0 [8.190343] ttwu_do_activate+0x7c/0x114 [8.194256] try_to_wake_up+0x2cc/0x5b0 [8.198082] wake_up_process+0x24/0x30 [8.201821] swake_up_one+0x48/0x9c [8.205300] rcu_gp_kthread_wake+0x68/0x8c [8.209388] rcu_accelerate_cbs_unlocked+0xb4/0xf0 [8.214168] rcu_core+0x208/0x230 [8.217473] rcu_core_si+0x1c/0x30 [8.220865] __do_softirq+0x128/0x3a4 [8.224517] irq_exit+0xc4/0xec [8.227649] __handle_domain_irq+0x8c/0xec [8.231737] gic_handle_irq+0x84/0xfc [8.235389] el1_irq+0xc0/0x180 [8.238520] klist_next+0xc0/0x180 [8.241913] bus_for_each_dev+0x68/0xe0 [8.245740] driver_attach+0x30/0x3c [8.249306] bus_add_driver+0x154/0x250 [8.253131] driver_register+0x84/0x140 [8.256958] __platform_driver_register+0x34/0x40 [8.261653] of_fixed_clk_driver_init+0x28/0x34 [8.266176] do_one_initcall+0x50/0x290 [8.270001] do_initcalls+0x104/0x144 [8.273659] kernel_init_freeable+0x174/0x1c0 [8.278005] kernel_init+0x20/0x134 [8.281486] ret_from_fork+0x10/0x18 [8.285056] Code: a90363f7 aa0103f5 b0010db7 f9401260 (b9402800) [8.291168] ---[ end trace e85c5f6ac85cc1e3 ]--- [8.295774] Kernel panic - not syncing: Oops: Fatal exception in interrupt [8.302655] SMP: stopping secondary CPUs [
[Kernel-packages] [Bug 1925075] Re: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925075 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925075 Title: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode Status in linux package in Ubuntu: Incomplete Bug description: The Gigabyte R120-T33 platform provides both device-tree and ACPI hardware descriptions. By default, the Linux kernel will boot in device-tree mode. A user can override this and choose ACPI mode by passing acpi=force. This system boots fine in DTB mode, but fails when booted in ACPI mode with acpi=force. [7.936228] ACPI: Power Button [PWRB] [7.941359] ACPI GTDT: [Firmware Bug]: failed to get the Watchdog base address. [7.948807] Unable to handle kernel read from unreadable memory at virtual address 0028 [7.957843] Mem abort info: [7.960625] ESR = 0x9604 [7.963667] EC = 0x25: DABT (current EL), IL = 32 bits [7.968968] SET = 0, FnV = 0 [7.972010] EA = 0, S1PTW = 0 [7.975140] Data abort info: [7.978008] ISV = 0, ISS = 0x0004 [7.981832] CM = 0, WnR = 0 [7.984788] [0028] user address but active_mm is swapper [7.991131] Internal error: Oops: 9604 [#1] SMP [7.996000] Modules linked in: [7.999047] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.11.0-16-generic #17-Ubuntu [8.006606] Hardware name: GIGABYTE R120-T33/MT30-GS1, BIOS F02 08/06/2019 [8.013469] pstate: 40400085 (nZcv daIf +PAN -UAO -TCO BTYPE=--) [8.019465] pc : __ipi_send_mask+0x60/0x114 [8.023645] lr : smp_cross_call+0x3c/0xdc [8.027648] sp : 8000127a3c90 [8.030951] x29: 8000127a3c90 x28: 000a [8.036256] x27: 800011b60510 x26: 8000122e5108 [8.041560] x25: 0001 x24: [8.046864] x23: 8000122ee000 x22: 8000123f8448 [8.052168] x21: 800010fd9a28 x20: 800010fd9a28 [8.056864] Unable to handle kernel read from unreadable memory at virtual address 0028 [8.057472] x19: 000100157c60 x18: 0020 [8.067011] Mem abort info: [8.067013] ESR = 0x9604 [8.072308] [8.072310] x17: c2da3fd1 [8.075089] EC = 0x25: DABT (current EL), IL = 32 bits [8.078131] x16: 1b5980d2 [8.079609] SET = 0, FnV = 0 [8.082998] [8.082999] x15: [8.088295] EA = 0, S1PTW = 0 [8.091684] x14: [8.094725] Data abort info: [8.096203] [8.096204] x13: 003d0900 [8.099591] ISV = 0, ISS = 0x0004 [8.102719] x12: 3d09 [8.106108] CM = 0, WnR = 0 [8.108975] [8.108977] x11: [8.110453] [0028] user address but active_mm is swapper [8.113841] x10: 3d09 [8.138598] x9 : 800010028c80 x8 : 0001 [8.143902] x7 : x6 : 000ff61d7318 [8.149206] x5 : 800011620080 x4 : 800011620150 [8.154510] x3 : 800010fd99e8 x2 : [8.159815] x1 : 800010fd9a28 x0 : [8.165120] Call trace: [8.167556] __ipi_send_mask+0x60/0x114 [8.171383] smp_cross_call+0x3c/0xdc [8.175036] smp_send_reschedule+0x3c/0x50 [8.179123] resched_curr+0x5c/0xb0 [8.182603] check_preempt_curr+0x58/0x90 [8.186604] ttwu_do_wakeup+0x2c/0x1a0 [8.190343] ttwu_do_activate+0x7c/0x114 [8.194256] try_to_wake_up+0x2cc/0x5b0 [8.198082] wake_up_process+0x24/0x30 [8.201821] swake_up_one+0x48/0x9c [8.205300] rcu_gp_kthread_wake+0x68/0x8c [8.209388] rcu_accelerate_cbs_unlocked+0xb4/0xf0 [8.214168] rcu_core+0x208/0x230 [8.217473] rcu_core_si+0x1c/0x30 [8.220865] __do_softirq+0x128/0x3a4 [8.224517] irq_exit+0xc4/0xec [8.227649] __handle_domain_irq+0x8c/0xec [8.231737] gic_handle_irq+0x84/0xfc [8.235389] el1_irq+0xc0/0x180 [8.238520] klist_next+0xc0/0x180 [8.241913] bus_for_each_dev+0x68/0xe0 [8.245740] driver_attach+0x30/0x3c [8.249306] bus_add_driver+0x154/0x250 [8.253131] driver_register+0x84/0x140 [8.256958] __platform_driver_register+0x34/0x40 [8.261653] of_fixed_clk_driver_init+0x28/0x34 [8.266176] do_one_initcall+0x50/0x290 [8.270001] do_initcalls+0x104/0x144 [8.273659] kernel_init_freeable+0x174/0x1c0 [8.278005] kernel_init+0x20/0x134 [8.281486] ret_from_fork+0x10/0x18 [8.285056] Code: a90363f7 aa0103f5 b0010db7 f9401260 (b9402800) [8.291168] ---[ end trace
[Kernel-packages] [Bug 1925075] 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 1925075 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: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925075 Title: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode Status in linux package in Ubuntu: Incomplete Bug description: The Gigabyte R120-T33 platform provides both device-tree and ACPI hardware descriptions. By default, the Linux kernel will boot in device-tree mode. A user can override this and choose ACPI mode by passing acpi=force. This system boots fine in DTB mode, but fails when booted in ACPI mode with acpi=force. [7.936228] ACPI: Power Button [PWRB] [7.941359] ACPI GTDT: [Firmware Bug]: failed to get the Watchdog base address. [7.948807] Unable to handle kernel read from unreadable memory at virtual address 0028 [7.957843] Mem abort info: [7.960625] ESR = 0x9604 [7.963667] EC = 0x25: DABT (current EL), IL = 32 bits [7.968968] SET = 0, FnV = 0 [7.972010] EA = 0, S1PTW = 0 [7.975140] Data abort info: [7.978008] ISV = 0, ISS = 0x0004 [7.981832] CM = 0, WnR = 0 [7.984788] [0028] user address but active_mm is swapper [7.991131] Internal error: Oops: 9604 [#1] SMP [7.996000] Modules linked in: [7.999047] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.11.0-16-generic #17-Ubuntu [8.006606] Hardware name: GIGABYTE R120-T33/MT30-GS1, BIOS F02 08/06/2019 [8.013469] pstate: 40400085 (nZcv daIf +PAN -UAO -TCO BTYPE=--) [8.019465] pc : __ipi_send_mask+0x60/0x114 [8.023645] lr : smp_cross_call+0x3c/0xdc [8.027648] sp : 8000127a3c90 [8.030951] x29: 8000127a3c90 x28: 000a [8.036256] x27: 800011b60510 x26: 8000122e5108 [8.041560] x25: 0001 x24: [8.046864] x23: 8000122ee000 x22: 8000123f8448 [8.052168] x21: 800010fd9a28 x20: 800010fd9a28 [8.056864] Unable to handle kernel read from unreadable memory at virtual address 0028 [8.057472] x19: 000100157c60 x18: 0020 [8.067011] Mem abort info: [8.067013] ESR = 0x9604 [8.072308] [8.072310] x17: c2da3fd1 [8.075089] EC = 0x25: DABT (current EL), IL = 32 bits [8.078131] x16: 1b5980d2 [8.079609] SET = 0, FnV = 0 [8.082998] [8.082999] x15: [8.088295] EA = 0, S1PTW = 0 [8.091684] x14: [8.094725] Data abort info: [8.096203] [8.096204] x13: 003d0900 [8.099591] ISV = 0, ISS = 0x0004 [8.102719] x12: 3d09 [8.106108] CM = 0, WnR = 0 [8.108975] [8.108977] x11: [8.110453] [0028] user address but active_mm is swapper [8.113841] x10: 3d09 [8.138598] x9 : 800010028c80 x8 : 0001 [8.143902] x7 : x6 : 000ff61d7318 [8.149206] x5 : 800011620080 x4 : 800011620150 [8.154510] x3 : 800010fd99e8 x2 : [8.159815] x1 : 800010fd9a28 x0 : [8.165120] Call trace: [8.167556] __ipi_send_mask+0x60/0x114 [8.171383] smp_cross_call+0x3c/0xdc [8.175036] smp_send_reschedule+0x3c/0x50 [8.179123] resched_curr+0x5c/0xb0 [8.182603] check_preempt_curr+0x58/0x90 [8.186604] ttwu_do_wakeup+0x2c/0x1a0 [8.190343] ttwu_do_activate+0x7c/0x114 [8.194256] try_to_wake_up+0x2cc/0x5b0 [8.198082] wake_up_process+0x24/0x30 [8.201821] swake_up_one+0x48/0x9c [8.205300] rcu_gp_kthread_wake+0x68/0x8c [8.209388] rcu_accelerate_cbs_unlocked+0xb4/0xf0 [8.214168] rcu_core+0x208/0x230 [8.217473] rcu_core_si+0x1c/0x30 [8.220865] __do_softirq+0x128/0x3a4 [8.224517] irq_exit+0xc4/0xec [8.227649] __handle_domain_irq+0x8c/0xec [8.231737] gic_handle_irq+0x84/0xfc [8.235389] el1_irq+0xc0/0x180 [8.238520] klist_next+0xc0/0x180 [8.241913] bus_for_each_dev+0x68/0xe0 [8.245740] driver_attach+0x30/0x3c [8.249306] bus_add_driver+0x154/0x250 [8.253131] driver_register+0x84/0x140 [8.256958]
[Kernel-packages] [Bug 1925075] [NEW] Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode
Public bug reported: The Gigabyte R120-T33 platform provides both device-tree and ACPI hardware descriptions. By default, the Linux kernel will boot in device- tree mode. A user can override this and choose ACPI mode by passing acpi=force. This system boots fine in DTB mode, but fails when booted in ACPI mode with acpi=force. [7.936228] ACPI: Power Button [PWRB] [7.941359] ACPI GTDT: [Firmware Bug]: failed to get the Watchdog base address. [7.948807] Unable to handle kernel read from unreadable memory at virtual address 0028 [7.957843] Mem abort info: [7.960625] ESR = 0x9604 [7.963667] EC = 0x25: DABT (current EL), IL = 32 bits [7.968968] SET = 0, FnV = 0 [7.972010] EA = 0, S1PTW = 0 [7.975140] Data abort info: [7.978008] ISV = 0, ISS = 0x0004 [7.981832] CM = 0, WnR = 0 [7.984788] [0028] user address but active_mm is swapper [7.991131] Internal error: Oops: 9604 [#1] SMP [7.996000] Modules linked in: [7.999047] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.11.0-16-generic #17-Ubuntu [8.006606] Hardware name: GIGABYTE R120-T33/MT30-GS1, BIOS F02 08/06/2019 [8.013469] pstate: 40400085 (nZcv daIf +PAN -UAO -TCO BTYPE=--) [8.019465] pc : __ipi_send_mask+0x60/0x114 [8.023645] lr : smp_cross_call+0x3c/0xdc [8.027648] sp : 8000127a3c90 [8.030951] x29: 8000127a3c90 x28: 000a [8.036256] x27: 800011b60510 x26: 8000122e5108 [8.041560] x25: 0001 x24: [8.046864] x23: 8000122ee000 x22: 8000123f8448 [8.052168] x21: 800010fd9a28 x20: 800010fd9a28 [8.056864] Unable to handle kernel read from unreadable memory at virtual address 0028 [8.057472] x19: 000100157c60 x18: 0020 [8.067011] Mem abort info: [8.067013] ESR = 0x9604 [8.072308] [8.072310] x17: c2da3fd1 [8.075089] EC = 0x25: DABT (current EL), IL = 32 bits [8.078131] x16: 1b5980d2 [8.079609] SET = 0, FnV = 0 [8.082998] [8.082999] x15: [8.088295] EA = 0, S1PTW = 0 [8.091684] x14: [8.094725] Data abort info: [8.096203] [8.096204] x13: 003d0900 [8.099591] ISV = 0, ISS = 0x0004 [8.102719] x12: 3d09 [8.106108] CM = 0, WnR = 0 [8.108975] [8.108977] x11: [8.110453] [0028] user address but active_mm is swapper [8.113841] x10: 3d09 [8.138598] x9 : 800010028c80 x8 : 0001 [8.143902] x7 : x6 : 000ff61d7318 [8.149206] x5 : 800011620080 x4 : 800011620150 [8.154510] x3 : 800010fd99e8 x2 : [8.159815] x1 : 800010fd9a28 x0 : [8.165120] Call trace: [8.167556] __ipi_send_mask+0x60/0x114 [8.171383] smp_cross_call+0x3c/0xdc [8.175036] smp_send_reschedule+0x3c/0x50 [8.179123] resched_curr+0x5c/0xb0 [8.182603] check_preempt_curr+0x58/0x90 [8.186604] ttwu_do_wakeup+0x2c/0x1a0 [8.190343] ttwu_do_activate+0x7c/0x114 [8.194256] try_to_wake_up+0x2cc/0x5b0 [8.198082] wake_up_process+0x24/0x30 [8.201821] swake_up_one+0x48/0x9c [8.205300] rcu_gp_kthread_wake+0x68/0x8c [8.209388] rcu_accelerate_cbs_unlocked+0xb4/0xf0 [8.214168] rcu_core+0x208/0x230 [8.217473] rcu_core_si+0x1c/0x30 [8.220865] __do_softirq+0x128/0x3a4 [8.224517] irq_exit+0xc4/0xec [8.227649] __handle_domain_irq+0x8c/0xec [8.231737] gic_handle_irq+0x84/0xfc [8.235389] el1_irq+0xc0/0x180 [8.238520] klist_next+0xc0/0x180 [8.241913] bus_for_each_dev+0x68/0xe0 [8.245740] driver_attach+0x30/0x3c [8.249306] bus_add_driver+0x154/0x250 [8.253131] driver_register+0x84/0x140 [8.256958] __platform_driver_register+0x34/0x40 [8.261653] of_fixed_clk_driver_init+0x28/0x34 [8.266176] do_one_initcall+0x50/0x290 [8.270001] do_initcalls+0x104/0x144 [8.273659] kernel_init_freeable+0x174/0x1c0 [8.278005] kernel_init+0x20/0x134 [8.281486] ret_from_fork+0x10/0x18 [8.285056] Code: a90363f7 aa0103f5 b0010db7 f9401260 (b9402800) [8.291168] ---[ end trace e85c5f6ac85cc1e3 ]--- [8.295774] Kernel panic - not syncing: Oops: Fatal exception in interrupt [8.302655] SMP: stopping secondary CPUs [9.350572] SMP: failed to stop secondary CPUs 0,3,9 [9.355527] Kernel Offset: disabled [9.359004] CPU features: 0x00040002,69101108 [9.363350] Memory Limit: none [9.366412] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: hirsute ** Attachment added: "console.log" https://bugs.launchpad.net/bugs/1925075/+attachment/5489891/+files/console.log ** Description changed: + The Gigabyte R120-T33
[Kernel-packages] [Bug 1915661] Re: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions
Added dmesg and lsusb -v output (with kernel paramter mentioned in #4). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915661 Title: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions Status in linux package in Ubuntu: Confirmed Bug description: Hi, the USB UART chip CHG340G is used by many developer ESP2866 boards to connect to USB serial. The standard kernel driver des support a lot of those CH340x chipset but it does currently not support the WDH CH340g with standard ch341 driver. Nevertheless there exists a working driver from the vendor since yaers. http://www.wch.cn/downloads/CH341PAR_LINUX_ZIP.html https://sparks.gogo.co.nz/assets/_site_/downloads/CH340_LINUX.zip https://sparks.gogo.co.nz/ch340.html Is it possable to get the mainlaine driver updated to support CHG340G out of the box without patching recompiling custom kernel. There are milions of CH340g chips on those ESP2866 boards out there. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-43-generic 5.8.0-43.49 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1412 F pulseaudio christian 1416 F pipewire-media- /dev/snd/seq:christian 1411 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Feb 14 22:23:38 2021 InstallationDate: Installed on 2018-11-27 (810 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 4349WJK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=980616fe-1ce0-41c1-b148-e64e68fdcce7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-13 (1 days ago) dmi.bios.date: 09/26/2012 dmi.bios.release: 1.82 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4349WJK dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4349WJK:pvrThinkPadT510:rvnLENOVO:rn4349WJK:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T510 dmi.product.name: 4349WJK dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915661] Re: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions
** Attachment added: "lsusb-v_AZ-Delivery_CH430G.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915661/+attachment/5489889/+files/lsusb-v_AZ-Delivery_CH430G.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/1915661 Title: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions Status in linux package in Ubuntu: Confirmed Bug description: Hi, the USB UART chip CHG340G is used by many developer ESP2866 boards to connect to USB serial. The standard kernel driver des support a lot of those CH340x chipset but it does currently not support the WDH CH340g with standard ch341 driver. Nevertheless there exists a working driver from the vendor since yaers. http://www.wch.cn/downloads/CH341PAR_LINUX_ZIP.html https://sparks.gogo.co.nz/assets/_site_/downloads/CH340_LINUX.zip https://sparks.gogo.co.nz/ch340.html Is it possable to get the mainlaine driver updated to support CHG340G out of the box without patching recompiling custom kernel. There are milions of CH340g chips on those ESP2866 boards out there. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-43-generic 5.8.0-43.49 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1412 F pulseaudio christian 1416 F pipewire-media- /dev/snd/seq:christian 1411 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Feb 14 22:23:38 2021 InstallationDate: Installed on 2018-11-27 (810 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 4349WJK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=980616fe-1ce0-41c1-b148-e64e68fdcce7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-13 (1 days ago) dmi.bios.date: 09/26/2012 dmi.bios.release: 1.82 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4349WJK dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4349WJK:pvrThinkPadT510:rvnLENOVO:rn4349WJK:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T510 dmi.product.name: 4349WJK dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915661] Re: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions
** Attachment added: "dmesg_AZ-Delivery_D1R2_CH430G.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915661/+attachment/5489888/+files/dmesg_AZ-Delivery_D1R2_CH430G.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/1915661 Title: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions Status in linux package in Ubuntu: Confirmed Bug description: Hi, the USB UART chip CHG340G is used by many developer ESP2866 boards to connect to USB serial. The standard kernel driver des support a lot of those CH340x chipset but it does currently not support the WDH CH340g with standard ch341 driver. Nevertheless there exists a working driver from the vendor since yaers. http://www.wch.cn/downloads/CH341PAR_LINUX_ZIP.html https://sparks.gogo.co.nz/assets/_site_/downloads/CH340_LINUX.zip https://sparks.gogo.co.nz/ch340.html Is it possable to get the mainlaine driver updated to support CHG340G out of the box without patching recompiling custom kernel. There are milions of CH340g chips on those ESP2866 boards out there. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-43-generic 5.8.0-43.49 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1412 F pulseaudio christian 1416 F pipewire-media- /dev/snd/seq:christian 1411 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Feb 14 22:23:38 2021 InstallationDate: Installed on 2018-11-27 (810 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 4349WJK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=980616fe-1ce0-41c1-b148-e64e68fdcce7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-13 (1 days ago) dmi.bios.date: 09/26/2012 dmi.bios.release: 1.82 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4349WJK dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4349WJK:pvrThinkPadT510:rvnLENOVO:rn4349WJK:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T510 dmi.product.name: 4349WJK dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915661] Re: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions
** Attachment added: "dmesg_NodeMCU_Lolin_CH430G.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915661/+attachment/5489886/+files/dmesg_NodeMCU_Lolin_CH430G.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/1915661 Title: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions Status in linux package in Ubuntu: Confirmed Bug description: Hi, the USB UART chip CHG340G is used by many developer ESP2866 boards to connect to USB serial. The standard kernel driver des support a lot of those CH340x chipset but it does currently not support the WDH CH340g with standard ch341 driver. Nevertheless there exists a working driver from the vendor since yaers. http://www.wch.cn/downloads/CH341PAR_LINUX_ZIP.html https://sparks.gogo.co.nz/assets/_site_/downloads/CH340_LINUX.zip https://sparks.gogo.co.nz/ch340.html Is it possable to get the mainlaine driver updated to support CHG340G out of the box without patching recompiling custom kernel. There are milions of CH340g chips on those ESP2866 boards out there. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-43-generic 5.8.0-43.49 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1412 F pulseaudio christian 1416 F pipewire-media- /dev/snd/seq:christian 1411 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Feb 14 22:23:38 2021 InstallationDate: Installed on 2018-11-27 (810 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 4349WJK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=980616fe-1ce0-41c1-b148-e64e68fdcce7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-13 (1 days ago) dmi.bios.date: 09/26/2012 dmi.bios.release: 1.82 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4349WJK dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4349WJK:pvrThinkPadT510:rvnLENOVO:rn4349WJK:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T510 dmi.product.name: 4349WJK dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915661] Re: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions
** Attachment added: "lsusb-v_NodeMCU_Lolin_CH340G.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915661/+attachment/5489887/+files/lsusb-v_NodeMCU_Lolin_CH340G.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/1915661 Title: WDH - CH340G USB UART not supported by ch341 driver in all chip revisions Status in linux package in Ubuntu: Confirmed Bug description: Hi, the USB UART chip CHG340G is used by many developer ESP2866 boards to connect to USB serial. The standard kernel driver des support a lot of those CH340x chipset but it does currently not support the WDH CH340g with standard ch341 driver. Nevertheless there exists a working driver from the vendor since yaers. http://www.wch.cn/downloads/CH341PAR_LINUX_ZIP.html https://sparks.gogo.co.nz/assets/_site_/downloads/CH340_LINUX.zip https://sparks.gogo.co.nz/ch340.html Is it possable to get the mainlaine driver updated to support CHG340G out of the box without patching recompiling custom kernel. There are milions of CH340g chips on those ESP2866 boards out there. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-43-generic 5.8.0-43.49 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1412 F pulseaudio christian 1416 F pipewire-media- /dev/snd/seq:christian 1411 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Feb 14 22:23:38 2021 InstallationDate: Installed on 2018-11-27 (810 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 4349WJK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=980616fe-1ce0-41c1-b148-e64e68fdcce7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-13 (1 days ago) dmi.bios.date: 09/26/2012 dmi.bios.release: 1.82 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4349WJK dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4349WJK:pvrThinkPadT510:rvnLENOVO:rn4349WJK:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T510 dmi.product.name: 4349WJK dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
It doesn't appear to affect all of the cloud kernels. Only focal:linux- kvm and focal:linux-azure that I've found (though that is not an exhaustive list). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918793] Re: HP m400 cartridges fail to find NIC when deploying hirsute
This bug was fixed in the package linux - 5.11.0-16.17
---
linux (5.11.0-16.17) hirsute; urgency=medium
* hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI
(LP: #1922403)
- SAUCE: efifb: Check efifb_pci_dev before using it
-- Seth Forshee Wed, 14 Apr 2021 14:31:58
-0500
** Changed in: linux (Ubuntu)
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/1918793
Title:
HP m400 cartridges fail to find NIC when deploying hirsute
Status in linux package in Ubuntu:
Fix Released
Bug description:
They do not appear to find the Mellanox NIC:
[0.00] Linux version 5.10.0-14-generic (buildd@bos02-arm64-008) (gcc
(Ubuntu 10.2.1-6ubuntu2) 10.2.1 20210121, GNU ld (GNU Binutils for Ubuntu)
2.36) #15-Ubuntu SMP Fri Jan 29 15:08:45 UTC 2021 (Ubuntu 5.10.0-14.15-generic
5.10.11)
[0.00] Machine model: HP ProLiant m400 Server Cartridge
[0.00] efi: UEFI not found.
[...]
ipconfig: BOOTIF: SIOCGIFINDEX: No such device
ipconfig: no devices to configure
[...]
(initramfs) cat /proc/cmdline
nomodeset ro
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/xgene-uboot/hirsute/stable/squashfs
ip=ms10-35-mcdivittB0-kernel:BOOTIF ip6=off overlayroot=tmpfs
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc
cloud-config-url=http://10.229.32.21:5248/MAAS/metadata/latest/by-id/chbcrm/?op=get_preseed
apparmor=0 log_host=10.229.32.21 log_port=5247 --- console=ttyS0,9600n8r
BOOTIF=01-14-58-d0-58-c3-c2
(initramfs) ls /sys/class/net
lo
(initramfs)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918793/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922403] Re: hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI
This bug was fixed in the package linux - 5.11.0-16.17 --- linux (5.11.0-16.17) hirsute; urgency=medium * hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI (LP: #1922403) - SAUCE: efifb: Check efifb_pci_dev before using it -- Seth Forshee Wed, 14 Apr 2021 14:31:58 -0500 ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) inside a Hyper-V Gen 2 Virtual Machine with UEFI enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923084] Re: duplicate consoles on riscv64
This bug was fixed in the package linux-riscv - 5.11.0-1007.7 --- linux-riscv (5.11.0-1007.7) hirsute; urgency=medium [ Ubuntu: 5.11.0-16.17 ] * hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI (LP: #1922403) - SAUCE: efifb: Check efifb_pci_dev before using it -- Seth Forshee Wed, 14 Apr 2021 14:53:29 -0500 ** Changed in: linux-riscv (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923084 Title: duplicate consoles on riscv64 Status in linux-riscv package in Ubuntu: Fix Released Bug description: When booting on SiFive boards, there are two gettys launched on the same console. There is sifive serial console which is the active/only physical console. But also, there is serial console exposed over legacy opensbi extension; which in linux kernel is implemented as hvc0 console, which systemd starts getty for. The issue is that the both consoles are actually the same one. Thus some other distros chose to hard-code disable hvc0 console on riscv64. But given that the legacy sbi serial console extension will eventually go away, it makes sense to disable that in the kernel out right. By setting: +# CONFIG_RISCV_SBI_V01 is not set +# CONFIG_SERIAL_EARLYCON_RISCV_SBI is not set +# CONFIG_HVC_RISCV_SBI is not set This way sifive0 console will be discovered and used automatically; ditto earlyprintk without needing to specify sbi or explicitely set sifive0 console. This will also improve UX experience with just a single getty on the serial connection. Before the patch is applied: # ls /run/systemd/generator/getty.target.wants/ serial-getty@hvc0.service serial-getty@ttySIF0.service After the patch is applied: $ sudo ls /run/systemd/generator/getty.target.wants/ serial-getty@ttySIF0.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: i7-8565U, sig=0x806eb/20190514, intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Same on my ASUS UX305UA. I haven't been able to boot into Kernel patch levels newer than 4.15.0-118 for a while now. A few days ago even that would only boot sporadically anymore (about every 1 out of 5 times). Updating to BIOS version 302 solved it all for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: i7-8565U, sig=0x806eb/20190514, intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 WORKAROUND 3: upgrade BIOS Asus has released updated BIOSes, which probably include the newest microcode. After upgrading workarounds 1,2 are not needed. Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be (easily) reverted. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to:
[Kernel-packages] [Bug 1925056] Re: Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem
** Description changed: Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. There is something funky going on in the kernel, hence I attached the dmesg kernel messages since system boot. All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. + + I tried the 5.4 kernel series and the latest one (5.4.0-72-generic) was + also working fine. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. I read about bluetooth vulnerability fixes in exactly the version where the problem started here: https://ubuntu.com/security/notices/USN-4752-1 Maybe that has something to do with the issue? Can somebody reproduce this issue? lsb_release -rd ``` Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1925056 Title: Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem Status in linux-meta-oem-5.6 package in Ubuntu: New Bug description: Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. There is something funky going on in the kernel, hence I attached the dmesg kernel messages since system boot. All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. I tried the 5.4 kernel series and the latest one (5.4.0-72-generic) was also working fine. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. I read about bluetooth vulnerability fixes in exactly the version where the problem started here: https://ubuntu.com/security/notices/USN-4752-1 Maybe that has something to do with the issue? Can somebody reproduce this issue? lsb_release -rd ``` Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.6/+bug/1925056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925056] Re: Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem
** Attachment added: "lspci output" https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.6/+bug/1925056/+attachment/5489851/+files/lspci.txt ** Description changed: Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. + I read about bluetooth vulnerability fixes in exactly the version where the problem started here: https://ubuntu.com/security/notices/USN-4752-1 + Maybe that has something to do with the issue? + Can somebody reproduce this issue? + lsb_release -rd ``` Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` - - lspci - ``` - 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) - 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) - 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) - 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model - 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) - 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) - 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) - 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) - 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) - 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) - 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) - 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) - 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) - 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) - 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) - 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) - 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) - 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) - 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) - 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) - 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) - 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) - 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) - 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) - 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) - 05:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) - 20:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) - 21:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] - 22:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] - 22:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] - 3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 - ``` ** Description changed: - Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. - All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. + Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to + hang and finally freezes when I want to connect to my AV-receiver over + bluetooth. There is something funky going on in the kernel, hence I + attached the dmesg kernel messages since system boot. + + All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence + I'm still booting 5.6.0-1047-oem currently. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. I read about bluetooth
[Kernel-packages] [Bug 1925056] [NEW] Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem
Public bug reported: Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. There is something funky going on in the kernel, hence I attached the dmesg kernel messages since system boot. All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. I tried the 5.4 kernel series and the latest one (5.4.0-72-generic) was also working fine. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. I read about bluetooth vulnerability fixes in exactly the version where the problem started here: https://ubuntu.com/security/notices/USN-4752-1 Maybe that has something to do with the issue? Can somebody reproduce this issue? lsb_release -rd ``` Description:Ubuntu 20.04.2 LTS Release:20.04 ``` ** Affects: linux-meta-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Tags: 9380 bluetooth crash dell xps ** Attachment added: "dmesg output" https://bugs.launchpad.net/bugs/1925056/+attachment/5489843/+files/bluetooth_crash_dmesg.txt ** Package changed: gnome-shell (Ubuntu) => linux-meta-oem-5.6 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1925056 Title: Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem Status in linux-meta-oem-5.6 package in Ubuntu: New Bug description: Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. There is something funky going on in the kernel, hence I attached the dmesg kernel messages since system boot. All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. I tried the 5.4 kernel series and the latest one (5.4.0-72-generic) was also working fine. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. I read about bluetooth vulnerability fixes in exactly the version where the problem started here: https://ubuntu.com/security/notices/USN-4752-1 Maybe that has something to do with the issue? Can somebody reproduce this issue? lsb_release -rd ``` Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.6/+bug/1925056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925056] [NEW] Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem
You have been subscribed to a public bug: Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. Can somebody reproduce this issue? lsb_release -rd ``` Description:Ubuntu 20.04.2 LTS Release:20.04 ``` lspci ``` 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1c.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #7 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 20:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) 21:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 22:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 22:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 ``` ** Affects: linux-meta-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Tags: 9380 bluetooth crash dell xps -- Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem https://bugs.launchpad.net/bugs/1925056 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 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 1921769] Re: Backport mlx5e fix for tunnel offload
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1921769 Title: Backport mlx5e fix for tunnel offload Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Bionic: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-azure source package in Groovy: Confirmed Status in linux source package in Hirsute: Fix Released Status in linux-azure source package in Hirsute: Confirmed Bug description: [SRU Justification] We've discovered an issue on Ubuntu 20.04 when used with Kubernetes CNIs that perform offloading using Geneve that causes the kernel to panic on Azure instances with accelerated networking with the following errors: [ 307.561223] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 0x3d4, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 307.573864] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5 [ 307.764902] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 0x3d7, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 307.777332] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5 [ 322.814393] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x218, ci 0x1a7, sqn 0x2bd, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 322.826685] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2bd NVIDIA fixed this issue in https://github.com/torvalds/linux/commit/5ccc0ecda9e8a67add654d93d7e0ac4346c0fa22 , so we're looking to have this backported to at least the linux-azure package. [Test Plan] Spin up a Kubernetes CNI that uses Geneve offloading [Where problems could occur] Its possible some traffic won't get geneve acceleration. This patch has been backported to v5.10.y and v5.11.y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Re: Packaging resync
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Committed Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900438] Re: Bcache bypasse writeback on caching device with fragmentation
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1900438
Title:
Bcache bypasse writeback on caching device with fragmentation
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
[Impact]
This bug in bcache affects I/O performance on all versions of the kernel
[correct versions affected]. It is particularly negative on ceph if used with
bcache.
Write I/O latency would suddenly go to around 1 second from around 10
ms when hitting this issue and would easily be stuck there for hours
or even days, especially bad for ceph on bcache architecture. This
would make ceph extremely slow and make the entire cloud almost
unusable.
The root cause is that the dirty bucket had reached the 70 percent
threshold, thus causing all writes to go direct to the backing HDD
device. It might be fine if it actually had a lot of dirty data, but
this happens when dirty data has not even reached over 10 percent, due
to having high memory fragmentation. What makes it worse is that the
writeback rate might be still at minimum value (8) due to the
writeback percent not reached, so it takes ages for bcache to really
reclaim enough dirty buckets to get itself out of this situation.
[Fix]
* 71dda2a5625f31bc3410cb69c3d31376a2b66f28 “bcache: consider the
fragmentation when update the writeback rate”
The current way to calculate the writeback rate only considered the dirty
sectors.
This usually works fine when memory fragmentation is not high, but it will
give us an unreasonably low writeback rate when we are in the situation that a
few dirty sectors have consumed a lot of dirty buckets. In some cases, the
dirty buckets reached CUTOFF_WRITEBACK_SYNC (i.e., stopped writeback) while
the dirty data (sectors) had not even reached the writeback_percent threshold
(i.e., started writeback). In that situation, the writeback rate will still be
the minimum value (8*512 = 4KB/s), thus it will cause all the writes to bestuck
in a non-writeback mode because of the slow writeback.
We accelerate the rate in 3 stages with different aggressiveness:
the first stage starts when dirty buckets percent reach above
BCH_WRITEBACK_FRAGMENT_THRESHOLD_LOW (50),
the second is BCH_WRITEBACK_FRAGMENT_THRESHOLD_MID (57),
the third is BCH_WRITEBACK_FRAGMENT_THRESHOLD_HIGH (64).
By default the first stage tries to writeback the amount of dirty data
in one bucket (on average) in (1 / (dirty_buckets_percent - 50)) seconds,
the second stage tries to writeback the amount of dirty data in one bucket
in (1 / (dirty_buckets_percent - 57)) * 100 milliseconds, the third
stage tries to writeback the amount of dirty data in one bucket in
(1 / (dirty_buckets_percent - 64)) milliseconds.
The initial rate at each stage can be controlled by 3 configurable
parameters:
writeback_rate_fp_term_{low|mid|high}
They are by default 1, 10, 1000, chosen based on testing and
production data, detailed below.
A. When it comes to the low stage, it is still far from the 70%
threshold, so we only want to give it a little bit push by setting the
term to 1, it means the initial rate will be 170 if the fragment is 6,
it is calculated by bucket_size/fragment, this rate is very small,
but still much more reasonable than the minimum 8.
For a production bcache with non-heavy workload, if the cache device
is bigger than 1 TB, it may take hours to consume 1% buckets,
so it is very possible to reclaim enough dirty buckets in this stage,
thus to avoid entering the next stage.
B. If the dirty buckets ratio didn’t turn around during the first stage,
it comes to the mid stage, then it is necessary for mid stage
to be more aggressive than low stage, so the initial rate is chosen
to be 10 times more than the low stage, which means 1700 as the initial
rate if the fragment is 6. This is a normal rate
we usually see for a normal workload when writeback happens
[Kernel-packages] [Bug 1909428] Re: eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with unexpected operator on F-5.8
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1909428
Title:
eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with
unexpected operator on F-5.8
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[Impact]
The fail check in the end of powerpc/eeh/eeh-basic.sh script will complain
about "unexpected operator"
This is caused by the following line in the script:
$ test "$failed" == 0
/bin/sh: 4: test: 0: unexpected operator
[Fix]
* 3db380570af705 ("selftests/powerpc: Make the test check in eeh-basic.sh
posix compliant")
This is affecting F/G/H and can be cherry-picked for all of them.
[Test case]
Run the eeh-basic.sh script in tools/testing/selftests/powerpc/eeh/
This error message should be gone.
[Where problems could occur]
This fix is limited to PowerPC testing tool, it's unlike to cause any issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909428/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910323] Re: Fix implicit declaration warnings for kselftests/memfd test on newer releases
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1910323
Title:
Fix implicit declaration warnings for kselftests/memfd test on newer
releases
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
While debugging bug 1910277, I found that the test compilation will
print some warnings:
memfd_test.c:64:7: warning: implicit declaration of function ‘open’;
memfd_test.c:90:6: warning: implicit declaration of function ‘fcntl’
memfd_test.c:397:6: warning: implicit declaration of function ‘fallocate’;
fuse_test.c:67:6: warning: implicit declaration of function ‘fcntl’
fuse_test.c:261:7: warning: implicit declaration of function ‘open’;
It's harmless but fixing this we can make the test report easier to
read.
[Fix]
* 1c49e3783f8899 ("selftests/memfd: Fix implicit declaration warnings")
This fix can be cherry-picked into F/F-oem-5.6/G and compiled without
any problem. Older kernel does not have this issue since they're
missing some other commits.
[Test Case]
Build the memfd test in tools/testing/selftests/ with:
sudo make TARGETS=memfd
With this fix, these warnings will be gone.
[Where problems could occur]
This fix is just for fixing the test case compilation, so it's not
affecting real kernel functionality.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910323/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1921104 Title: net/mlx5e: Add missing capability check for uplink follow Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * Since older firmware may not support the uplink state setting, this can lead to problems. * Now expose firmware indication that it supports setting eswitch uplink state to follow the physical link. * If a kernel without the backport is used on an adapter which does not have the latest adapter firmware, the adapter silently drops outgoing traffic. * This is a regression which was introduced with kernel 5.4.0-48. [Fix] * upstream fix (as in 5.11): 9c9be85f6b59d80efe4705109c0396df18d4e11d 9c9be85f6b59 "net/mlx5e: Add missing capability check for uplink follow" * backport for focal: https://launchpadlibrarian.net/529543695/0001 -Backport-net-mlx5e-Add-missing-capability-check-for-.patch * backport for groovy: https://launchpadlibrarian.net/529775887/0001 -Backport-groovy-net-mlx5e-Add-missing-capability-che.patch [Test Case] * Two IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04 or 20.10 on LPAR, are needed. * Each with RoCE Express 2.x adapters (Mellanox ConnectX4/5) attached and firmware 16.29.1006 or earlier. * Assign an IP address to the adapters on both systems and try to ping one node from the other. * The ping will just fail with the stock Ubuntu kernels (not having the patch), but will succeed with kernels that incl. the patches (like the test builds from the PPA mentioned below). * Due to the lack of hardware this needs to be verified by IBM. [Regression Potential] * Undesired / erroneous behavior in case the modified if condition is assembled in a wrong way. * Again wrong behavior in case the modification of the capability bits in mlx5_ifc_cmd_hca_cap_bits are wrong. * All modification are limited to the mlx5 driver only. * The changes are relatively limited with effectively two lines removed and 4 added (three of them adjustments of the capability bits only). * The modifications were done and tested by IBM and reviewed by Mellanox (see LP comments), based on a PPA test build. [Other] * The above patch/commit was upstream accepted with kernel 5.11. * Hence the patch is not needed for hirsute, just needs to be SRUed for groovy and focal. * The commit couldn't be cleanly cherry-picked, mainly due to changed context, hence the backport(s). __ Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921769] Re: Backport mlx5e fix for tunnel offload
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1921769 Title: Backport mlx5e fix for tunnel offload Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Bionic: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-azure source package in Groovy: Confirmed Status in linux source package in Hirsute: Fix Released Status in linux-azure source package in Hirsute: Confirmed Bug description: [SRU Justification] We've discovered an issue on Ubuntu 20.04 when used with Kubernetes CNIs that perform offloading using Geneve that causes the kernel to panic on Azure instances with accelerated networking with the following errors: [ 307.561223] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 0x3d4, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 307.573864] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5 [ 307.764902] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 0x3d7, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 307.777332] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5 [ 322.814393] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x218, ci 0x1a7, sqn 0x2bd, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 322.826685] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2bd NVIDIA fixed this issue in https://github.com/torvalds/linux/commit/5ccc0ecda9e8a67add654d93d7e0ac4346c0fa22 , so we're looking to have this backported to at least the linux-azure package. [Test Plan] Spin up a Kubernetes CNI that uses Geneve offloading [Where problems could occur] Its possible some traffic won't get geneve acceleration. This patch has been backported to v5.10.y and v5.11.y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921498] Re: [UBUNUT 21.04] s390/vtime: fix increased steal time accounting
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1921498
Title:
[UBUNUT 21.04] s390/vtime: fix increased steal time accounting
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* The reported steal time on s390x is erroneously increasing and
therefore broken.
* This problem got introduced with commit 152e9b8676c6e
("s390/vtime: steal time exponential moving average") - upstream with v5.1
[Fix]
* d54cb7d54877d529bc1e0e1f47a3dd082f73add3 d54cb7d54877 "s390/vtime:
fix increased steal time accounting"
[Test Case]
* An IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04,
20.10 and 21.04 on LPAR, are needed.
* The system needs to be configured as KVM host with one or more KVM
guests.
* Now put significant workload on the guest(s), so that the hypervisor starts
to 'steal time'.
This can be best forced by having only very limited CPU resources for the
hypervisor itself.
* Start monitoring the steal time, that is reported at /proc/stat,
but can be more easily verified with tools like vmstat or even top.
* If the steal time starts ever growing (exponentially), the situation
is broken.
* In case the steal time stays relatively constant,
or grows only very limited after a ramp up phase of some minutes,
or just oscillates around a certain value, a fixed/patched kernel is in use.
[Regression Potential]
* The patch only changes the single line that calculates:
account_steal_time
* In case the account_steal_time calculation is still broken after the
modification,
the steal time is just again not reported correctly on s390x,
but maybe in a different way (rather than exponentially growing).
* But it will not further harm virtualization on s390x systems.
* The modification is very limited with that one line change.
* The commit got upstream accepted with 5.12-rc4.
[Other]
* Since the patch is needed for kernel higher than 5.1 and got upstream
accepted with 5.12-rc4,
hirsute, groovy and focal are affected.
* The upstream commit can be cleanly cherry-picked from all three affected
Ubuntu releases.
__
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921498/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922738] Re: 5.4 kernel: when iommu is on crashdump fails
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1922738 Title: 5.4 kernel: when iommu is on crashdump fails Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [IMPACT] When iommu is enabled crashdump fails to be collected because crash-kernel crashes with following trace [1]. Commits that address it : 1ddb32da4a62 iommu/vt-d: Simplify check in identity_mapping() 96d170f3b1a6 iommu/vt-d: Remove deferred_attach_domain() a11bfde9c77d iommu/vt-d: Do deferred attachment in iommu_need_mapping() 034d98cc0cdc iommu/vt-d: Move deferred device attachment into helper function 1d4615978f52 iommu/vt-d: Add attach_deferred() helper 1ee0186b9a12 iommu/vt-d: Refactor find_domain() helper [TEST CASE] Install a 5.4 kernel, add intel_iommu=on and iommu=pt to grub cmdline and trigger a crash. The crash kernel that boots will crash with trace [1]. [REGRESSION POTENTIAL] 1) 1ee0186b9a12 iommu/vt-d: Refactor find_domain() helper Refactors find_domain() into two helpers: 1) find_domain() only returns the domain in use; 2) deferred_attach_domain() does the deferred domain attachment if required and return the domain in use. 2) 1d4615978f52 iommu/vt-d: Add attach_deferred() helper Add helper function to check if a device's attach process is deffered. Before this commit, this check was done with "dev->archdata.iommu == DEFER_DEVICE_DOMAIN_INFO". This commit wraps it into a function. Fixes (1). 3) 034d98cc0cdc iommu/vt-d: Move deferred device attachment into helper function Takes the code that does the deffered attachment from deferred_attach_domain() function and places it in new do_deferred_attach() function. Fixes (1). 4) a11bfde9c77d iommu/vt-d: Do deferred attachment in iommu_need_mapping() This one actually fixes the bug. Attachement of devive needs to happen before checking if device is identity mapped. Fixes (1). 5) 96d170f3b1a6 iommu/vt-d: Remove deferred_attach_domain() Code cleanup, removes deferred_attach_domain() which now is just a wrapper around find_domain and calls directly find_domain from caller sites. Fixes (1). 6) 1ddb32da4a62 iommu/vt-d: Simplify check in identity_mapping() Code cleanup. Fixes (1). Commits 2,3,5, and 6 are code movements/cleanups so little regression potential. Commit 1 is the intial code refactroring ( the rest of commits fix it) and commit 3 fixes the bug. So far testing has not revealed any regression. Any possible regression will regard device deffered attachment. [OTHER] Kernel affected 5.4. [1] https://pastebin.ubuntu.com/p/FNxTxjg3DV/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489834/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489832/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489833/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489831/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489830/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489829/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489828/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489827/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489826/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
apport information ** Tags added: apport-collected focal uec-images ** Description changed: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CRDA: N/A + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 + ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-1038-kvm N/A + linux-backports-modules-5.4.0-1038-kvm N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.4.0-1038-kvm x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.12.0-1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-2.7 + dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-2.7 + dmi.sys.vendor: QEMU ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489825/+files/AudioDevicesInUse.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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A
[Kernel-packages] [Bug 1925030] Re: [21.04 FEAT] SCLP extended length SCCBs
This was more added for the reason of completeness, since it became upstream accepted with 5.10 and we are on final kernel target level 5.11, hence I can be set to Fix Released right away. ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: New => Fix Released ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925030 Title: [21.04 FEAT] SCLP extended length SCCBs Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Make use of SCLP's "extended-length-SCCB facility" for READ SCP INFO (FORCED) and READ CPU INFORMATION. The current limitation to 4k SCCB might cause issues for future machines with many CPUs. For such machines with ~240 CPUs the information for all CPUs cannot be provided within the response of READ CPU INFORMATION. To avoid this problem make use of extended length SCCBs. Available with kernel 5.10. Therefore upstream integrated with Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] 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 1925008 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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Incomplete Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925026] Re: Timer of 100us causes 64-bit app spin on Pi4
** Tags added: raspi-image -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925026 Title: Timer of 100us causes 64-bit app spin on Pi4 Status in linux package in Ubuntu: Confirmed Bug description: This problem happens with 64-bit 20.04 LTS or 20.10 on a Raspberry Pi 4 w/4GB (I am using the official Ubuntu Pi versions). It does NOT happen with either version when running on a standard x86 machine or VM. Also, it does NOT happen when using the 64-bit Raspberry Pi OS (https://downloads.raspberrypi.org/raspios_arm64/images/). So this issue is specific to the official 64-bit Ubuntu on Raspberry Pi version. When a 100us timer is started (via setitimer) the app will spin at 100%. With values slightly higher (150, 200, 1000) this does not happen. I've included the source for a small timer test program that I found reproduces the issue that broke my larger formal app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
Marking affects linux, so the kernel folks can weigh in on this. ** Also 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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Incomplete Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
Hi, I don't think that's a viable option as cloud-init may very well be
the component that allows the network interface to be configured with a
routable address, so we can't wait such an address to be available
before configuring the machine, at least not in general.
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
New
Status in linux-azure package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes the SSH key is not setup properly and the user
cannot log into the VM.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM to debug, run:
```
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925026] Re: Timer of 100us causes 64-bit app spin on Pi4
** 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/1925026 Title: Timer of 100us causes 64-bit app spin on Pi4 Status in linux package in Ubuntu: Confirmed Bug description: This problem happens with 64-bit 20.04 LTS or 20.10 on a Raspberry Pi 4 w/4GB (I am using the official Ubuntu Pi versions). It does NOT happen with either version when running on a standard x86 machine or VM. Also, it does NOT happen when using the 64-bit Raspberry Pi OS (https://downloads.raspberrypi.org/raspios_arm64/images/). So this issue is specific to the official 64-bit Ubuntu on Raspberry Pi version. When a 100us timer is started (via setitimer) the app will spin at 100%. With values slightly higher (150, 200, 1000) this does not happen. I've included the source for a small timer test program that I found reproduces the issue that broke my larger formal app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924970] Re: Add soundwire sdca codec support
Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1924970 Title: Add soundwire sdca codec support Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Committed Bug description: [Impact] * The output device in sound settings will non-functional. Sound input device will be empty. An upstream commit add supports for SDW sdca codec support. [Test Plan] * Open settings and select Sound column. Testing speaker won't have any sound output. * Try to update files mentioned here https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/a7f348bb37d2b3254801702299ab2c76833a3c16 https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/651c2c851bf17a1d76e0a046eb33eccbcf98845f * alsactl init * Open settings and select Sound column and test output device again. Sound devices work properly. [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. [Other Info] * The change has been verified on Dell machine with sdca codec. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924970] Re: Add soundwire sdca codec support
Hi @seb128, I don't know if G also need it or not. Since it's not LTS, I think we don't need it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1924970 Title: Add soundwire sdca codec support Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Committed Bug description: [Impact] * The output device in sound settings will non-functional. Sound input device will be empty. An upstream commit add supports for SDW sdca codec support. [Test Plan] * Open settings and select Sound column. Testing speaker won't have any sound output. * Try to update files mentioned here https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/a7f348bb37d2b3254801702299ab2c76833a3c16 https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/651c2c851bf17a1d76e0a046eb33eccbcf98845f * alsactl init * Open settings and select Sound column and test output device again. Sound devices work properly. [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. [Other Info] * The change has been verified on Dell machine with sdca codec. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924611] Re: setting extended attribute may cause memory leak
$ uname -a Linux focal 5.6.0-1055-oem #59-Ubuntu SMP Fri Apr 16 08:43:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ ./leak.sh $ echo $? 0 $ ** Changed in: linux-hwe (Ubuntu) Status: New => Invalid ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak Status in linux package in Ubuntu: Invalid Status in linux-gke-5.3 package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-raspi2-5.3 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-gke-5.3 source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Invalid Status in linux-oem-5.6 source package in Xenial: Invalid Status in linux-raspi2-5.3 source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux-gke-5.3 source package in Bionic: Triaged Status in linux-hwe source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-raspi2-5.3 source package in Bionic: In Progress Status in linux source package in Focal: Invalid Status in linux-gke-5.3 source package in Focal: Invalid Status in linux-hwe source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-raspi2-5.3 source package in Focal: Invalid Bug description: [Impact] A memory leak may happen when an error happens when setting extended attributes. [Fix] The issue was introduced by an improper backport, so the fix is specific to Ubuntu, so a SAUCE patch. [Test case] Test setting attribute under a user namespace. [Regression potential] A double free bug might be introduced. Or setting extended attributes might fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924611] Re: setting extended attribute may cause memory leak
$ uname -a Linux bionic 5.3.0-1043-gke #46-Ubuntu SMP Fri Apr 16 09:14:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ ./leak.sh $ echo $? 0 $ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak Status in linux package in Ubuntu: Invalid Status in linux-gke-5.3 package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-raspi2-5.3 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-gke-5.3 source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Invalid Status in linux-oem-5.6 source package in Xenial: Invalid Status in linux-raspi2-5.3 source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux-gke-5.3 source package in Bionic: Triaged Status in linux-hwe source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-raspi2-5.3 source package in Bionic: In Progress Status in linux source package in Focal: Invalid Status in linux-gke-5.3 source package in Focal: Invalid Status in linux-hwe source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-raspi2-5.3 source package in Focal: Invalid Bug description: [Impact] A memory leak may happen when an error happens when setting extended attributes. [Fix] The issue was introduced by an improper backport, so the fix is specific to Ubuntu, so a SAUCE patch. [Test case] Test setting attribute under a user namespace. [Regression potential] A double free bug might be introduced. Or setting extended attributes might fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925026] 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 1925026 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/1925026 Title: Timer of 100us causes 64-bit app spin on Pi4 Status in linux package in Ubuntu: Incomplete Bug description: This problem happens with 64-bit 20.04 LTS or 20.10 on a Raspberry Pi 4 w/4GB (I am using the official Ubuntu Pi versions). It does NOT happen with either version when running on a standard x86 machine or VM. Also, it does NOT happen when using the 64-bit Raspberry Pi OS (https://downloads.raspberrypi.org/raspios_arm64/images/). So this issue is specific to the official 64-bit Ubuntu on Raspberry Pi version. When a 100us timer is started (via setitimer) the app will spin at 100%. With values slightly higher (150, 200, 1000) this does not happen. I've included the source for a small timer test program that I found reproduces the issue that broke my larger formal app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
linux 5.8.0-51 not available in groovy-proposed - developer options - (19/4/21 13:11 gmt) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925026] Re: Timer of 100us causes 64-bit app spin on Pi4
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925026 Title: Timer of 100us causes 64-bit app spin on Pi4 Status in linux package in Ubuntu: New Bug description: This problem happens with 64-bit 20.04 LTS or 20.10 on a Raspberry Pi 4 w/4GB (I am using the official Ubuntu Pi versions). It does NOT happen with either version when running on a standard x86 machine or VM. Also, it does NOT happen when using the 64-bit Raspberry Pi OS (https://downloads.raspberrypi.org/raspios_arm64/images/). So this issue is specific to the official 64-bit Ubuntu on Raspberry Pi version. When a 100us timer is started (via setitimer) the app will spin at 100%. With values slightly higher (150, 200, 1000) this does not happen. I've included the source for a small timer test program that I found reproduces the issue that broke my larger formal app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924611] Re: setting extended attribute may cause memory leak
For bionic:linux-hwe, the same patch was applied, so we can rely on the xenial verification for that. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak Status in linux package in Ubuntu: Invalid Status in linux-gke-5.3 package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-raspi2-5.3 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-gke-5.3 source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Invalid Status in linux-oem-5.6 source package in Xenial: Invalid Status in linux-raspi2-5.3 source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux-gke-5.3 source package in Bionic: Triaged Status in linux-hwe source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-raspi2-5.3 source package in Bionic: In Progress Status in linux source package in Focal: Invalid Status in linux-gke-5.3 source package in Focal: Invalid Status in linux-hwe source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-raspi2-5.3 source package in Focal: Invalid Bug description: [Impact] A memory leak may happen when an error happens when setting extended attributes. [Fix] The issue was introduced by an improper backport, so the fix is specific to Ubuntu, so a SAUCE patch. [Test case] Test setting attribute under a user namespace. [Regression potential] A double free bug might be introduced. Or setting extended attributes might fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925026] [NEW] Timer of 100us causes 64-bit app spin on Pi4
You have been subscribed to a public bug: This problem happens with 64-bit 20.04 LTS or 20.10 on a Raspberry Pi 4 w/4GB (I am using the official Ubuntu Pi versions). It does NOT happen with either version when running on a standard x86 machine or VM. Also, it does NOT happen when using the 64-bit Raspberry Pi OS (https://downloads.raspberrypi.org/raspios_arm64/images/). So this issue is specific to the official 64-bit Ubuntu on Raspberry Pi version. When a 100us timer is started (via setitimer) the app will spin at 100%. With values slightly higher (150, 200, 1000) this does not happen. I've included the source for a small timer test program that I found reproduces the issue that broke my larger formal app. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Timer of 100us causes 64-bit app spin on Pi4 https://bugs.launchpad.net/bugs/1925026 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 1924611] Re: setting extended attribute may cause memory leak
$ uname -a Linux bionic 5.3.0-74-generic #70-Ubuntu SMP Fri Apr 16 08:44:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ ./leak.sh $ echo $? 0 $ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak Status in linux package in Ubuntu: Invalid Status in linux-gke-5.3 package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-raspi2-5.3 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-gke-5.3 source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Invalid Status in linux-oem-5.6 source package in Xenial: Invalid Status in linux-raspi2-5.3 source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux-gke-5.3 source package in Bionic: Triaged Status in linux-hwe source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-raspi2-5.3 source package in Bionic: In Progress Status in linux source package in Focal: Invalid Status in linux-gke-5.3 source package in Focal: Invalid Status in linux-hwe source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-raspi2-5.3 source package in Focal: Invalid Bug description: [Impact] A memory leak may happen when an error happens when setting extended attributes. [Fix] The issue was introduced by an improper backport, so the fix is specific to Ubuntu, so a SAUCE patch. [Test case] Test setting attribute under a user namespace. [Regression potential] A double free bug might be introduced. Or setting extended attributes might fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924939] Re: Intel GPU lockups and graphical glitches in KDE
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 It seems, it started happening with kernel version 5.8.0-49. With 5.8.0-48 I can't reproduce this behavior, at least not as easily. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924939 Title: Intel GPU lockups and graphical glitches in KDE Status in linux package in Ubuntu: Confirmed Bug description: After a recent package update (at this point, I believe it was a kernel package upgrade) I began experiencing Intel GPU hangs and graphical glitches, such as blinking or corrupt textures in the panels and windows. In dmesg I can see messages like these: [ 24.825956] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:86d2bff9, in plasmashell [1625] [ 24.826005] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 24.927993] i915 :00:02.0: [drm] plasmashell[1625] context reset due to GPU hang ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-lowlatency 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-lowlatency 5.8.18 Uname: Linux 5.8.0-50-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 1319 F pulseaudio /dev/snd/controlC1: lastique 1319 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 19 02:18:39 2021 HibernationDevice: # Prevents "gave up waiting for suspend/resume device" timeout on boot RESUME=none InstallationDate: Installed on 2013-10-11 (2746 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. N550JV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-lowlatency root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-lowlatency N/A linux-backports-modules-5.8.0-50-lowlatency N/A linux-firmware 1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-21 (148 days ago) WifiSyslog: dmi.bios.date: 11/19/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV 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.:bvrN550JV.208:bd11/19/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924611] Re: setting extended attribute may cause memory leak
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1924611 Title: setting extended attribute may cause memory leak Status in linux package in Ubuntu: Invalid Status in linux-gke-5.3 package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-raspi2-5.3 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-gke-5.3 source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Invalid Status in linux-oem-5.6 source package in Xenial: Invalid Status in linux-raspi2-5.3 source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux-gke-5.3 source package in Bionic: Triaged Status in linux-hwe source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-raspi2-5.3 source package in Bionic: In Progress Status in linux source package in Focal: Invalid Status in linux-gke-5.3 source package in Focal: Invalid Status in linux-hwe source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-raspi2-5.3 source package in Focal: Invalid Bug description: [Impact] A memory leak may happen when an error happens when setting extended attributes. [Fix] The issue was introduced by an improper backport, so the fix is specific to Ubuntu, so a SAUCE patch. [Test case] Test setting attribute under a user namespace. [Regression potential] A double free bug might be introduced. Or setting extended attributes might fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
