[Kernel-packages] [Bug 1910928] [NEW] Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL
You have been subscribed to a public bug: After I have installed the Ubuntu - I have noticed, that Bluetooth won't go turn on after Suspend. The only way to get it working - reboot the system. WiFi Adapter - AX201 I have tried the latest kernel (5.11.rc2) - no luck. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL https://bugs.launchpad.net/bugs/1910928 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1910541] Re: [SRU][G/H/U/OEM-5.10] re-enable s0ix of e1000e
** Summary changed: - [SRU][U/OEM-5.10] re-enable s0ix of e1000e on 5.10 kernel + [SRU][G/H/U/OEM-5.10] re-enable s0ix of e1000e ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Groovy) Importance: Undecided Status: New ** No longer affects: linux-oem-5.10 (Ubuntu Groovy) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) ** No longer affects: linux (Ubuntu Focal) ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu) Status: Invalid => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Description changed: [Impact] Due to s2idle failure on e1000e driver in ME enabled system, it disabled s0ix. Finally latest kernel accepted the bump up timeout value to fixed the issue. s0ix can be supported again. [Fix] Rebase the sauce patch to upstream patch, then support s0ix of e1000e. [Test Case] s2idle can work normally on ME enabled platform. [Where problems could occur] s2idle may fail to suspend on 2nd times. + + These patches are trying to revert the disabled s0ix patch in 5.8+, + no need for 5.7- kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910541 Title: [SRU][G/H/U/OEM-5.10] re-enable s0ix of e1000e Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Due to s2idle failure on e1000e driver in ME enabled system, it disabled s0ix. Finally latest kernel accepted the bump up timeout value to fixed the issue. s0ix can be supported again. [Fix] Rebase the sauce patch to upstream patch, then support s0ix of e1000e. [Test Case] s2idle can work normally on ME enabled platform. [Where problems could occur] s2idle may fail to suspend on 2nd times. These patches are trying to revert the disabled s0ix patch in 5.8+, no need for 5.7- kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
** Tags added: originate-from-1892304
--
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/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
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-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
This new fix should help: https://gitlab.gnome.org/GNOME/mutter/-/commit/f0a9ec0519 It's basically what I was hoping for in comment #26, but an additional fix was required. If that does solve it then potentially a workaround is to just create a custom wallpaper image that's the same resolution as your monitor. Then you probably wouldn't need this week's fix. ** Changed in: mutter (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
See kernel log with the 5.10.0-4008-oem kernel. Didn't work with either USB-C port. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+attachment/5451633/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909062] Re: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1909062 [Impact] For users with QLogic QL41xxx series NICs, such as the FastLinQ QL41000 Series 10/25/40/50GbE Controller, when they upgrade from the 4.15 kernel to the 5.4 kernel, Kubernetes Internal DNS requests will fail, due to these packets getting corrupted. Kubernetes uses IPIP tunnelled packets for internal DNS resolution, and this particular packet type is not supported for hardware tx checksum offload, and the packets end up corrupted when the qede driver attempts to checksum them. This only affects internal Kubernetes DNS, as regular DNS lookups to regular external domains will succeed, due to them not using IPIP packet types. [Fix] Marvell has developed a fix for the qede driver, which checks the packet type, and if it is IPPROTO_IPIP, then csum offloads are disabled for socket buffers of type IPIP. commit 5d5647dad259bb416fd5d3d87012760386d97530 Author: Manish Chopra Date: Mon Dec 21 06:55:30 2020 -0800 Subject: qede: fix offload for IPIP tunnel packets - Link: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=5d5647dad259bb416fd5d3d87012760386d97530 + Link: https://github.com/torvalds/linux/commit/5d5647dad259bb416fd5d3d87012760386d97530 - This commit is currently in the netdev tree, awaiting merge to mainline. - The commit is queued for upstream stable. + This commit landed in mainline in 5.11-rc3. The commit is queued for + upstream stable. [Testcase] The system must have a QLogic QL41xxx series NIC fitted, and needs to be a part of a Kubernetes cluster. Firstly, get a list of all devices in the system: $ sudo ifconfig Next, set all devices down with: $ sudo ifconfig down Next, bring up the QLogic QL41xxx device: $ sudo ifconfig up Then, attempt to lookup an internal Kubernetes domain: $ nslookup Without the patch, the connection will time out: ;; connection timed out; no servers could be reached If we look at packet traces with tcpdump, we see it leaves the source, but never arrives at the destination. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf297772-test If you install it, then Kubernetes internal DNS lookups will succeed. [Where problems could occur] If a regression were to occur, then users of the qede driver would be affected. This is limited to those with QLogic QL41xxx series NICs. The patch explicitly checks for IPIP type packets, so only those particular packets would be affected. Since IPIP type packets are uncommon, it would not cause a total outage on regression, since most packets are not IPIP tunnelled. It could potentially cause problems for users who frequently handle VPN or Kubernetes internal DNS traffic. A workaround would be to use ethtool to disable tx csum offload for all packet types, or to revert to an older kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909062 Title: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1909062 [Impact] For users with QLogic QL41xxx series NICs, such as the FastLinQ QL41000 Series 10/25/40/50GbE Controller, when they upgrade from the 4.15 kernel to the 5.4 kernel, Kubernetes Internal DNS requests will fail, due to these packets getting corrupted. Kubernetes uses IPIP tunnelled packets for internal DNS resolution, and this particular packet type is not supported for hardware tx checksum offload, and the packets end up corrupted when the qede driver attempts to checksum them. This only affects internal Kubernetes DNS, as regular DNS lookups to regular external domains will succeed, due to them not using IPIP packet types. [Fix] Marvell has developed a fix for the qede driver, which checks the packet type, and if it is IPPROTO_IPIP, then csum offloads are disabled for socket buffers of type IPIP. commit 5d5647dad259bb416fd5d3d87012760386d97530 Author: Manish Chopra Date: Mon Dec 21 06:55:30 2020 -0800 Subject: qede: fix offload for IPIP tunnel packets Link: https://github.com/torvalds/linux/commit/5d5647dad259bb416fd5d3d87012760386d97530 This commit landed in mainline in 5.11-rc3. The commit is queued for upstream stable. [Testcase] The system must have a QLogic QL41xxx series NIC fitted, and needs to be a part of a Kubernetes cluster. Firstly, get a list of all devices in the system: $ sudo ifconfig Next, set all devices down with: $ sudo
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
Is this a regresison? Did it start to happen after upgrade from 5.4 to 5.8? And is it possible to attach `lspci -vv` after the issue happen? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-34-generic N/A
[Kernel-packages] [Bug 1903794] Re: Wifi stopped working: Init ucode -5 [Intel Wireless 9560]
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903794 Title: Wifi stopped working: Init ucode -5 [Intel Wireless 9560] Status in linux package in Ubuntu: Expired Bug description: I once cold booted my laptop and the wifi stopped working completely. This is the error I get from dmesg when I filter for wireless driver info only. Relevant specs: --- Operating System: Distributor ID:Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal PC make: Dell Inspiron 7586 2-in-1 Linux Firmware: linux-firmware/focal-updates,focal-updates,now 1.187.4 all [installed] Linux Headers: 5.4.0-42-generic $dmesg | grep iwlwifi [8.050151] iwlwifi :00:14.3: enabling device ( -> 0002) [8.073632] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [8.073635] iwlwifi :00:14.3: Found debug configuration: 0 [8.073898] iwlwifi :00:14.3: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm [8.133208] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 9460, REV=0x318 [8.156288] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [8.159789] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [8.164794] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [8.164799] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [8.164816] iwlwifi :00:14.3: Fseq Registers: [8.164822] iwlwifi :00:14.3: 0x98402404 | FSEQ_ERROR_CODE [8.164825] iwlwifi :00:14.3: 0x34504D88 | FSEQ_TOP_INIT_VERSION [8.164828] iwlwifi :00:14.3: 0x65A63677 | FSEQ_CNVIO_INIT_VERSION [8.164831] iwlwifi :00:14.3: 0x015660A5 | FSEQ_OTP_VERSION [8.164834] iwlwifi :00:14.3: 0x39BEFAFE | FSEQ_TOP_CONTENT_VERSION [8.164837] iwlwifi :00:14.3: 0xC1B9DFF0 | FSEQ_ALIVE_TOKEN [8.164841] iwlwifi :00:14.3: 0x00409810 | FSEQ_CNVI_ID [8.164844] iwlwifi :00:14.3: 0xFFEE77FF | FSEQ_CNVR_ID [8.164847] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [8.164882] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP [8.164951] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [8.165020] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [8.165247] iwlwifi :00:14.3: SecBoot CPU1 Status: 0xa5a5a5a2, CPU2 Status: 0xa5a5a5a2 [8.165251] iwlwifi :00:14.3: Failed to start INIT ucode: -5 [8.165253] iwlwifi :00:14.3: Collecting data: trigger 16 fired. [8.411263] iwlwifi :00:14.3: Firmware not running - cannot dump error [8.424358] iwlwifi :00:14.3: Failed to run INIT ucode: -5 **My wireless network adapter is recognized by the OS.** name@name:~$ lspci 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) name@name:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no name@name:~$ sudo lshw -C network [sudo] password for name: *-network description: Network controller product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 version: 30 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list configuration: driver=iwlwifi latency=0 resources: irq:16 memory:a121c000-a121 Resolutions attempted: - Downloading official iwlwifi drivers from Intel, Dell and my /lib/firmware folder (-34.ucode from Intel and Dell and also the -33, -34, -38, -41, -43 and -46.ucode from /lib/firmware) - Downloading the backport iwlwifi drivers from PPA Research: My suspicion is that there might be a conflict with the Bluetooth module (hindering the correct firmware from being loaded) as there was a time the wifi briefly worked then stopped when I turned off Bluetooth. However, now I can't turn off Bluetooth and wifi. As you can see, the radio kill button has just the Bluetooth option which doesn't even work. Please help me? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gacoka 1753 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 IwConfig: lono wireless extensions. usb0 no wireless extensions. MachineType: Dell Inc. Inspiron 7586 Package: linux (not installed) ProcFB: 0 i915drmfb
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
Is there a signed version of 5.10 oem available anywhere? I see 5.10.0-1008-oem available in Ubuntu sources, but the version you asked for testing is 5.10.0-4008-oem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910618] Re: bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34
Looking at the source code for the broadcom-sta package, which is
working, I am wondering if
lines 3359-3381 from wl_linux.c in the bcmwl package
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 10, 0)
static const struct file_operations wl_fops = {
.owner = THIS_MODULE,
.read = wl_proc_read,
.write = wl_proc_write,
};
#endif
should be updated to something similar to what is in the broadcom-sta
package in order to convert to using proc_ops that is found in the new
5.8.0-34/36 headers.
lines 3359-3381 from wl_linux.c in the broadcom-sta package
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 10, 0)
#if LINUX_VERSION_CODE >= KERNEL_VERSION(5, 6, 0)
static const struct proc_ops wl_fops = {
.proc_read = wl_proc_read,
.proc_write = wl_proc_write,
};
#else
static const struct file_operations wl_fops = {
.owner = THIS_MODULE,
.read = wl_proc_read,
.write = wl_proc_write,
};
#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(5, 6, 0) */
#endif /* LINUX_VERSION_CODE >= KERNEL_VERSION(3, 10, 0) */
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1910618
Title:
bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34
Status in bcmwl package in Ubuntu:
New
Bug description:
Ubuntu 20.04.1 LTS
bcmwl-kernel-source_6.30.223.271
I believe the important part of the
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log is below.
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of ‘proc_create_data’ from incompatible pointe
r type [-Werror=incompatible-pointer-types]
3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, _fops,
wl)) == NULL) {
| ^~~~
| |
| const struct
file_operations *
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:38:
./include/linux/proc_fs.h:102:31: note: expected ‘const struct proc_ops *’
but argument is of type ‘const struct file_operations *’
102 | extern struct proc_dir_entry *proc_create_data(const char *, umode_t,
| ^~~~
It looks like
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c uses the
file_operations structure.
lines 3359-3381 from wl_linux.c
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 10, 0)
static const struct file_operations wl_fops = {
.owner = THIS_MODULE,
.read = wl_proc_read,
.write = wl_proc_write,
};
#endif
static int
wl_reg_proc_entry(wl_info_t *wl)
{
char tmp[32];
sprintf(tmp, "%s%d", HYBRID_PROC, wl->pub->unit);
#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 10, 0)
if ((wl->proc_entry = create_proc_entry(tmp, 0644, NULL)) == NULL) {
WL_ERROR(("%s: create_proc_entry %s failed\n", __FUNCTION__,
tmp));
#else
if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, _fops, wl))
== NULL) {
WL_ERROR(("%s: proc_create_data %s failed\n", __FUNCTION__,
tmp));
#endif
ASSERT(0);
return -1;
}
However, it looks like proc_fs.h uses a different structure (proc_ops).
/usr/src/linux-headers-5.8.0-34-generic/include/linux/proc_fs.h
/usr/src/linux-hwe-5.8-headers-5.8.0-34/include/linux/proc_fs.h
kernel 5.8.0-34
proc_fs.h
lines 29-43
struct proc_ops {
unsigned int proc_flags;
int (*proc_open)(struct inode *, struct file *);
ssize_t (*proc_read)(struct file *, char __user *, size_t, loff_t *);
ssize_t (*proc_write)(struct file *, const char __user *, size_t,
loff_t *);
loff_t (*proc_lseek)(struct file *, loff_t, int);
int (*proc_release)(struct inode *, struct file *);
__poll_t (*proc_poll)(struct file *, struct poll_table_struct *);
long(*proc_ioctl)(struct file *, unsigned int, unsigned long);
#ifdef CONFIG_COMPAT
long(*proc_compat_ioctl)(struct file *, unsigned int, unsigned
long);
#endif
int (*proc_mmap)(struct file *, struct vm_area_struct *);
unsigned long (*proc_get_unmapped_area)(struct file *, unsigned long,
unsigned long, unsigned long, unsigned long);
} __randomize_layout;
and lines 102-107
extern struct proc_dir_entry *proc_create_data(const char *, umode_t,
struct proc_dir_entry *,
const struct proc_ops *,
void *);
struct proc_dir_entry *proc_create(const char *name, umode_t mode,
[Kernel-packages] [Bug 1905287] Re: Phantom mouse wheel events without user input
** Changed in: libinput (Ubuntu) Status: New => Incomplete ** Changed in: mutter (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/1905287 Title: Phantom mouse wheel events without user input Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: This doesn't occur with Firefox. But it occurs with Chrome AND gnome- terminal. What happens is that if I have more than one tab in focus, it moves to the last tabs by itself. Here is a screen capture of what happens. I am running ubuntu 18.04.5 LTS, i have never had this issue before. Issue started happening since yesterday. This morning I applied my updates hoping that this will fix it, but even then nothing happened. I have known this to happen in another older laptop running an older version of ubuntu as well. journalctl -f gives me ths following: ``` Nov 23 15:28:36 xxxmymachinenamexxx gnome-shell[4051]: pushModal: invocation of begin_modal failed ``` Note that this error entry from the journalctl does not always appear when the tabs cycle through like in the video, might be unrelated. My graphics card is: lspci |grep VGA ``` 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) ``` I thought initially it might be some key that is being pressed, so i ran screenkey when this happens, there was no key appearing, so it does not seem that this is a key being pressed. I tail -f /var/log/syslog and /var/log/Xorg.0.log when i click on the tabs and it does this weirdness, nothing happens. So i don't have much information to give on this issue. Please get in touch with me if you want any information. I cannot push all my logs since it is a professional laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1905287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909496] Re: [i915] Blinking unlock screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (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/1909496 Title: [i915] Blinking unlock screen Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hello, I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The issue still persists even after re-installing Ubuntu 20.04.1 LTS. Due to inactivity the system goes to the Suspend mode. On restoring from the suspend mode the login screen appears but it starts to blink continuously making it impossible to use the system. The only option is to force restart the system. Please let me know if this is an already known issue/bug and if there is a solution available for the same. Thank You ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 28 19:21:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2020-12-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] Re: Screen Keeps Blinking/Flickering after waking up from lock
*** This bug is a duplicate of bug 1909496 *** https://bugs.launchpad.net/bugs/1909496 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1909496, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1909496 [i915] Blinking unlock screen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908366] Re: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin
** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1908366 Title: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] It shows the firmware is missing, and runtime power management has been disabled. [ 1.884400] i915 :00:02.0: vgaarb: deactivate vga console [ 1.887078] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.887161] i915 :00:02.0: Direct firmware load for i915/tgl_dmc_ver2_08.bin failed with error -2 [ 1.887164] i915 :00:02.0: [drm] Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin. Disabling runtime power management. [ 1.887165] i915 :00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 [Fix] cherry picked from linux-firmware bdf8d7a8 i915: Add DMC firmware 2.08 for TGL BTW, groovy has this commit already. [Test] Verified on Dell's machine [Where problems could occur] It's a new firmware for new GPU, not possible to introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910936] 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 1910936 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/1910936 Title: nic card error Status in linux package in Ubuntu: Incomplete Bug description: internet stops working after 10 min. must do a hard restart to enable card again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910936] Re: nic card error
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1910936 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** 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/1910936 Title: nic card error Status in linux package in Ubuntu: Incomplete Bug description: internet stops working after 10 min. must do a hard restart to enable card again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910936] [NEW] nic card error
You have been subscribed to a public bug: internet stops working after 10 min. must do a hard restart to enable card again ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- nic card error https://bugs.launchpad.net/bugs/1910936 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 1905591] Re: no brightness control in {455, 460} after update from 450
I tried the fix for a different problem in this link randomly and it
worked for me.
https://forums.developer.nvidia.com/t/problem-driver-nvidia-455-45-01
-on-linux-mint-20-4-6-7/165402
I am adding steps here:
1. Add the following lines to the file "/etc/initramfs-tools/modules"
nvidia
nvidia-drm
nvidia-modeset
2. Run "sudo update-initramfs -u" in the terminal
3. Reboot
--
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/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Confirmed
Bug description:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
GTX 1050 Ti Mobile]:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
*Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910875] Re: Broadcom wireless driver failed to install with code 10 on focal 20.04
@jsarka, Thanks for those clear instructions! As it turns out I already
figured out (I hope) how to revert to kernel 5.4. That has brought back
my wifi. If other things go bonkers, I'll get 5.8 back and follow your
steps.
The bump to 5.8 broke several things on my system, which is why I first
tried downgrading kernels. I deliberately picked an LTS, so I'm very
surprised that I got a kernel bump that skips three point releases
without any warning.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1910875
Title:
Broadcom wireless driver failed to install with code 10 on focal
20.04
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
First, I suspect this may be the same bug as Bug #1905211 "package
bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in
kernel v5.9" because I got the same error "installed bcmwl-kernel-
source package post-installation script subprocess returned error exit
status 10". However, I wanted to make a separate report because I am
still on kernel v5.8. Please merge these threads if it seems like
they're the same bug.
Anyway, my problem is this:
The last time I installed a tranche of system updates, I got a "System
software problem detected" dialog and submitted the crash report. The
next time I booted up my computer, the Broadcom wifi device was not
recognized. The wifi had worked fine up until that point.
I tried to manually uninstall and reinstall the driver using dpkg with
the bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) package
downloaded from packages.ubuntu.com (the machine in question does not
have a wired ethernet connection). dpkg produced the following
output:
Preparing to unpack bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb
...
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) over
(6.30.223.271+bdcom-0ubuntu5) ...
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.8.0-36-generic
Building for architecture x86_64
Building initial module for 5.8.0-36-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/bcmwl-kernel-source.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more
information.
dpkg: error processing package bcmwl-kernel-source (--install):
installed bcmwl-kernel-source package post-installation script subprocess
returned error exit status 10
Errors were encountered while processing:
bcmwl-kernel-source
The make log from my manually installation attempt read:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-36-generic
(x86_64)
Sat 09 Jan 2021 01:14:26 PM PST
make: Entering directory '/usr/src/linux-headers-5.8.0-36-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 |
[Kernel-packages] [Bug 1907557] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1907445 *** https://bugs.launchpad.net/bugs/1907445 armishra your post helped me with this problem thank you! My question is will this be fixed in future updates? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1907557 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:16:44 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1907557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905182] Re: nvidia-dkms-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build
Solved updating to 390.141 too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1905182 Title: nvidia-dkms-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Ran into this while installing linux-lowlatency-hwe-20.04-edge on a Dell Latitude E6520 with NVIDIA NVS 4200M graphics. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-29-lowlatency Date: Sun Nov 22 12:05:26 2020 DuplicateSignature: dkms:nvidia-dkms-390:390.138-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.138/build/common/inc/nv-linux.h:534:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-01-05 (322 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageVersion: 390.138-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: Upgraded to focal on 2020-05-13 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1905182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
I had the same problem and submitted it as Bug #1910875. I didn't see
this bug at first because I got a slightly different error message
("post-installation script subprocess returned error exit status 10").
But it's definitely the same bug and installing the 6.30.223.271+bdcom-
0ubuntu7 version of bcmwl-kernel-source worked for me. So in one sense
this bug has already been patched, but I would say that the real bug is
that the patch didn't get included in the focal repository.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1910555
Title:
Driver build error on kernel 5.8, but works on 5.4
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on
WiFi doesn't work anymore. After a try rebuild (reconfigure) the result is:
---
# dpkg-reconfigure bcmwl-kernel-source
Removing all DKMS Modules
Done.
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.4.0-59-generic 5.8.0-34-generic
Building for architecture x86_64
Building initial module for 5.4.0-59-generic
Done.
wl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.4.0-59-generic/updates/dkms/
depmod
DKMS: install completed.
Building initial module for 5.8.0-34-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/bcmwl-kernel-source.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more
information.
---
As could be seen, the build for 5.4 completes successfully (and works on same
kernel), but for 5.8 fails. Seems something is going wrong with missing
function declaration - function "ioremap_nocache", as could be seen in attached
make.log.
I'm guessing, driver code may need be updated according to the new kernel
headers.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
Uname: Linux 5.4.0-59-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Jan 7 17:13:05 2021
InstallationDate: Installed on 2020-06-22 (198 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910875] Re: Broadcom wireless driver failed to install with code 10 on focal 20.04
Yes, I agree this does look like a duplicate of Bug #1910555. I'm not sure why I didn't see that one when I was looking for bugs that corresponded to my problem. Anyway, this solution worked for me: 1. Manually download the bcmwl-kernel-source package from this page: https://packages.ubuntu.com/groovy/bcmwl-kernel-source Make sure that you get the "6.30.223.271+bdcom-0ubuntu7" version from the "groovy" repository, not the older version from the "focal" repository. (You might also need to install or reinstall the "dkms" package, which you will see a link to under "related packages".) (I needed to download the package on a different computer and transfer on a flash drive it to the laptop where the wifi wasn't working because that laptop doesn't have an ethernet port.) 2. Open a terminal, go to the directory where the package file is located and run dpkg with this command: sudo dpkg -i bcmwl-kernel- source_6.30.223.271+bdcom-0ubuntu7_amd64.deb 3. Enter your administrator password. The broadcom driver kernel module should install automatically. If you get an error saying that package you are trying to install depends upon some other package that isn't available, download that package from packages.ubuntu.com and install it using the command: sudo dpkg -i [package file name], then try step 2 again. For me the installation worked fine, and the wifi came back on instantly and even automatically reconnected to my home network. I didn't even need to reboot! So this is definitely an effective workaround, but this bug won't really be solved until Canonical gets this patch into the focal repositories. (And even then, people will still have to manually reinstall their wifi driver if they don't have wired internet access.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910875 Title: Broadcom wireless driver failed to install with code 10 on focal 20.04 Status in bcmwl package in Ubuntu: Confirmed Bug description: First, I suspect this may be the same bug as Bug #1905211 "package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in kernel v5.9" because I got the same error "installed bcmwl-kernel- source package post-installation script subprocess returned error exit status 10". However, I wanted to make a separate report because I am still on kernel v5.8. Please merge these threads if it seems like they're the same bug. Anyway, my problem is this: The last time I installed a tranche of system updates, I got a "System software problem detected" dialog and submitted the crash report. The next time I booted up my computer, the Broadcom wifi device was not recognized. The wifi had worked fine up until that point. I tried to manually uninstall and reinstall the driver using dpkg with the bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) package downloaded from packages.ubuntu.com (the machine in question does not have a wired ethernet connection). dpkg produced the following output: Preparing to unpack bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb ... Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) over (6.30.223.271+bdcom-0ubuntu5) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-36-generic Building for architecture x86_64 Building initial module for 5.8.0-36-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--install): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: bcmwl-kernel-source The make log from my manually installation attempt read: DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-36-generic (x86_64) Sat 09 Jan 2021 01:14:26 PM PST make: Entering directory '/usr/src/linux-headers-5.8.0-36-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In function ‘osl_reg_map’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you
[Kernel-packages] [Bug 998310] Re: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session
See https://forum.xfce.org/viewtopic.php?id=13926 and upstream issue https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/168 There is a partial fix which apparently fixes the desktop shortcuts being locked, but not the multiple calls to xmodmap: https://gitlab.xfce.org/atomsymbol/libxfce4ui/-/commit/85d8d390f9f2265613da4291992523937a7a2519 XFCE desktop shortcuts are unusable for about 30-40 seconds after switching from tty to Xorg if there exists a .Xmodmap file in $HOME. Without a .Xmodmap file, the delay is about 10 seconds. Similar behavior gets triggered when a keyboard is reconnected to an USB port. With this patch, desktop shortcuts are usable immediately (likely in less than 0.25 seconds after switching from tty to Xorg). An issue not fixed by this patch is that /usr/bin/xmodmap can be executed about 30 times after switching to Xorg. However, on the tested machine with a relatively small .Xmodmap this does not pose a performance issue which would be noticeable by the user. ** Bug watch added: gitlab.xfce.org/xfce/xfce4-settings/-/issues #168 https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/168 ** Also affects: linux via https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/168 Importance: Unknown Status: Unknown ** Project changed: linux => xfce4-settings ** Package changed: linux (Ubuntu) => xfce4-settings (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/998310 Title: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session Status in Xfce4 Settings: Unknown Status in xfce4-settings package in Ubuntu: Incomplete Bug description: Each time when I resume my laptop, my computer nearly freezes for about 5 minutes and Xorg is using 90-100% cpu. This issue disappears and then everything is back to normal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Fri May 11 22:57:03 2012 EcryptfsInUse: Yes InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) ProcEnviron: LANGUAGE=ca_ES TERM=xterm LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2012-03-25 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/998310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 998310] Re: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session
I noticed this on Debian (buster). It appears to be caused by the
keyboard being detected multiple times, resulting in xfsettingsd running
xmodmap multiple times. To monitor, run:
XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon
After suspend/resume (or just unplug/plug the USB keyboard), xfsettingsd
launches xmodmap multiple times:
xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap"
xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings.
Warning: Only changing the first 3 of 10 buttons.
xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap"
xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings.
Warning: Only changing the first 3 of 10 buttons.
xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap"
Warning: Only changing the first 3 of 10 buttons.
xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings.
xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap"
xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings.
xfce4-settings(keyboard-layout): spawning "xmodmap /home/user/.Xmodmap"
xfce4-settings(keyboard-layout): New keyboard detected; restoring XKB settings.
As a test, doing:
for x in {1..10}; do bash -c 'xmodmap ~/.Xmodmap &'; done
Has similar results of high CPU in xorg and xmodmap.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/998310
Title:
.Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%)
after resume or when coming back from tty to X session
Status in Xfce4 Settings:
Unknown
Status in xfce4-settings package in Ubuntu:
Incomplete
Bug description:
Each time when I resume my laptop, my computer nearly freezes for
about 5 minutes and Xorg is using 90-100% cpu. This issue disappears
and then everything is back to normal.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Fri May 11 22:57:03 2012
EcryptfsInUse: Yes
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
ProcEnviron:
LANGUAGE=ca_ES
TERM=xterm
LANG=ca_ES.UTF-8
SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: Upgraded to precise on 2012-03-25 (47 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/998310/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905591] Re: no brightness control in {455, 460} after update from 450
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Status: Triaged => In Progress
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Status: In Progress => Confirmed
--
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/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Confirmed
Bug description:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
GTX 1050 Ti Mobile]:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
*Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873641] Re: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write.
I'm also experiencing several crash. I'm using an Asus PRIME B450M-A II motherboard. $ systemctl status --user pulseaudio.service pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-01-10 20:55:22 CET; 25min ago TriggeredBy: ● pulseaudio.socket Main PID: 1474 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─1474 /usr/bin/pulseaudio --daemonize=no --log-target=journal gen 10 20:55:22 XXX systemd[1468]: Starting Sound Service... gen 10 20:55:22 XXX systemd[1468]: Started Sound Service. gen 10 20:55:26 XXX pulseaudio[1474]: ALSA woke us up to write new data to the device, but there was actually nothing to write. gen 10 20:55:26 XXX pulseaudio[1474]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. gen 10 20:55:26 XXX pulseaudio[1474]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. gen 10 20:55:47 XXX pulseaudio[1474]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. $ uname -a Linux XXX 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873641 Title: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write. Status in linux package in Ubuntu: Confirmed Bug description: Apr 19 03:12:37 shh pulseaudio[2107]: ALSA woke us up to write new data to the device, but there was actually nothing to write. Apr 19 03:12:37 shh pulseaudio[2107]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Apr 19 03:12:37 shh pulseaudio[2107]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. I'm running Ubuntu 20.04 beta, and have just gotten past several crash or abort issues in pulseaudio on this Gigabyte AX370-Gaming5 motherboard. With tonight's update to: Package: pulseaudio Architecture: amd64 Version: 1:13.99.1-1ubuntu3 and the running kernel: Linux shh.toad.com 5.4.0-24-generic #28-Ubuntu SMP Thu Apr 9 22:16:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I got a somg;e report like this in syslog (so far). Since the developers asked me to report it, here's the bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 03:24:07 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: enp6s0no wireless extensions. enp5s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=35b84e12-683c-43ea-9b3f-64fae90e1984 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte
[Kernel-packages] [Bug 1910927] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451528/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451526/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451530/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451529/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451527/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451532/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451531/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451525/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451524/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451523/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451521/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451522/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451520/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] Re: Suspend stopped working with kernel 5.4 (ubuntu 20.04)
apport information ** Tags added: apport-collected ** Description changed: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! - I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, - suspend is broken on my older device with Core2Duo. + I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: xubuntu4020 F pulseaudio + CasperMD5CheckResult: pass + CasperVersion: 1.445 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 20.04 + LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaudrmfb + ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity + ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-26-generic N/A + linux-backports-modules-5.4.0-26-generic N/A + linux-firmware1.187 + Tags: focal + Uname: Linux 5.4.0-26-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/01/2010 + dmi.bios.vendor: Phoenix Technologies Ltd. + dmi.bios.version: 10LI.M008.20100401.KSJ + dmi.board.name: R510/P510 + dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: + dmi.product.name: R510/P510 + dmi.product.version: Not Applicable + dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451516/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO.,
[Kernel-packages] [Bug 1910927] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451519/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451518/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1910927/+attachment/5451517/+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/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
** Changed in: linux (Ubuntu) Status: Expired => 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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
If there is a need for additional debug info, this bug is currently affecting me and I am free to provide any logs neccessary. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] 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 1910927 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Incomplete Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] [NEW] Suspend stopped working with kernel 5.4 (ubuntu 20.04)
Public bug reported: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel suspend ** Tags added: kernel suspend -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910927 Title: Suspend stopped working with kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: New Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906655] Re: Ethernet interface broken (Flags mismatch irq) after upgrading to kernel 5.8.0-31
This is still happening to me on up to date 5.8 kernel. I'd consider it very serious bug as for non-technical user the internet just stops working and updates cannot fix it. Workaround is to choose 5.4 kernel from grub menu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906655 Title: Ethernet interface broken (Flags mismatch irq) after upgrading to kernel 5.8.0-31 Status in linux package in Ubuntu: Confirmed Bug description: Realtek ethernet network interface is broken when booting with kernel 5.8.0-31. It works fine when simply booting with previous kernel 5.8.0-29 in GRUB. No other packages were updated. The only related line in /var/log/kern.log: Dec 3 14:01:21 hd kernel: [ 17.824691] genirq: Flags mismatch irq 16. 00010080 (enp4s0) vs. 2080 (uhci_hcd:usb3) `lspci -v` for this network interface below (`lspci -vv` attached): 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet Flags: bus master, fast devsel, latency 0, IRQ 16 I/O ports at d000 [size=256] Memory at f800 (64-bit, non-prefetchable) [size=4K] Expansion ROM at f700 [virtual] [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 00-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting Kernel driver in use: r8169 Kernel modules: r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910920] 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 1910920 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910920 Title: no soundcard present with linux-image-5.8.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: With linux-image-5.8.0-34-generic, all on-board soundcards work flawlessly. After update of kernel to linux-image-5.8.0-37-generic durign this week no soundcards are detected. I am happy to provide more information. But I will not sent automatic apport reports because it includes private local data. !!DMI Information !!--- Manufacturer: LENOVO Product Name: 20BUS23M00 Product Version: ThinkPad T450 Firmware Version: JBET54WW (1.19 ) Board Vendor: LENOVO Board Name:20BUS23M00 !!Kernel Information !!-- Kernel release:5.8.0-34-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.8.0-34-generic Library version:1.2.3.2 Utilities version: 1.2.3 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xe123 irq 51 1 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe1234000 irq 52 !!PCI Soundcards installed in the system !!-- 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller [17aa:5034] 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller [17aa:5034] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910923] 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 1910923 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/1910923 Title: Purging of old kernel does not work with boot on other partition Status in linux package in Ubuntu: Incomplete Bug description: The following command is suggested to remove old Kernels: sudo apt-get autoremove --purge e.g. on this Q https://askubuntu.com/questions/1253347/how-to-easily-remove-old-kernels-in-ubuntu-20-04-lts This seems not to work well with set-up where the boot files sit on a different partition with limited size. Example: LVM configuration with boot on a different partition thank root: Filesystem Size Used Avail Use% Mounted on /dev/mapper/linux-root100G 20G 80G 60% / /dev/sda3485M287M 174M 63% /boot /dev/sda1 96M 39M 58M 40% /boot/efi Expected process: sudo apt-get autoremove --purge should remove all kernels on all partitions Work-around solution: uname -r $CURRENT-KERNEL$ dpkg --list 'linux-image-*' sudo apt-get purge $PREVIOUS-KERNEL$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910921] 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 1910921 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/1910921 Title: Keyboard short conflict since upgrade to 20.10 Status in linux package in Ubuntu: Incomplete Bug description: Starting Dolphin since Upgrade to Kubuntu 20.10 shows a message notifying about keyboard short cut conflict. the orginal keymapping was not changed. The system was originally installed with 20.04. I am happy to provide more info such as diff on keyboard mapping etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910923] [NEW] Purging of old kernel does not work with boot on other partition
Public bug reported: The following command is suggested to remove old Kernels: sudo apt-get autoremove --purge e.g. on this Q https://askubuntu.com/questions/1253347/how-to-easily-remove-old-kernels-in-ubuntu-20-04-lts This seems not to work well with set-up where the boot files sit on a different partition with limited size. Example: LVM configuration with boot on a different partition thank root: Filesystem Size Used Avail Use% Mounted on /dev/mapper/linux-root100G 20G 80G 60% / /dev/sda3485M287M 174M 63% /boot /dev/sda1 96M 39M 58M 40% /boot/efi Expected process: sudo apt-get autoremove --purge should remove all kernels on all partitions Work-around solution: uname -r $CURRENT-KERNEL$ dpkg --list 'linux-image-*' sudo apt-get purge $PREVIOUS-KERNEL$ ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1910923 Title: Purging of old kernel does not work with boot on other partition Status in linux package in Ubuntu: Incomplete Bug description: The following command is suggested to remove old Kernels: sudo apt-get autoremove --purge e.g. on this Q https://askubuntu.com/questions/1253347/how-to-easily-remove-old-kernels-in-ubuntu-20-04-lts This seems not to work well with set-up where the boot files sit on a different partition with limited size. Example: LVM configuration with boot on a different partition thank root: Filesystem Size Used Avail Use% Mounted on /dev/mapper/linux-root100G 20G 80G 60% / /dev/sda3485M287M 174M 63% /boot /dev/sda1 96M 39M 58M 40% /boot/efi Expected process: sudo apt-get autoremove --purge should remove all kernels on all partitions Work-around solution: uname -r $CURRENT-KERNEL$ dpkg --list 'linux-image-*' sudo apt-get purge $PREVIOUS-KERNEL$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
5.8.0-36-generic was just installed as part of the 20.04 HWE and it does not boot without intremap=off. What does that mean? Was this fixed in 5.7 and broken again in 5.8? Do I need to do another rebase? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808418 Title: Thinkpad T430u won't boot without noapic workaround Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 - 4.20.0-rc7 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. This bug seems very similar to what's described here for the Thinkpad E485/E585: https://evilazrael.de/node/401 I'll attach screenshots of various times I've encountered this bug over the last year. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy linux-image-4.15.0-42-generic linux-image-4.15.0-42-generic: Installed: 4.15.0-42.45 Candidate: 4.15.0-42.45 Version table: *** 4.15.0-42.45 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910921] [NEW] Keyboard short conflict since upgrade to 20.10
Public bug reported: Starting Dolphin since Upgrade to Kubuntu 20.10 shows a message notifying about keyboard short cut conflict. the orginal keymapping was not changed. The system was originally installed with 20.04. I am happy to provide more info such as diff on keyboard mapping etc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Error message" https://bugs.launchpad.net/bugs/1910921/+attachment/5451505/+files/Dolphin%20-%20bug%20-%20shortcuts%20-%20Screenshot_20210110_183846.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910921 Title: Keyboard short conflict since upgrade to 20.10 Status in linux package in Ubuntu: New Bug description: Starting Dolphin since Upgrade to Kubuntu 20.10 shows a message notifying about keyboard short cut conflict. the orginal keymapping was not changed. The system was originally installed with 20.04. I am happy to provide more info such as diff on keyboard mapping etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910920] [NEW] no soundcard present with linux-image-5.8.0-37-generic
Public bug reported: With linux-image-5.8.0-34-generic, all on-board soundcards work flawlessly. After update of kernel to linux-image-5.8.0-37-generic durign this week no soundcards are detected. I am happy to provide more information. But I will not sent automatic apport reports because it includes private local data. !!DMI Information !!--- Manufacturer: LENOVO Product Name: 20BUS23M00 Product Version: ThinkPad T450 Firmware Version: JBET54WW (1.19 ) Board Vendor: LENOVO Board Name:20BUS23M00 !!Kernel Information !!-- Kernel release:5.8.0-34-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.8.0-34-generic Library version:1.2.3.2 Utilities version: 1.2.3 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xe123 irq 51 1 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe1234000 irq 52 !!PCI Soundcards installed in the system !!-- 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller [17aa:5034] 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller [17aa:5034] ** 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/1910920 Title: no soundcard present with linux-image-5.8.0-37-generic Status in linux package in Ubuntu: New Bug description: With linux-image-5.8.0-34-generic, all on-board soundcards work flawlessly. After update of kernel to linux-image-5.8.0-37-generic durign this week no soundcards are detected. I am happy to provide more information. But I will not sent automatic apport reports because it includes private local data. !!DMI Information !!--- Manufacturer: LENOVO Product Name: 20BUS23M00 Product Version: ThinkPad T450 Firmware Version: JBET54WW (1.19 ) Board Vendor: LENOVO Board Name:20BUS23M00 !!Kernel Information !!-- Kernel release:5.8.0-34-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.8.0-34-generic Library version:1.2.3.2 Utilities version: 1.2.3 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xe123 irq 51 1 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe1234000 irq 52 !!PCI Soundcards installed in the system !!-- 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller [17aa:5034] 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller [17aa:5034] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910917] [NEW] no access to hdmi screen after power failure
Public bug reported: After laptop shut down(battery low - not enough time to plug in AC) secondary screen (on hdmi) is not detected ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-34-generic Date: Thu Jan 7 06:43:22 2021 DuplicateSignature: dkms:nvidia-dkms-440-server:440.95.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.95.01/build/common/inc/nv-linux.h:512:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-07-02 (192 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 440.95.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-440-server Title: nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-440-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440-server in Ubuntu. https://bugs.launchpad.net/bugs/1910917 Title: no access to hdmi screen after power failure Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Bug description: After laptop shut down(battery low - not enough time to plug in AC) secondary screen (on hdmi) is not detected ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-34-generic Date: Thu Jan 7 06:43:22 2021 DuplicateSignature: dkms:nvidia-dkms-440-server:440.95.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.95.01/build/common/inc/nv-linux.h:512:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-07-02 (192 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 440.95.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-440-server Title: nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440-server/+bug/1910917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910875] Re: Broadcom wireless driver failed to install with code 10 on focal 20.04
This bug looks more like a duplicate of Bug #1910555
Take a look there for workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1910875
Title:
Broadcom wireless driver failed to install with code 10 on focal
20.04
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
First, I suspect this may be the same bug as Bug #1905211 "package
bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in
kernel v5.9" because I got the same error "installed bcmwl-kernel-
source package post-installation script subprocess returned error exit
status 10". However, I wanted to make a separate report because I am
still on kernel v5.8. Please merge these threads if it seems like
they're the same bug.
Anyway, my problem is this:
The last time I installed a tranche of system updates, I got a "System
software problem detected" dialog and submitted the crash report. The
next time I booted up my computer, the Broadcom wifi device was not
recognized. The wifi had worked fine up until that point.
I tried to manually uninstall and reinstall the driver using dpkg with
the bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) package
downloaded from packages.ubuntu.com (the machine in question does not
have a wired ethernet connection). dpkg produced the following
output:
Preparing to unpack bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb
...
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) over
(6.30.223.271+bdcom-0ubuntu5) ...
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.8.0-36-generic
Building for architecture x86_64
Building initial module for 5.8.0-36-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/bcmwl-kernel-source.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more
information.
dpkg: error processing package bcmwl-kernel-source (--install):
installed bcmwl-kernel-source package post-installation script subprocess
returned error exit status 10
Errors were encountered while processing:
bcmwl-kernel-source
The make log from my manually installation attempt read:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-36-generic
(x86_64)
Sat 09 Jan 2021 01:14:26 PM PST
make: Entering directory '/usr/src/linux-headers-5.8.0-36-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva =
[Kernel-packages] [Bug 1910280] Re: can't adjust my screen_brightness
UPDATE: made the change permanent and also fixed the issue for windows -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910280 Title: can't adjust my screen_brightness Status in linux package in Ubuntu: Confirmed Bug description: Im using my machine since 20.12.20 and use it in dual boot with windows10 alongside. Hotkeys and adjusting brightness via GUI both broken, since formatting the machine on day 1. Before formatting, adjusting brightness was possible in windows10, but not in ubuntu or other linux distro, that I tried out. There is no bar in the top right corner under the bar for adjusting the sound output. Because "The description is too long. If you have lots of text to add, attach a file to the bug instead." the description is added as .txt- file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bella 2076 F pulseaudio /dev/snd/pcmC0D0p: bella 2076 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 13:58:37 2021 InstallationDate: Installed on 2020-12-25 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20VH001CGE ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=2850ca84-1b0f-4cdd-ac66-5b9c964159e6 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET29W (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VH001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR1FET29W(1.03):bd10/08/2020:svnLENOVO:pn20VH001CGE:pvrThinkPadL13Gen2:rvnLENOVO:rn20VH001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L13 Gen 2 dmi.product.name: 20VH001CGE dmi.product.sku: LENOVO_MT_20VH_BU_Think_FM_ThinkPad L13 Gen 2 dmi.product.version: ThinkPad L13 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910280] Re: can't adjust my screen_brightness
wow. that finally solved my issue. thank you very much alex hung! how do I make this change permanent and also working on my windows os? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910280 Title: can't adjust my screen_brightness Status in linux package in Ubuntu: Confirmed Bug description: Im using my machine since 20.12.20 and use it in dual boot with windows10 alongside. Hotkeys and adjusting brightness via GUI both broken, since formatting the machine on day 1. Before formatting, adjusting brightness was possible in windows10, but not in ubuntu or other linux distro, that I tried out. There is no bar in the top right corner under the bar for adjusting the sound output. Because "The description is too long. If you have lots of text to add, attach a file to the bug instead." the description is added as .txt- file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bella 2076 F pulseaudio /dev/snd/pcmC0D0p: bella 2076 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 13:58:37 2021 InstallationDate: Installed on 2020-12-25 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20VH001CGE ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=2850ca84-1b0f-4cdd-ac66-5b9c964159e6 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R1FET29W (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20VH001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR1FET29W(1.03):bd10/08/2020:svnLENOVO:pn20VH001CGE:pvrThinkPadL13Gen2:rvnLENOVO:rn20VH001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L13 Gen 2 dmi.product.name: 20VH001CGE dmi.product.sku: LENOVO_MT_20VH_BU_Think_FM_ThinkPad L13 Gen 2 dmi.product.version: ThinkPad L13 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907557] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1907445 *** https://bugs.launchpad.net/bugs/1907445 thanks armishra your post help me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1907557 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:16:44 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1907557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451451/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451460/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451459/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451463/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451464/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451455/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451454/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451462/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451466/+files/UdevDb.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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451465/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451457/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451452/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451453/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451458/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451461/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451456/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rishiraj 1366 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 15-3568 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.187.7 Tags: focal wayland-session Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 01Y1RD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] Re: Screen Keeps Blinking/Flickering after waking up from lock
apport information ** Tags added: apport-collected wayland-session ** Description changed: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: rishiraj 1366 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-10 (0 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Dell Inc. Vostro 15-3568 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=ac2bc6f4-820f-41d4-b012-59118c273761 ro quiet splash drm.debug=0x1e log_buf_len=4M vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-36-generic N/A + linux-backports-modules-5.8.0-36-generic N/A + linux-firmware1.187.7 + Tags: focal wayland-session + Uname: Linux 5.8.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/23/2017 + dmi.bios.release: 1.8 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 01.08.00 + dmi.board.name: 01Y1RD + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:br1.8:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01Y1RD:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.family: Vostro + dmi.product.name: Vostro 15-3568 + dmi.product.sku: 0794 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1910861/+attachment/5451450/+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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display:
[Kernel-packages] [Bug 1713017] Re: Enable MIDI support
@henning that sounds great! In which version did you see this? I expect the build would also need the libasound2-dev dependency, which should be in the control file. I remember that indeed an alsa sequencer device was created on connection; I only tested (when submitting this bug) midi controllers that provided midi notes, which could drive a drum synth (not the other direction), but I'd expect both directions to work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1713017 Title: Enable MIDI support Status in bluez package in Ubuntu: Triaged Bug description: Now that bluez has landed with 5.46-0ubuntu2, it would be nice to enable Bluetooth MIDI support. This did not seem to be enabled by default in the build from https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE MIDI devices, gatttool could talk to them, but no MIDI device was made; also ldd showed no linkage to libasound.so.2). After recompiling it with libasound2-dev installed and --enable-midi in debian/rules, it worked. Suggestion: add libasound2-dev to bluez dependencies, add --enable- midi to rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] 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 1910861 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] Re: Screen Keeps Blinking/Flickering after waking up from lock
** Package changed: gnome-shell-extension-ubuntu-dock (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/1910861 Title: Screen Keeps Blinking/Flickering after waking up from lock Status in linux package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910861] [NEW] Screen Keeps Blinking/Flickering after waking up from lock
You have been subscribed to a public bug: Description:Ubuntu 20.04.1 LTS Release:20.04 What you expected to happen? After waking up from lock it should show the enter password screen and then after entering password it should show desktop What happened instead? After waking up the machine from lock , its starts flickering/blinking with black backlight for some times (from 20 seconds to 5 mins) and then shows enter password screen to login. Following is my hardware information along with a short video what happens Hardware Information : System:Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 15-3568 v: N/A serial: Mobo: Dell model: 01Y1RD v: A00 serial: UEFI: Dell v: 01.08.00 date: 03/23/2017 CPU: Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 Speed: 800 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 802 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.8 driver: i915 resolution: 1366x768~48Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 direct render: Yes Video Link : hhttps://youtu.be/XPfYNbduPig ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: ubuntu20.04 unity -- Screen Keeps Blinking/Flickering after waking up from lock https://bugs.launchpad.net/bugs/1910861 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 1910900] Re: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
You need to provide /var/lib/dkms/nvidia/390.141/build/make.log ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910900 Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: sometimes works great ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-dkms-390 390.141-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 10 02:36:18 2021 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910900] [NEW] package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error e
Public bug reported: sometimes works great ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-dkms-390 390.141-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 10 02:36:18 2021 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910900 Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: sometimes works great ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-dkms-390 390.141-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 10 02:36:18 2021 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907557] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1907445 *** https://bugs.launchpad.net/bugs/1907445 Thanks armishra and papasumit. Solved now -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1907557 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:16:44 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1907557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
Solved in 5.10.6 (installed and tried today).
Bug can be marked as solved.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887968
Title:
Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a
[Kernel-packages] [Bug 1906515] Re: Bluetooth : No device found (rtl8822cu)
*** This bug is a duplicate of bug 1887968 *** https://bugs.launchpad.net/bugs/1887968 Solved in 5.10.6 (installed and tried today). Bug can be marked as solved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906515 Title: Bluetooth : No device found (rtl8822cu) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, The bluetooth with device rtl8822cu does not work with 5.9.12 mainline kernel (and all 5.9 kernel). Before it worked fine with 5.8.0 mainline kernel. A similar problem was solved for rl8822ce in 5.9.11 kernel by arch. Discussion here : https://bbs.archlinux.org/viewtopic.php?pid=1940003#p1940003 meloli@Asus-A17:~$ sudo dmesg | grep -i bluetooth [1.476073] usb 5-1: Product: Bluetooth Radio [3.977975] Bluetooth: Core ver 2.22 [3.978022] Bluetooth: HCI device and connection manager initialized [3.978030] Bluetooth: HCI socket layer initialized [3.978035] Bluetooth: L2CAP socket layer initialized [3.978043] Bluetooth: SCO socket layer initialized [4.002039] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [4.003996] Bluetooth: hci0: RTL: rom_version status=0 version=3 [4.004001] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin [4.006885] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin [4.007705] Bluetooth: hci0: RTL: cfg_sz 6, total sz 31422 [4.283989] Bluetooth: hci0: RTL: fw version 0x09993aa1 [4.933204] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [4.933207] Bluetooth: BNEP filters: protocol multicast [4.933214] Bluetooth: BNEP socket layer initialized [ 1422.650815] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 1422.652695] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 1422.652725] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin [ 1422.652877] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin [ 1422.653058] Bluetooth: hci0: RTL: cfg_sz 6, total sz 31422 [ 1422.931399] Bluetooth: hci0: RTL: fw version 0x09993aa1 [ 1632.862056] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=0999 lmp_ver=0a lmp_subver=3aa1 [ 1632.862064] Bluetooth: hci0: RTL: unknown IC info, lmp subver 3aa1, hci rev 0999, hci ver 000a [ 1632.862065] Bluetooth: hci0: RTL: assuming no firmware upload needed meloli@Asus-A17:~$ lsmod|grep blue bluetooth 647168 12 btrtl,btintel,btbcm,bnep,btusb ecdh_generic 16384 1 bluetooth meloli@Asus-A17:~$ lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 002: ID 13d3:3548 IMC Networks Bluetooth Radio Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub meloli@Asus-A17:~$ rfkill list all 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-18 (75 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: focal Uname: Linux 5.9.12-050912-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1906515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
