[Kernel-packages] [Bug 1849721] Re: Raydium Touchscreen on ThinkPad L390 does not work
Hey Feng, the touchscreen with this kernel does work! Thank you for the help, I appreciate it. This commit is not in the master yet - is it fine to use this kernel until the commit is in the official kernel release? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849721 Title: Raydium Touchscreen on ThinkPad L390 does not work Status in linux package in Ubuntu: Confirmed Bug description: I have bought new Lenovo ThinkPad L390 with touchscreen and it works fine on Windows, but not on Ubuntu. I've tried Ubuntu LTS 18.4, 19.4 and 19.10. I've tried installing Ubuntu and running Live USB image, and also other distributions (Manjaro i3, Kubuntu). There is an Ubuntu certification with the same touchscreen using Ubuntu 18.4: https://certification.ubuntu.com/hardware/201812-26720 Other info: - `xinput` is showing touchscreen: "Raydium Touchscreen id=10 [slave pointer (2)]" - if I list device props using `xinput list-props 10`, I see device: `Device Node (277): "/dev/input/event9"` - `cat /dev/input/event9` does not produce anything - `xinput --test-xi2 --root` does not produce any touchscreen events, even though events from other devices are successfully shown Also, attached `ubuntu-bug` report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1821 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 24 18:32:07 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NRCTO1WW:pvrThinkPadL390:rvnLENOVO:rn20NRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NRCTO1WW dmi.product.sku: LENOVO_MT_20NR_BU_Think_FM_ThinkPad L390 dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
The upstream has some fixes for v3d driver, I applied them to the kernel and built a testing kernel: https://people.canonical.com/~hwang4/v3d-fix/ Please also monitor the dmesg, to see if there are some "gpu mmc pte errors" in the dmesg. thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: While using Ubuntu 19.10 with either MATE or GNOME, I can use only 1920x1080 resolution instead of the full 2560x1440. If extra pixels are configured, they fall off the right side or bottom of the display and are not visible. Reproduced on Raspberry Pi 4 with 3GB max workaround. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: User Name 5.3.0-1008.9-raspi2 5.3.1 Uname: Linux 5.3.0-1008-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 18:18:23 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:38:DF:15 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) 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.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 N/A 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-raspi2/+bug/1852035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852837] Re: Ubuntu 19.10 boots into blinking underscore when manually restart, not even grub shows up!
I have cleaned installed Ubuntu once again but this time upgraded package by package, the problem occurs after upgrading one of these packages to the latest version: amd64-microcode intel-microcode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852837 Title: Ubuntu 19.10 boots into blinking underscore when manually restart, not even grub shows up! Status in linux package in Ubuntu: Confirmed Bug description: Hello, I didn't exactly know which category to slected during bug report submission, but after I updated my Ubuntu 19.10 installation yesterday, whenever I press restart either through gui or terminal the system boot into blinking underscore immediately after bios post screen. Not even grub menu shows up. I have to shutdown the system, then turn it on again to fix the problem. The system boot normally from a shutdown. I have already tried clean installing Ubuntu 19.10 but the problem returned after installing the updates by executing sudo apt upgrade command! I guess this issue happens after upgrading the linux-firmware package to the latest 1.183.2 version. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..65.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:65:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 15 22:56:48 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-23-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2019-11-16 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=c39caed8-873a-4a54-a075-6917258f368e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2002 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2002:bd09/25/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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/linux/+bug/1852837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] Re: Possible cause for 19.10 invisible cursor with Matrox graphics
** 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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Confirmed Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307375/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307370/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307372/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307377/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307379/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307380/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307378/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307371/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307369/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307366/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307367/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307368/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- 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 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] Re: Possible cause for 19.10 invisible cursor with Matrox graphics
apport information ** Tags added: apport-collected uec-images ** Description changed: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + MachineType: LENOVO System x3650 M5 -[8871AC1]- + 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 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 + ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-23-generic N/A + linux-backports-modules-5.3.0-23-generic N/A + linux-firmware1.183.2 + RfKill: + + Tags: eoan uec-images + Uname: Linux 5.3.0-23-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) + UserGroups: adm cdrom dip libvirt lxd plugdev sudo + _MarkForUpload: True + dmi.bios.date: 06/03/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: -[TCE140H-2.91]- + dmi.board.asset.tag: (none) + dmi.board.name: 01KN179 + dmi.board.vendor: LENOVO + dmi.board.version: NULL + dmi.chassis.asset.tag: none + dmi.chassis.type: 23 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: none + dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: + dmi.product.family: System X + dmi.product.name: System x3650 M5 -[8871AC1]- + dmi.product.sku: (none) + dmi.product.version: 13 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1853721/+attachment/5307365/+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/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5
[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
This bug was fixed in the package lvm2 - 2.03.02-2ubuntu7 --- lvm2 (2.03.02-2ubuntu7) focal; urgency=medium * Include raid1 in the list of modules installed by the initramfs hook, as this is not a kernel module dependency of dm-raid but if the user's root disk is configured as RAID1 it is definitely required. Closes: #841423, LP: #1509717. -- Steve Langasek Fri, 22 Nov 2019 13:59:47 -0800 ** Changed in: lvm2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: New Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: New Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Triaged Status in lvm2 package in Debian: Incomplete Bug description: After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO
I gave 5.3.0-23.25~18.04.2 on the canonical kernel team ppa a try, but it looks like the signing issue still persists. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852581 Title: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-hwe-edge source package in Eoan: Invalid Bug description: SRU Justification Impact: The fix for bug 1850234 does not function as intended in bionic, as a result of modinfo not knowing about module signatures. This results in no modules being signed in hwe kernels based on 5.3, rendering systems with secure boot enabled unbootable. Fix: Check for the module signature at the end of modules instead of relying on modinfo. This can be done without any external tools needing to be aware of module signatures. Test Case: Check that all built modules contain signatures, except for those in staging which have not been whitelisted. Regression Potential: I can think of two possible regression situations. We could regress to the behavior prior to the fix for bug 1850234, or the eoan 5.3 kernel could also end up with all modules unsigned. I've done test builds of both the eoan 5.3 kernel and the bionic 5.3 hwe-edge kernel with this patch and checked that the results are as intended. We should also check this again once new kernels have been built, before copying them out to -proposed. --- The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message that it cannot find the UUID associated with the root partition. The user gets dropped to a busybox shell with an initramfs prompt. The standard hwe kernel does not have this issue and the last hwe-edge kernel that does work is 5.3.0-19.20. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04-edge 5.3.0.23.90 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 08:19:57 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-09-01 (73 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] 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 1853721 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: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] [NEW] Possible cause for 19.10 invisible cursor with Matrox graphics
Public bug reported: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Incomplete Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791312]
thank you for your tip, we can face a problem. Can I use free this -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] Screen flickers when using radeon.ko. It's a regression, it didn't happen on Trusty. [Fix] Quote the original commit log: "Instead of the closest reference divider prefer the lowest". [Test] Affected user confirms it fixes the issue. [Regression Potential] Low. Only affect radeaon, and it's in upstream stable tree. === Original Bug Report === my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1791312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852220] Re: eoan/linux-raspi2: 5.3.0-1013.15 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 22. November 2019 01:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: eoan/linux-raspi2/pi-kernel: bug 1852219 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852220 Title: eoan/linux-raspi2: 5.3.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 22. November 2019 01:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: eoan/linux-raspi2/pi-kernel: bug 1852219 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852837] Re: Ubuntu 19.10 boots into blinking underscore when manually restart, not even grub shows up!
log attached by executing journalctl -b -1 -k ** Attachment added: "boot.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852837/+attachment/5307354/+files/boot.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/1852837 Title: Ubuntu 19.10 boots into blinking underscore when manually restart, not even grub shows up! Status in linux package in Ubuntu: Confirmed Bug description: Hello, I didn't exactly know which category to slected during bug report submission, but after I updated my Ubuntu 19.10 installation yesterday, whenever I press restart either through gui or terminal the system boot into blinking underscore immediately after bios post screen. Not even grub menu shows up. I have to shutdown the system, then turn it on again to fix the problem. The system boot normally from a shutdown. I have already tried clean installing Ubuntu 19.10 but the problem returned after installing the updates by executing sudo apt upgrade command! I guess this issue happens after upgrading the linux-firmware package to the latest 1.183.2 version. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..65.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:65:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 15 22:56:48 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-23-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2019-11-16 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=c39caed8-873a-4a54-a075-6917258f368e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2002 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2002:bd09/25/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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/linux/+bug/1852837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852435] Re: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22
Secure lot is disabled, but TPM is needed for Windows disk encryption. The BUG is also present in the latest vanilla kernel from kernel.org. Will test things out and report my finding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852435 Title: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22 Status in linux package in Ubuntu: Confirmed Bug description: System doesn't boot anymore with new kernel update linux- image-5.3.0-22-generic. Here is the screenshot where the boot process stops: https://photos.app.goo.gl/6b7D2SsGBpgKWLd1A I installed old kernel packages out of local deb cache (linux- image-5.3.0-19-generic), initramfs regenerated, same boot options and was able to boot fine. I assume something went wrong with new security patches, ucode for intel CPU seems not to be an issue, because old kernel booted with newly generated initrd image. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-22-generic 5.3.0-22.24 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrej 3321 F pulseaudio /dev/snd/controlC0: andrej 3321 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 14:37:01 2019 InstallationDate: Installed on 2019-11-04 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q500E2GE ProcFB: 0 i915drmfb ProcKernelCmdLine: initrd=\initrd.img-5.3.0-19-generic BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET35W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q500E2GE 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:bvrR0ZET35W(1.13):bd10/11/2019:svnLENOVO:pn20Q500E2GE:pvrThinkPadL490:rvnLENOVO:rn20Q500E2GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L490 dmi.product.name: 20Q500E2GE dmi.product.sku: LENOVO_MT_20Q5_BU_SMB_FM_ThinkPad L490 dmi.product.version: ThinkPad L490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby
penalvch: in view of the fact that we have independently confirmed the bug with the latest BIOS and the latest Ubuntu, would it now make sense to change the status back to Confirmed (and remove the bios-outdated tag)? Also, can I ask why you changed the importance down to Low? Having sound not working is a major usability problem, in my opinion. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612916 Title: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby Status in linux package in Ubuntu: Incomplete Status in linux package in Debian: New Bug description: On initial boot, sound on internal speakers is working. After standby it doesn work anymore, but a analog headset does. Switching around in pavucontrol doesn't work... Internal microphone works. I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel. Toshiba/Dynabook Portege Z20T-C: https://support.dynabook.com/support/modelHome?freeText=1200015981=785 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michi 6510 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/1tb-swap MachineType: TOSHIBA PORTEGE Z20t-C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.60 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z20t-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z20t-C dmi.product.version: PT16BE-00W006GR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking
** Changed in: linux Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1727662 Title: [Lenovo ThinkPad T450s] Issues after docking and locking Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the following three things happen ~50% of the time when I come back to unlock it: * Most of the time the computer is found shut down. * Sometimes the notebook screen flickers weirdly and one of the two external monitors show pixelation. * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking works. I have two external monitors attached to the docking station. When I dock my laptop, the battery indicator does recognize its charging. I've not seen this issue when: 1) With the laptop in the dock, while actively using the laptop. 2) With the laptop out of the dock and no external monitors present. This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10. Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 Updated docking station firmware to latest 2.33.00. PC temperatures are normal as per lm-sensors. 20171109 - Not reproducible testing drm-tip for 1.5 days. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS2YL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS2YL00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1727662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727662]
I'm happy to report that I've not had a single problem since I installed 5.4.0-rc7-drm-tip-git-g3ff71899c56c. I'm marking this as resolved, with thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1727662 Title: [Lenovo ThinkPad T450s] Issues after docking and locking Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the following three things happen ~50% of the time when I come back to unlock it: * Most of the time the computer is found shut down. * Sometimes the notebook screen flickers weirdly and one of the two external monitors show pixelation. * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking works. I have two external monitors attached to the docking station. When I dock my laptop, the battery indicator does recognize its charging. I've not seen this issue when: 1) With the laptop in the dock, while actively using the laptop. 2) With the laptop out of the dock and no external monitors present. This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10. Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 Updated docking station firmware to latest 2.33.00. PC temperatures are normal as per lm-sensors. 20171109 - Not reproducible testing drm-tip for 1.5 days. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS2YL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS2YL00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1727662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727662]
Excellent to hear, thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1727662 Title: [Lenovo ThinkPad T450s] Issues after docking and locking Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the following three things happen ~50% of the time when I come back to unlock it: * Most of the time the computer is found shut down. * Sometimes the notebook screen flickers weirdly and one of the two external monitors show pixelation. * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking works. I have two external monitors attached to the docking station. When I dock my laptop, the battery indicator does recognize its charging. I've not seen this issue when: 1) With the laptop in the dock, while actively using the laptop. 2) With the laptop out of the dock and no external monitors present. This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10. Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 Updated docking station firmware to latest 2.33.00. PC temperatures are normal as per lm-sensors. 20171109 - Not reproducible testing drm-tip for 1.5 days. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS2YL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS2YL00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1727662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
#46 Still working for me, have not had the issue since I made that change. I'm on Fedora 31 as well, fully up to date. Maybe I have just been lucky so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838154] Re: Scrolling and responsiveness is artificially low (a few ideas: syntax, window manager logic)
** Attachment added: "amazingly low temperatures (omg :D)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838154/+attachment/5307318/+files/2019-11-23_20-36-23.png ** Attachment removed: "y20190727d214233 3.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838154/+attachment/5279639/+files/y20190727d214233%20%203.png ** Attachment removed: "y20190727d214233 1.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838154/+attachment/5279641/+files/y20190727d214233%20%201.png ** Attachment removed: "y20190727d214233 2.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838154/+attachment/5279640/+files/y20190727d214233%20%202.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838154 Title: Scrolling and responsiveness is artificially low (a few ideas: syntax, window manager logic) Status in NULL Project: New Status in wayland: New Status in Xfwm4: New Status in linux package in Ubuntu: Confirmed Status in xfwm4 package in Fedora: Unknown Bug description: In XFCE4 is a trick to make temperatures cooler and win back simple responsiveness like scrolling or typing. Pls look at images. Settings: snapping top 1 and bottom 1 Unix message trick: leave recipient empty type "idiot :)) " Additional info: two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1838154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838154] Re: Scrolling and responsiveness is artificially low (a few ideas: syntax, window manager logic)
** Summary changed: - Simply snapping terminal window from the outside the screen fixes thermal build up + Scrolling and responsiveness is artificially low (a few ideas: syntax, window manager logic) ** Description changed: - If you snap terminal window from the outside of screen area - against the left edge of screen then heat build up stops. + In XFCE4 is a trick to make temperatures cooler + and win back simple responsiveness like scrolling + or typing. - Or in other words terminal either stops heating or - gives somehow unknown cooling benefit. Which should be - really strange. + Pls look at images. + + Settings: snapping top 1 and bottom 1 + + Unix message trick: leave recipient empty type "idiot :)) " + + + Additional info: + two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 + https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 + Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 + https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) ** Description changed: - In XFCE4 is a trick to make temperatures cooler and win back simple responsiveness like scrolling or typing. Pls look at images. Settings: snapping top 1 and bottom 1 Unix message trick: leave recipient empty type "idiot :)) " - Additional info: two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 + Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) ** Attachment added: "unix send message trick" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838154/+attachment/5307317/+files/2019-11-23_20-31-44.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838154 Title: Scrolling and responsiveness is artificially low (a few ideas: syntax, window manager logic) Status in NULL Project: New Status in wayland: New Status in Xfwm4: New Status in linux package in Ubuntu: Confirmed Status in xfwm4 package in Fedora: Unknown Bug description: In XFCE4 is a trick to make temperatures cooler and win back simple responsiveness like scrolling or typing. Pls look at images. Settings: snapping top 1 and bottom 1 Unix message trick: leave recipient empty type "idiot :)) " Additional info: two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1838154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769517] Re: Radeon HD 3450 acceleration not working
Launchpad has imported 6 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=106471. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-05-11T01:57:40+00:00 Josh Cogliati wrote: Created attachment 139483 full dmesg The Radeon HD 3450 acceleration support does not work on my computer. uname -a: Linux mouse 4.17.0-041700rc4-generic #201805070430 SMP Mon May 7 04:31:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux In the dmesg I get: [ 4.007419] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [ 4.007433] radeon :02:00.0: disabling GPU acceleration Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/comments/7 On 2018-05-11T14:56:49+00:00 Alexdeucher wrote: Does it work properly if you remove the nouveau card or switch the slots? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/comments/8 On 2018-05-12T00:56:31+00:00 Josh Cogliati wrote: The other video card is integrated into the motherboard, and the disabling the integrated video with bios causes the boot to fail. I could try the video card in a different computer, but that computer would have to be booted from usb since I don't want to change its os. Would a dmesg.txt from a different computer with the same video card with say a 4.15 kernel be useful? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/comments/9 On 2018-05-25T20:33:46+00:00 Josh Cogliati wrote: Created attachment 139777 dmesg from different motherboard I tried it on a different computer. I don't get the acceleration error, instead I get errors like: [drm:radeon_dvi_detect [radeon]] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID which is odd, since there no HDMI connection on the card. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/comments/10 On 2018-06-03T11:18:41+00:00 mirh wrote: Phoronix also reported 4870 not to work on 4.17. Could you try some previous kernel version? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/comments/11 On 2019-11-19T09:33:23+00:00 Martin-peres-n wrote: -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/850. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769517/comments/12 ** Changed in: linux Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #850 https://gitlab.freedesktop.org/drm/amd/issues/850 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1769517 Title: Radeon HD 3450 acceleration not working Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: The Radeon HD 3450 acceleration support does not work. In the dmesg is the information: [ 13.892364] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [ 13.892476] radeon :02:00.0: disabling GPU acceleration ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1645 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun May 6 22:28:53 2018 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 002: ID 154b:005b PNY Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper
[Kernel-packages] [Bug 1853712] [NEW] linux-cloud-tools-*-azure package is not installed when installing linux-azure-edge
Public bug reported: While installing linux-azure package, it installs linux-cloud-tools- azure Bionic + linux-azure The following NEW packages will be installed: linux-azure linux-azure-cloud-tools-5.0.0-1024 linux-azure-headers-5.0.0-1024 linux-azure-tools-5.0.0-1024 linux-cloud-tools-5.0.0-1024-azure linux-cloud-tools-azure linux-headers-5.0.0-1024-azure linux-headers-azure linux-image-5.0.0-1024-azure linux-image-azure linux-modules-5.0.0-1024-azure linux-tools-5.0.0-1024-azure linux-tools-azure 0 upgraded, 13 newly installed, 0 to remove and 280 not upgraded. But during linux-azure-edge package installation, it does not install linux-cloud-tools-azure Bionic + linux-azure-edge The following NEW packages will be installed: crda iw libnl-genl-3-200 linux-azure-5.3-headers-5.3.0-1006 linux-azure-edge linux-headers-5.3.0-1006-azure linux-headers-azure-edge linux-image-5.3.0-1006-azure linux-image-azure-edge linux-modules-5.3.0-1006-azure linux-modules-extra-5.3.0-1006-azure wireless-regdb 0 upgraded, 12 newly installed, 0 to remove and 280 not upgraded. Can we have linux-cloud-tools-azure package included as well. Let me know, if you have any questions. Thank you. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853712 Title: linux-cloud-tools-*-azure package is not installed when installing linux-azure-edge Status in linux-azure package in Ubuntu: New Bug description: While installing linux-azure package, it installs linux-cloud-tools- azure Bionic + linux-azure The following NEW packages will be installed: linux-azure linux-azure-cloud-tools-5.0.0-1024 linux-azure-headers-5.0.0-1024 linux-azure-tools-5.0.0-1024 linux-cloud-tools-5.0.0-1024-azure linux-cloud-tools-azure linux-headers-5.0.0-1024-azure linux-headers-azure linux-image-5.0.0-1024-azure linux-image-azure linux-modules-5.0.0-1024-azure linux-tools-5.0.0-1024-azure linux-tools-azure 0 upgraded, 13 newly installed, 0 to remove and 280 not upgraded. But during linux-azure-edge package installation, it does not install linux-cloud-tools-azure Bionic + linux-azure-edge The following NEW packages will be installed: crda iw libnl-genl-3-200 linux-azure-5.3-headers-5.3.0-1006 linux-azure-edge linux-headers-5.3.0-1006-azure linux-headers-azure-edge linux-image-5.3.0-1006-azure linux-image-azure-edge linux-modules-5.3.0-1006-azure linux-modules-extra-5.3.0-1006-azure wireless-regdb 0 upgraded, 12 newly installed, 0 to remove and 280 not upgraded. Can we have linux-cloud-tools-azure package included as well. Let me know, if you have any questions. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
~/.xsession-errors can also get Quite Big. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
It fills not only /var/log/syslog but also /var/log/messages and /var/log/user.log It grows very quick up to the disk limit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
My configuration is the result of the server install, plus the proposed kernel above plus: sudo apt-get install ^ubuntu-mate-core (select lightdm when prompted). After rebooting, the system comes up in graphical mode with a 1920x1080 viewport on a 2560x1440 screen buffer. It is useful for a few minutes before the kernel panic. I have an attached serial port to capture the panic output. The panic seems to occur with or without the total_mem=3072 workaround needed for previous kernels for the USB issue. The system appears otherwise stable if I disable the lightdm service and continue using the system in text mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: While using Ubuntu 19.10 with either MATE or GNOME, I can use only 1920x1080 resolution instead of the full 2560x1440. If extra pixels are configured, they fall off the right side or bottom of the display and are not visible. Reproduced on Raspberry Pi 4 with 3GB max workaround. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: User Name 5.3.0-1008.9-raspi2 5.3.1 Uname: Linux 5.3.0-1008-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 18:18:23 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:38:DF:15 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) 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.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 N/A 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-raspi2/+bug/1852035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852865] Re: Kernel bug in amdgpu system freezing
Unfortunately no improvement. I would say even worse, because I could not get a VT, so it needed a hard shutdown, after opening a something in `foliate`, Only thing working the mouse. With old kernel at least (after a time) I could open up a VT, to close and reboot. uname -a Linux desk 5.4.0-050400rc8-generic #201911171930 SMP Mon Nov 18 00:33:15 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 89.533687] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! kernel: [ 94.397626] gmc_v9_0_process_interrupt: 111 callbacks suppressed kernel: [ 94.397633] amdgpu :09:00.0: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process Xorg pid 2272 thread Xorg:cs0 pid 2275) kernel: [ 94.397638] amdgpu :09:00.0: in page starting at address 0x000117d0 from client 27 kernel: [ 94.397641] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 kernel: [ 94.397643] amdgpu :09:00.0: MORE_FAULTS: 0x1 kernel: [ 94.397646] amdgpu :09:00.0: WALKER_ERROR: 0x0 kernel: [ 94.397648] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 kernel: [ 94.397650] amdgpu :09:00.0: MAPPING_ERROR: 0x0 kernel: [ 94.397651] amdgpu :09:00.0: RW: 0x0 kernel: [ 94.397662] amdgpu :09:00.0: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32769, for process Xorg pid 2272 thread Xorg:cs0 pid 2275) kernel: [ 94.397664] amdgpu :09:00.0: in page starting at address 0x000117d0 from client 27 kernel: [ 94.397666] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 kernel: [ 94.397668] amdgpu :09:00.0: MORE_FAULTS: 0x1 kernel: [ 94.397670] amdgpu :09:00.0: WALKER_ERROR: 0x0 kernel: [ 94.397672] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 kernel: [ 94.397674] amdgpu :09:00.0: MAPPING_ERROR: 0x0 kernel: [ 94.397676] amdgpu :09:00.0: RW: 0x0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852865 Title: Kernel bug in amdgpu system freezing Status in linux package in Ubuntu: Confirmed Bug description: Running any flatpak package like Foliate of Visual Studio Code freezes system in Ubuntu 19.10. Worked fine in 19.04 Description: Ubuntu 19.10 Release: 19.10 Only see it when using flatpak. For the rest system is quite stable. Lots of errors in syslog: mdgpu :09:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:3 pasid:32769, for process Xorg pid 2137 thread Xorg:cs0 pid 2138) amdgpu :09:00.0: in page starting at address 0x00011a50 from 27 amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 Also errors in Gnone-shell: gnome-shell[2440]: [GFX1]: Shader compilation failure, cfg: features: 0 multiplier: 1 op: CompositionOp::OP_OVER gnome-shell[2440]: message repeated 5 times: [ [GFX1]: Shader compilation failure, cfg: features: 0 multiplier: 1 op: CompositionOp::OP_OVER] gnome-shell[2440]: Object .Gjs_WindowSwitcherPopup (0x557f7238f500), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ben2111 F pulseaudio /dev/snd/controlC0: ben2111 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 20:08:36 2019 InstallationDate: Installed on 2019-07-19 (120 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=7fb304cc-a08f-4ccf-945c-f9f1556d4342 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-28 (19 days ago) dmi.bios.date: 02/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1852266] Re: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1852266 Title: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838154] Re: Simply snapping terminal window from the outside the screen fixes thermal build up
** Project changed: xorg-server => null-and-void -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838154 Title: Simply snapping terminal window from the outside the screen fixes thermal build up Status in NULL Project: New Status in wayland: New Status in Xfwm4: New Status in linux package in Ubuntu: Confirmed Status in xfwm4 package in Fedora: Unknown Bug description: If you snap terminal window from the outside of screen area against the left edge of screen then heat build up stops. Or in other words terminal either stops heating or gives somehow unknown cooling benefit. Which should be really strange. :-) To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1838154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853701] Re: thermald not works on intel GeminiLake
** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Tags added: originate-from-1850248 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853701 Title: thermald not works on intel GeminiLake Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux package in Ubuntu: Incomplete Bug description: After the patch landed by "LP: #1851506 Add GeminiLake support on Intel int340x thermal device" The thermal zone "TCPU" is corretly created, but thermald still not work as expected on bionic so system will shutdown by cpu stress test. But thermald 1.9 works well with patched kernel, so it might some patches needed for thermald 1.7 on bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1853701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853701] [NEW] thermald not works on intel GeminiLake
Public bug reported: After the patch landed by "LP: #1851506 Add GeminiLake support on Intel int340x thermal device" The thermal zone "TCPU" is corretly created, but thermald still not work as expected on bionic so system will shutdown by cpu stress test. But thermald 1.9 works well with patched kernel, so it might some patches needed for thermald 1.7 on bionic. ** Affects: oem-priority Importance: Critical Assignee: Alex Tu (alextu) Status: New ** Affects: oem-priority/bionic Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: originate-from-1850248 ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853701 Title: thermald not works on intel GeminiLake Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux package in Ubuntu: Incomplete Bug description: After the patch landed by "LP: #1851506 Add GeminiLake support on Intel int340x thermal device" The thermal zone "TCPU" is corretly created, but thermald still not work as expected on bionic so system will shutdown by cpu stress test. But thermald 1.9 works well with patched kernel, so it might some patches needed for thermald 1.7 on bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1853701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853701] 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 1853701 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/1853701 Title: thermald not works on intel GeminiLake Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux package in Ubuntu: Incomplete Bug description: After the patch landed by "LP: #1851506 Add GeminiLake support on Intel int340x thermal device" The thermal zone "TCPU" is corretly created, but thermald still not work as expected on bionic so system will shutdown by cpu stress test. But thermald 1.9 works well with patched kernel, so it might some patches needed for thermald 1.7 on bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1853701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
That line was already commented out (#dtoverlay=vc4-fkms-v3d) in config.txt so I blacklisted module v3d, works now better with 1013 kernel. Thanks. On Sat, Nov 23, 2019 at 2:05 PM Hui Wang wrote: > @Jussi, > > I found that issue too. the driver v3d.ko crashed. In the 1013, we > enabled v3d.ko, while before the 1013, the v3d.ko is disabled. > > You could change dtoverlay=vc4-fkms-v3d to #dtoverlay=vc4-fkms-v3d in > the config.txt, then boot with 1013 kernel, system will use fbdev as > before. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1848790 > > Title: > USB not working under arm64 on Pi4 with 4G ram > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions > -- -jussi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb 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 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb 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 The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847643] Re: iwlwifi during heavy transfers on XPS15 7590 (19.10)
Oops - replication steps are actually in another bug linked from that bugzilla page: https://bugzilla.kernel.org/show_bug.cgi?id=205061 ** Bug watch added: Linux Kernel Bug Tracker #205061 https://bugzilla.kernel.org/show_bug.cgi?id=205061 -- 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/1847643 Title: iwlwifi during heavy transfers on XPS15 7590 (19.10) Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Bug description: I'm running 19.10 (beta). The Dell's 7590 wifi card is identified in `lspci` as: 3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a) From my googling the Dell 7590 seems to have a Killer AX1650 (in collaboration with Intel?) And when uploading a massive image to say S3, for example through CLI or browser, I get the following messages in `dmesg` after a few dozens of MB, at which point the net is killed and I need to turn the wifi off and on again to get online: [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump: [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6 [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0 [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0 [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1 [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2 [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1 [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2 [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1 [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2 [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3 [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1 [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2 [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0 [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1 [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2 [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3 [234483.616572] iwlwifi :3b:00.0: 0x | isr4 [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel [234483.616577] iwlwifi :3b:00.0: 0x | timestamp [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump: [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7 [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1 [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2 [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1 [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2 [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1 [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2 [234483.616657] iwlwifi :3b:00.0: 0x | umac data3 [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg [234483.616688] iwlwifi :3b:00.0: Fseq Registers: [234483.616700] iwlwifi :3b:00.0: 0xE101 | FSEQ_ERROR_CODE [234483.616712] iwlwifi :3b:00.0: 0x00290006 | FSEQ_TOP_INIT_VERSION [234483.616724] iwlwifi :3b:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION [234483.616735] iwlwifi :3b:00.0:
[Kernel-packages] [Bug 1847643] Re: iwlwifi during heavy transfers on XPS15 7590 (19.10)
FWIW, it appears that somebody has found the bug in the driver that results in this issue and created a patch for it. There are also replication steps here: https://bugzilla.kernel.org/show_bug.cgi?id=205109 Here is the patch: https://patchwork.kernel.org/patch/11253471/ I'm personally experiencing this when performing large sftp transfers over my internal wifi network. Jay ** Bug watch added: Linux Kernel Bug Tracker #205109 https://bugzilla.kernel.org/show_bug.cgi?id=205109 -- 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/1847643 Title: iwlwifi during heavy transfers on XPS15 7590 (19.10) Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Bug description: I'm running 19.10 (beta). The Dell's 7590 wifi card is identified in `lspci` as: 3b:00.0 Network controller: Intel Corporation Device 2723 (rev 1a) From my googling the Dell 7590 seems to have a Killer AX1650 (in collaboration with Intel?) And when uploading a massive image to say S3, for example through CLI or browser, I get the following messages in `dmesg` after a few dozens of MB, at which point the net is killed and I need to turn the wifi off and on again to get online: [234483.616399] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. [234483.616553] iwlwifi :3b:00.0: Start IWL Error Log Dump: [234483.616554] iwlwifi :3b:00.0: Status: 0x0080, count: 6 [234483.616555] iwlwifi :3b:00.0: Loaded firmware version: 48.4fa0041f.0 [234483.616556] iwlwifi :3b:00.0: 0x103C | ADVANCED_SYSASSERT [234483.616557] iwlwifi :3b:00.0: 0x0080A201 | trm_hw_status0 [234483.616558] iwlwifi :3b:00.0: 0x | trm_hw_status1 [234483.616558] iwlwifi :3b:00.0: 0x004F8E3C | branchlink2 [234483.616559] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink1 [234483.616560] iwlwifi :3b:00.0: 0x004E4FF4 | interruptlink2 [234483.616560] iwlwifi :3b:00.0: 0x00408FAC | data1 [234483.616561] iwlwifi :3b:00.0: 0xDEADBEEF | data2 [234483.616562] iwlwifi :3b:00.0: 0xDEADBEEF | data3 [234483.616562] iwlwifi :3b:00.0: 0x0E0116FA | beacon time [234483.616563] iwlwifi :3b:00.0: 0xB0DF7916 | tsf low [234483.616564] iwlwifi :3b:00.0: 0x02C7 | tsf hi [234483.616564] iwlwifi :3b:00.0: 0x00011696 | time gp1 [234483.616565] iwlwifi :3b:00.0: 0xF7C6EE47 | time gp2 [234483.616565] iwlwifi :3b:00.0: 0x0001 | uCode revision type [234483.616566] iwlwifi :3b:00.0: 0x0030 | uCode version major [234483.616567] iwlwifi :3b:00.0: 0x4FA0041F | uCode version minor [234483.616567] iwlwifi :3b:00.0: 0x0340 | hw version [234483.616568] iwlwifi :3b:00.0: 0x00C89000 | board version [234483.616569] iwlwifi :3b:00.0: 0x06AE001C | hcmd [234483.616569] iwlwifi :3b:00.0: 0xE6F23000 | isr0 [234483.616570] iwlwifi :3b:00.0: 0x01448000 | isr1 [234483.616571] iwlwifi :3b:00.0: 0x08F00112 | isr2 [234483.616571] iwlwifi :3b:00.0: 0x00C1FFDC | isr3 [234483.616572] iwlwifi :3b:00.0: 0x | isr4 [234483.616573] iwlwifi :3b:00.0: 0x0682001C | last cmd Id [234483.616573] iwlwifi :3b:00.0: 0x97BE | wait_event [234483.616574] iwlwifi :3b:00.0: 0x00C4 | l2p_control [234483.616575] iwlwifi :3b:00.0: 0x0001CC14 | l2p_duration [234483.616575] iwlwifi :3b:00.0: 0x0007 | l2p_mhvalid [234483.616576] iwlwifi :3b:00.0: 0x0081 | l2p_addr_match [234483.616577] iwlwifi :3b:00.0: 0x0009 | lmpm_pmg_sel [234483.616577] iwlwifi :3b:00.0: 0x | timestamp [234483.616578] iwlwifi :3b:00.0: 0x5800 | flow_handler [234483.616651] iwlwifi :3b:00.0: Start IWL Error Log Dump: [234483.616651] iwlwifi :3b:00.0: Status: 0x0080, count: 7 [234483.616652] iwlwifi :3b:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [234483.616653] iwlwifi :3b:00.0: 0x | umac branchlink1 [234483.616653] iwlwifi :3b:00.0: 0xC008CC3C | umac branchlink2 [234483.616654] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink1 [234483.616655] iwlwifi :3b:00.0: 0x8048D0E6 | umac interruptlink2 [234483.616655] iwlwifi :3b:00.0: 0x0400 | umac data1 [234483.616656] iwlwifi :3b:00.0: 0x8048D0E6 | umac data2 [234483.616657] iwlwifi :3b:00.0: 0x | umac data3 [234483.616657] iwlwifi :3b:00.0: 0x0030 | umac major [234483.616658] iwlwifi :3b:00.0: 0x4FA0041F | umac minor [234483.616659] iwlwifi :3b:00.0: 0xF7C6EE57 | frame pointer [234483.616659] iwlwifi :3b:00.0: 0xC0886284 | stack pointer [234483.616660] iwlwifi :3b:00.0: 0x00C00502 | last host cmd [234483.616660] iwlwifi :3b:00.0: 0x | isr status reg [234483.616688] iwlwifi :3b:00.0: Fseq Registers: [234483.616700]
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
@Jussi, I found that issue too. the driver v3d.ko crashed. In the 1013, we enabled v3d.ko, while before the 1013, the v3d.ko is disabled. You could change dtoverlay=vc4-fkms-v3d to #dtoverlay=vc4-fkms-v3d in the config.txt, then boot with 1013 kernel, system will use fbdev as before. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb 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 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb 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 The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853030] Re: No connection through SSH over WIfi after kernel update
I've got a bit confused about the behavior of the system so I restarted the process to check what's happening. Here the steps I performed: 1. Install clean image on SD card. 2. Block internet access of the RPI, so no updates to be installed on first boot. 3. Reboot 4. Remove 50-cloud-init.yaml from /etc/netplan 5. Create eth0-dhcp.yaml in /etc/netplan with the following content: network: version: 2 ethernets: eth0: dhcp4: true dhcp6: false optional: true 6. Create wlan0-dhcp.yaml in /etc/netplan with the following content: network: version: 2 wifis: wlan0: optional: true access-points: "SSID": password: "PASS" dhcp4: true dhcp6: false 7. Execute "netplan try" and "netplan apply" 8. Reboot 9. At that point the kernel is "linux-image-5.3.0-1007-raspi2" and both adapters are connected, have their IPs and SSH is possible to both. 10. Remove ethernet cable from RPI. 11. SSH over wlan0 IP is possible. 12. Reboot 13. Check SSH over wlan0 IP - still possible. 14. Unblock internet access of the RPI and run "sudo apt-get update" 15. Install newest kernel "linux-image-5.3.0-1012-raspi2": sudo apt install linux-image-5.3.0-1012-raspi2 16. Reboot 17. SSH over wlan0 IP - NOT possible (connection time out) 18. Connect ethernet cable. 19. Check again SSH over wlan0 IP - NOT possible (connection time out) 20. Check SSH over eth0 IP - connection possible, but after 5-10 minutes of waiting. 21. Install net tools: "sudo apt install net-tools" 22. ifconfig show that only eth0 is connected. wlan0 is up, but don't have IP. 23. Reboot 24. SSH possible over eth0 and wlan0. ifconfig confirm that both adapters have their IPs. 25. Remove ethernet cable from RPI. 26. SSH not possible to wlan0. 27. Connect ethernet cable - SSH still not possible to either eth0, nor wlan0. 28. Hard reset of the RPI to reboot it - remove power supply. 29. SSH over eth0 possible. ifconfig show that wlan0 is up, but don't have IP. I performed the same steps with "linux-image-5.3.0-1013-raspi2" and the results are the same. As a summaryI would say that "linux-image-5.3.0-1007-raspi2" have no issues with plug-in, pulg-out of the ethernet cable. wlan0 and eth0 seem to work independently and together without issues. With kernels above the before mentioned, plug-in/pulg-out of the ethernet cable disrupt wlan0 and without the cable, SSH (or ping) is not possible to wlan0. Tried to revert the kernel to 1007 (on another clean image) as you suggested, but after reboot I no longer can establish SSH to RPI. And as I'm running headless, I don't know if the RPI actually booted or it's a connection issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: After updating from kernel "linux-image-5.3.0-1007-raspi2" to "linux- image-5.3.0-1012-raspi2" I no longer can establish SSH connection to Raspberry over Wifi. When it is on wired connection, SSH works and initial screen shows that both adapters (eth0 and wlan0) are connected and have their IPs. "ifconfig" confirms that both adapters are up and have their IPs. Establishing SSH session with both IPs is successful. When I disconnect the network cable, SSH is no longer possible (connection time out). In the same time the router is showing that the Raspberry is connected to the Wifi network. Plugging back the wire does not make the SSH possible. A restart of the Raspberry is required with plugged in network cable in order to establish SSH again. The system is Raspberry Pi 4, 4GB with Ubuntu server X64 image - clean install. Wifi was enabled by editing /etc/netplan/50-cloud-init.yaml and running "sudo netplan apply" Reference info for what is done so far: https://answers.launchpad.net/ubuntu/+question/685941 Output of "ubuntu-bug linux": ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Mon Nov 18 16:46:39 2019 Dependencies: adduser 3.118ubuntu1 apt 1.9.4 apt-utils 1.9.4 binutils 2.33-2ubuntu1 binutils-aarch64-linux-gnu 2.33-2ubuntu1 binutils-common 2.33-2ubuntu1 busybox-initramfs 1:1.30.1-4ubuntu4 ca-certificates 20190110 coreutils 8.30-3ubuntu2 cpio 2.12+dfsg-9ubuntu0.1 debconf 1.5.73 debconf-i18n 1.5.73 device-tree-compiler 1.4.7-3ubuntu2 devio 1.2-1.2 dpkg 1.19.7ubuntu2 e2fsprogs 1.45.3-4ubuntu2 fdisk 2.34-0.1ubuntu2 flash-kernel 3.98ubuntu5.1 gcc-9-base 9.2.1-9ubuntu2 gpgv 2.2.12-1ubuntu3 initramfs-tools 0.133ubuntu10 initramfs-tools-bin 0.133ubuntu10 initramfs-tools-core 0.133ubuntu10 klibc-utils 2.0.6-1ubuntu3 kmod 26-1ubuntu1
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
I tried kernel linux-image-5.3.0-1013-raspi2 on Pi4. I'm running mate- desktop-environment using autologin and with this kernel X-server started but only showing black screen with mouse cursor, I could log in with ssh. I rolled back to linux-image-5.3.0-1012-raspi2 for now. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+attachment/5307241/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb 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 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb 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 The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853683] Re: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1853683 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: NVIDIA-SMI couldn't find libnvidia-ml.so library in your system. Please make sure that the NVIDIA Display Driver is properly installed and present in your system. Please also try adding directory that contains libnvidia-ml.so to your system PATH. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 DKMSKernelVersion: 4.4.0-169-generic Date: Sat Nov 23 16:02:50 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.130/build/common/inc/nv-mm.h:44:9: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2017-06-02 (903 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 384.130-0ubuntu0.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 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-384/+bug/1853683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853683] [NEW] nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build
Public bug reported: NVIDIA-SMI couldn't find libnvidia-ml.so library in your system. Please make sure that the NVIDIA Display Driver is properly installed and present in your system. Please also try adding directory that contains libnvidia-ml.so to your system PATH. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 DKMSKernelVersion: 4.4.0-169-generic Date: Sat Nov 23 16:02:50 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.130/build/common/inc/nv-mm.h:44:9: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2017-06-02 (903 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 384.130-0ubuntu0.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1853683 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: NVIDIA-SMI couldn't find libnvidia-ml.so library in your system. Please make sure that the NVIDIA Display Driver is properly installed and present in your system. Please also try adding directory that contains libnvidia-ml.so to your system PATH. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 DKMSKernelVersion: 4.4.0-169-generic Date: Sat Nov 23 16:02:50 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.130/build/common/inc/nv-mm.h:44:9: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2017-06-02 (903 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 384.130-0ubuntu0.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 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-384/+bug/1853683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
