[Kernel-packages] [Bug 1901312] Re: tpm module malfunctions
Hi bluppfisk, Can you help to provide the following information: 1. upload the /sys/kernel/security/tpm0/binary_bios_measurements, you can cp it into ~/ and then upload it to Launchpad bug as it's in-memory file, so it should be amount of bytes in size. 2. check if TCG event log can be extracted by fwts sudo add-apt-repository ppa:firmware-testing-team/ppa-fwts-stable sudo apt-get update sudo apt-get install fwts sudo fwts tpmevlogdump attach results.log to this bug 3. add loglevel=8 to kernel cmdline or GRUB_CMDLINE_LINUX_DEFAULT to capture dmesg with all levels. Also attach dmesg to this bug I'm verifying various devices with TPM2 on ubuntu core and ubuntu 20.04 so maybe I can try to help for cross reference. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901312 Title: tpm module malfunctions Status in linux package in Ubuntu: Confirmed Bug description: I originally filed a bug against the fwupd software (https://github.com/fwupd/fwupd/issues/2508) from where it transpired that this problem was with the tpm package rather than with fwupd. Some evidence is in: $ sudo cat /sys/kernel/security/tpm0/binary_bios_measurements Killed The device is an XPS 13 9300 (2020 model). I can reproduce the problem on kernels 5.8, 5.9 and 5.9.1 too. Haven't tried any other kernel versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 2665 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 14:29:34 2020 HibernationDevice: # RESUME=UUID=e2b4846f-867a-4f84-a3d7-0f5d10d24a33 resume_offset=31260671 # RESUME=UUID=6a9d6823-9903-4887-bd63-11831c1218c0 # RESUME=/dev/nvme0n1p7 resume_offset=31260671 # RESUME=/dev/nvme0n1p7 # Resume from /swapfile InstallationDate: Installed on 2020-04-01 (206 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 9300 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e1b4846f-867a-4f84-a3d7-0f5d10d24a33 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (183 days ago) dmi.bios.date: 08/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0Y4GNJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd08/13/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899721] Re: Dell XPS 9300 stops responding
First coredump came from docker as below: CPU: 2 PID: 2024 Comm: dockerd Not tainted 5.4.0-48-generic #52-Ubuntu What's the deployment and configuration by using docker? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899721 Title: Dell XPS 9300 stops responding Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on a new Dell XPS 13 9300 a few weeks ago and have been experiencing a number of hangs, where keyboard and mouse stop responding, requiring a reboot. I have two LG 27" monitors connected, one of which acts as a usb hub for an external apple keyboard and trackpad. I've attached a journal from the last boot that crashed using journalctl -b -1 --no-hostname -k > dmesg.txt Any help would be appreciated. Regards, Kim ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kim3083 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 13:36:34 2020 InstallationDate: Installed on 2020-09-16 (27 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 13 9300 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=17be153f-3281-48bf-86c6-7d4af7253015 ro quiet splash pci=noaer mitigations=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd08/13/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897416] Re: grub 2.04 could not boot from iso at UEFI native environment
Hi can you try to add nomodeset into kernel parameter? basically 20.04 image should work with UEFI/secure boot, and that's what I did set up for all my machines/laptops. For example, one of my machines is Intel NUC7 and it was installed by 20.04. Or, Maybe you can update BIOS if it has the latest version available. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897416 Title: grub 2.04 could not boot from iso at UEFI native environment Status in linux package in Ubuntu: Confirmed Bug description: Dear everyone I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC. grub 2.04 can boot from iso file. and I use ubuntu-18.04.5 at my UEFI native environment note PC. grub 2.02 can boot from iso file. I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC. I power on note PC, and selecting boot device to use UEFI boot manager. then grub 2.04 boot menu displayed. I change Boot from next volume to iso boot. iso boot step as same as grub 2.02 definition. but grub 2.04 could not boot from iso, display black screen. I power off note PC. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1542 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-29 (120 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Jumper EZbook Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02 dmi.board.asset.tag: Default string dmi.board.name: EZbook dmi.board.vendor: Jumper dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: EZbook dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Jumper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856077] Re: Fix latency issue on Realtek Bluetooth
After installing linux-oem-osp1 (5.0.0-1033.38) bionic in -proposed and linux-firmware (1.173.14) bionic in -proposed, the test result is good for me. ** Tags added: verification-done-bionic -- 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/1856077 Title: Fix latency issue on Realtek Bluetooth Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Bug description: [Impact] When multiple Bluetooth devices are connected to Realtek Bluetooth controller, the BT latency becomes really high, e.g. audio stutters, mouse lags. [Fix] The new Realtek Bluetooth firmware can fix the issue. [Test] Cold boot the system to reload the new firmware, and the issue is gone. [Regression Potential] Low. The firmware is already in Eoan. We also tested it on Bionic and haven't found any regression so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1856077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850668] Re: Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly
Did you check if TPM chip was enabled on BIOS option? Refer: https://askubuntu.com/questions/1178285/how-to-solve-ima-error-communicating-to-tpm-chip-messages-during-boot/1178287 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850668 Title: Kernel repeatedly logs "ima: Error Communicating to TPM chip" and boots slowly Status in linux package in Ubuntu: Confirmed Bug description: NO se que le pasa ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01: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 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CompositorRunning: None Date: Wed Oct 30 17:33:50 2019 DistUpgraded: 2019-10-23 18:48:24,042 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.0.0-32-generic, x86_64: installed nvidia, 430.50, 5.3.0-19-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:125f] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1261] InstallationDate: Installed on 2019-08-19 (72 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire A717-72G ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=a2aeaa4e-4f3c-4b06-b9e5-ba7fe9d5ee08 ro acpi_osi=Linux acpi_backlight=vendor quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (6 days ago) dmi.bios.date: 10/31/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.22 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charizard_CFS dmi.board.vendor: CFL dmi.board.version: V1.22 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.22 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.22:bd10/31/2018:svnAcer:pnAspireA717-72G:pvrV1.22:rvnCFL:rnCharizard_CFS:rvrV1.22:cvnAcer:ct10:cvrV1.22: dmi.product.family: Aspire 7 dmi.product.name: Aspire A717-72G dmi.product.sku: dmi.product.version: V1.22 dmi.sys.vendor: Acer nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 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 19.2.1-1ubuntu1 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 1:2.10.6-1 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 xserver.bootTime: Wed Oct 30 16:11:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4509 vendor AUO xserver.version: 2:1.20.5+git20191008-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808097] Re: Console got stuck using serial tty after logout
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808097 Title: Console got stuck using serial tty after logout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit is cherry-picked by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808097] Re: Console got stuck using serial tty after logout
The -proposed kernel has verified on x86. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808097 Title: Console got stuck using serial tty after logout Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit is cherry-picked by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808097] Re: Console got stuck using serial tty after logout
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808097 Title: Console got stuck using serial tty after logout Status in linux package in Ubuntu: In Progress Bug description: [Impact] The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit is cherry-picked by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808097] Re: Console got stuck using serial tty after logout
** Description changed: [Impact] - The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. + The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] - The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit link is provided by + The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit is cherry-picked by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808097 Title: Console got stuck using serial tty after logout Status in linux package in Ubuntu: Confirmed Bug description: [Impact] The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit is cherry-picked by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808097] [NEW] Console got stuck using serial tty after logout
Public bug reported: [Impact] The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit link is provided by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Woodrow Shen (woodrow-shen) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Woodrow Shen (woodrow-shen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808097 Title: Console got stuck using serial tty after logout Status in linux package in Ubuntu: Confirmed Bug description: [Impact] The agetty stopped working using serial tty when user logged out, especially if there is a remained process. The agetty failed to open tty device due to serial port used by previous process was not released. [Test Case] 1. Run background processes from serial console $ while true; do sleep 10; done & 2. Log out $ logout 3. Read journal log by journalctl | tail Jan 28 16:07:01 ubuntu systemd[1]: Stopped Serial Getty on ttyAMA0. Jan 28 16:07:01 ubuntu systemd[1]: Started Serial Getty on ttyAMA0. Jan 28 16:07:02 ubuntu agetty[1643]: /dev/ttyAMA0: not a tty [Fix] The upstream has a fix since 4.20-rc6, which turns off TTY_IO_ERROR flag if port comes from console. The commit link is provided by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_port.c?h=v4.20-rc6=2a48602615e0a2f563549c7d5c8d507f904cf96e [Regression Potential] Should be none, and it's regression becoz 4.4 kernel didn't have this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
I verified the udev -proposed on Dell Inspiron 5767 machine and it works fine. Change tag to verification-done-bionic. Thanks. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
I verified both bionic-proposed and artful-proposed kernel on Dell Inspiron 5767 laptop, and they work fine. So I change the tag to verification-done-artful/verification-done-bionic. Thanks. ** Tags removed: verification-needed-artful verification-needed-bionic ** Tags added: verification-done-artful verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771542 Title: Suspend to idle: Open lid didn't resume Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Test Case] 1. echo s2idle | sudo tee /sys/power/mem_sleep 2. Close the lid 3. Open the lid [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 71630b7a832f to use the power button for waking up from suspend-to-idle, no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1771542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
Ok, thanks. Do I need to remove linux-oem? or you can help me to do it :) -- 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/1771542 Title: Suspend to idle: Open lid didn't resume Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Test Case] 1. echo s2idle | sudo tee /sys/power/mem_sleep 2. Close the lid 3. Open the lid [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 71630b7a832f to use the power button for waking up from suspend-to-idle, no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1771542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- 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/1771542 Title: Suspend to idle: Open lid didn't resume Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Test Case] 1. echo s2idle | sudo tee /sys/power/mem_sleep 2. Close the lid 3. Open the lid [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 71630b7a832f to use the power button for waking up from suspend-to-idle, no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1771542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
** Description changed: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Test Case] 1. echo s2idle | sudo tee /sys/power/mem_sleep 2. Close the lid 3. Open the lid [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] - no regression could be happened + Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 71630b7a832f to use the power button for waking up from suspend-to-idle, no regression could be happened -- 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/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Test Case] 1. echo s2idle | sudo tee /sys/power/mem_sleep 2. Close the lid 3. Open the lid [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 71630b7a832f to use the power button for waking up from suspend-to-idle, no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
@jsalisbury, Sorry for changing the status. Please let the bug follow your policy, thanks. ** Description changed: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. + [Test Case] + 1. echo s2idle | sudo tee /sys/power/mem_sleep + 2. Close the lid + 3. Open the lid + [Fix] - According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. + According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened ** Changed in: linux-oem (Ubuntu) Status: Triaged => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Artful) Status: Triaged => New ** Changed in: linux-oem (Ubuntu Bionic) Status: Triaged => New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux-oem (Ubuntu) Status: New => Confirmed ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Artful) ** No longer affects: linux (Ubuntu Bionic) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Woodrow Shen (woodrow-shen) ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu) Status: New => Confirmed ** No longer affects: linux-oem (Ubuntu) ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Test Case] 1. echo s2idle | sudo tee /sys/power/mem_sleep 2. Close the lid 3. Open the lid [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 71630b7a832f to use the power button for waking up from suspend-to-idle, no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
** 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/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
** Description changed: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] - According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. + According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771542] [NEW] Suspend to idle: Open lid didn't resume
Public bug reported: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-1769555 timbuktu ** Description changed: [Impact] - Some platforms is set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. + Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: New Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
Attached deb patch for bionic ** Patch added: "systemd_237-3ubuntu10_237-3ubuntu11.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+attachment/5139157/+files/systemd_237-3ubuntu10_237-3ubuntu11.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492132] Re: Fix the white noise on Dell laptop
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492132 Title: Fix the white noise on Dell laptop Status in linux package in Ubuntu: Fix Committed Bug description: Dell laptop causes the white noise by login screen and headphone, and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this noise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492132] [NEW] Fix the white noise on Dell laptop
Public bug reported: Dell laptop causes the white noise by login screen and headphone, and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this noise. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Woodrow Shen (woodrow-shen) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Woodrow Shen (woodrow-shen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492132 Title: Fix the white noise on Dell laptop Status in linux package in Ubuntu: Confirmed Bug description: Dell laptop causes the white noise by login screen and headphone, and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this noise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1492132] [alsa-devel] [PATCH] ALSA: hda - Add some FIXUP quirks for white noise on Dell laptop.
From: Woodrow Shen <woodrow.s...@canonical.com>
Dell laptop has a series model to use the same codec but different subsystem ID.
At the same time they happens the white noise by login screen and headphone;
for fixing them together, I only can add these IDs to FIXUP function
ALC292_FIXUP_DISABLE_AAMIX,
then try to solve such the similar issues.
Codec: Realtek ALC3235
Vendor Id: 0x10ec0293
Subsystem Id: 0x102806dd
Subsystem Id: 0x102806df
Subsystem Id: 0x102806e0
Cc: <sta...@vger.kernel.org>
BugLink: https://bugs.launchpad.net/bugs/1492132
Signed-off-by: Woodrow Shen <woodrow.s...@canonical.com>
---
sound/pci/hda/patch_realtek.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 4e6b090..764dd5b 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5189,8 +5189,11 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x1028, 0x06c7, "Dell",
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1028, 0x06d9, "Dell",
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1028, 0x06da, "Dell",
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
- SND_PCI_QUIRK(0x1028, 0x06de, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
SND_PCI_QUIRK(0x1028, 0x06db, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
+ SND_PCI_QUIRK(0x1028, 0x06dd, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
+ SND_PCI_QUIRK(0x1028, 0x06de, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
+ SND_PCI_QUIRK(0x1028, 0x06df, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
+ SND_PCI_QUIRK(0x1028, 0x06e0, "Dell", ALC292_FIXUP_DISABLE_AAMIX),
SND_PCI_QUIRK(0x1028, 0x164a, "Dell",
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1028, 0x164b, "Dell",
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x103c, 0x1586, "HP", ALC269_FIXUP_HP_MUTE_LED_MIC2),
--
2.1.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1492132
Title:
Fix the white noise on Dell laptop
Status in linux package in Ubuntu:
Confirmed
Bug description:
Dell laptop causes the white noise by login screen and headphone,
and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this
noise.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480142] Re: Need support for Pericom PCIe Serial Card [12d8:7952]
SKU: FAR-MT-DTV1-C1 CID: 201504-18255 The -proposed kernel (3.19.0-27.29) verified the Pericom serial device. Console log: == Welcome to minicom 2.7 OPTIONS: I18n Compiled on Jan 1 2014, 17:13:19. Port /dev/ttyUSB0, 11:46:01 Press CTRL-A Z for help on special keys Ubuntu 14.04.2 LTS u-Precision-Tower-3620 ttyS5 u-Precision-Tower-3620 login: Ubuntu 14.04.2 LTS u-Precision-Tower-3620 ttyS5 u-Precision-Tower-3620 login: u Password: Last login: Tue Aug 18 23:44:28 EDT 2015 on ttyS5 Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.19.0-27-generic x86_64) * Documentation: https://help.ubuntu.com/ u@u-Precision-Tower-3620:~$ == -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480142 Title: Need support for Pericom PCIe Serial Card [12d8:7952] Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: Pericom PCIe Serial Card [12d8:7952] doesn't work. Still in progress of upstreaming the fix to mainline. SRU Justification: Impact: https://launchpad.net/bugs/1475481 Fix: from vendor, upstreamed by Adam, accepted by Greg's tty-next by now. Testcase: already tested on a dell laptop, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1480142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484334] Re: Fix the white noise on Dell laptop
** Changed in: linux (Ubuntu) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484334 Title: Fix the white noise on Dell laptop Status in linux package in Ubuntu: Fix Committed Bug description: Dell laptop causes the white noise by login screen and headphone, and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this noise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484334] [alsa-devel][PATCH] ALSA: hda - Fix the white noise on Dell laptop
From: Woodrow Shen woodrow.s...@canonical.com
Dell laptop causes the white noise by login screen and headphone,
and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this
noise.
Codec: Realtek ALC3235
Vendor Id: 0x10ec0293
Subsystem Id: 0x102806db
Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1484334
Signed-off-by: Woodrow Shen woodrow.s...@canonical.com
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 0e3fe01..1de427a 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5190,6 +5190,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x1028, 0x06d9, Dell,
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1028, 0x06da, Dell,
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1028, 0x06de, Dell, ALC292_FIXUP_DISABLE_AAMIX),
+ SND_PCI_QUIRK(0x1028, 0x06db, Dell, ALC292_FIXUP_DISABLE_AAMIX),
SND_PCI_QUIRK(0x1028, 0x164a, Dell,
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1028, 0x164b, Dell,
ALC293_FIXUP_DELL1_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x103c, 0x1586, HP, ALC269_FIXUP_HP_MUTE_LED_MIC2),
--
2.1.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1484334
Title:
Fix the white noise on Dell laptop
Status in linux package in Ubuntu:
Confirmed
Bug description:
Dell laptop causes the white noise by login screen and headphone,
and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this
noise.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484334/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484334] [NEW] Fix the white noise on Dell laptop
Public bug reported: Dell laptop causes the white noise by login screen and headphone, and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this noise. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Woodrow Shen (woodrow-shen) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New = Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Woodrow Shen (woodrow-shen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484334 Title: Fix the white noise on Dell laptop Status in linux package in Ubuntu: Confirmed Bug description: Dell laptop causes the white noise by login screen and headphone, and the fixup function ALC292_FIXUP_DISABLE_AAMIX can eliminate this noise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481575] Re: Fix Dell laptop to internal mic/headset mic
** Changed in: linux (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1481575 Title: Fix Dell laptop to internal mic/headset mic Status in linux package in Ubuntu: In Progress Bug description: This bug is for tracking purposes. Please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481575] Re: Fix Dell laptop to internal mic/headset mic
** Changed in: linux (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1481575 Title: Fix Dell laptop to internal mic/headset mic Status in linux package in Ubuntu: Fix Committed Bug description: This bug is for tracking purposes. Please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481575] [NEW] Fix Dell laptop to internal mic/headset mic
Public bug reported: This bug is for tracking purposes. Please do not triage. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Woodrow Shen (woodrow-shen) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New = Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Woodrow Shen (woodrow-shen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1481575 Title: Fix Dell laptop to internal mic/headset mic Status in linux package in Ubuntu: Confirmed Bug description: This bug is for tracking purposes. Please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481575] [alsa-devel][PATCH] ALSA: hda - Fix Dell laptop for internal mic/headset mic
From: Woodrow Shen woodrow.s...@canonical.com
The new Dell laptop with ALC3266 can't use internal microphone to
record. Also, the 3 ring headset mic doesn't work on it. For src of
patch_realtek.c, only the pin cfg of Nid 0x17 is different, so the
Nid 0x17 is added into pin quirk, and others are defined to macro
ALC298_STANDARD_PINS in common use.
Codec: Realtek ALC3266
Vendor Id: 0x10ec0298
Subsystem Id: 0x102806e5
BugLink: https://bugs.launchpad.net/bugs/1481575
Signed-off-by: Woodrow Shen woodrow.s...@canonical.com
---
sound/pci/hda/patch_realtek.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index b20f104..294ba67 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5401,6 +5401,10 @@ static const struct hda_model_fixup
alc269_fixup_models[] = {
{0x14, 0x90170110}, \
{0x15, 0x0221401f}
+#define ALC298_STANDARD_PINS \
+ {0x12, 0x90a60130}, \
+ {0x21, 0x03211020}
+
static const struct snd_hda_pin_quirk alc269_pin_fixup_tbl[] = {
SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, Dell,
ALC255_FIXUP_DELL2_MIC_NO_PRESENCE,
{0x14, 0x90170110},
@@ -5570,9 +5574,11 @@ static const struct snd_hda_pin_quirk
alc269_pin_fixup_tbl[] = {
ALC292_STANDARD_PINS,
{0x13, 0x90a60140}),
SND_HDA_PIN_QUIRK(0x10ec0298, 0x1028, Dell,
ALC298_FIXUP_DELL1_MIC_NO_PRESENCE,
- {0x12, 0x90a60130},
- {0x17, 0x90170140},
- {0x21, 0x03211020}),
+ ALC298_STANDARD_PINS,
+ {0x17, 0x90170140}),
+ SND_HDA_PIN_QUIRK(0x10ec0298, 0x1028, Dell,
ALC298_FIXUP_DELL1_MIC_NO_PRESENCE,
+ ALC298_STANDARD_PINS,
+ {0x17, 0x90170110}),
{}
};
--
2.1.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1481575
Title:
Fix Dell laptop to internal mic/headset mic
Status in linux package in Ubuntu:
Confirmed
Bug description:
This bug is for tracking purposes. Please do not triage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481575/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1478497] [alsa-devel][PATCH] ALSA: hda - Add pin quirk for the headset mic jack detection on Dell laptop
From: Woodrow Shen woodrow.s...@canonical.com
The new Dell laptop with codec 256 can't detect headset mic when headset was
inserted on the machine. From alsa-info, we check init_pin_configs and need to
define the new register value for pin 0x1d 0x1e because the original macro
ALC256_STANDARD_PINS can't match pin definition. Also, the macro
ALC256_STANDARD_PINS
is simplified by removing them. This makes headset mic works on laptop.
Codec: Realtek ALC256
Vendor Id: 0x10ec0256
Subsystem Id: 0x102806f2
BugLink: https://bugs.launchpad.net/bugs/1478497
Signed-off-by: Woodrow Shen woodrow.s...@canonical.com
---
sound/pci/hda/patch_realtek.c | 15 +++
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index d94c0e3..4ae877c 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5398,8 +5398,6 @@ static const struct hda_model_fixup alc269_fixup_models[]
= {
{0x19, 0x41f0}, \
{0x1a, 0x41f0}, \
{0x1b, 0x41f0}, \
- {0x1d, 0x4071}, \
- {0x1e, 0x41f0}, \
{0x21, 0x02211020}
#define ALC282_STANDARD_PINS \
@@ -5556,10 +5554,19 @@ static const struct snd_hda_pin_quirk
alc269_pin_fixup_tbl[] = {
{0x21, 0x02211030}),
SND_HDA_PIN_QUIRK(0x10ec0256, 0x1028, Dell,
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC256_STANDARD_PINS,
- {0x13, 0x4000}),
+ {0x13, 0x4000},
+ {0x1d, 0x4071},
+ {0x1e, 0x41f0}),
SND_HDA_PIN_QUIRK(0x10ec0256, 0x1028, Dell,
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
ALC256_STANDARD_PINS,
- {0x13, 0x41f0}),
+ {0x13, 0x41f0},
+ {0x1d, 0x4071},
+ {0x1e, 0x41f0}),
+ SND_HDA_PIN_QUIRK(0x10ec0256, 0x1028, Dell,
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
+ ALC256_STANDARD_PINS,
+ {0x13, 0x41f0},
+ {0x1d, 0x4077992d},
+ {0x1e, 0x41ff}),
SND_HDA_PIN_QUIRK(0x10ec0280, 0x103c, HP, ALC280_FIXUP_HP_GPIO4,
{0x12, 0x90a60130},
{0x13, 0x4000},
--
2.1.4
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1478497
Title:
Headset mic support for a Dell laptop machine
Status in linux package in Ubuntu:
In Progress
Bug description:
When the headset was plugged in the Dell laptop, the mic of headset
can't be detected and workable.
Codec: Realtek ALC256
Vendor Id: 0x10ec0256
Subsystem Id: 0x102806f2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478497/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1478497] Re: Headset mic support for a Dell laptop machine
** Changed in: linux (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1478497 Title: Headset mic support for a Dell laptop machine Status in linux package in Ubuntu: Fix Committed Bug description: When the headset was plugged in the Dell laptop, the mic of headset can't be detected and workable. Codec: Realtek ALC256 Vendor Id: 0x10ec0256 Subsystem Id: 0x102806f2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1478497] [NEW] Headset mic support for a Dell laptop machine
Public bug reported: When the headset was plugged in the Dell laptop, the mic of headset can't be detected and workable. Codec: Realtek ALC256 Vendor Id: 0x10ec0256 Subsystem Id: 0x102806f2 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Woodrow Shen (woodrow-shen) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New = Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Woodrow Shen (woodrow-shen) ** Description changed: - The bug + When the headset was plugged in the Dell laptop, the mic of headset + can't be detected and workable. + + Codec: Realtek ALC256 + Vendor Id: 0x10ec0256 + Subsystem Id: 0x102806f2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1478497 Title: Headset mic support for a Dell laptop machine Status in linux package in Ubuntu: Confirmed Bug description: When the headset was plugged in the Dell laptop, the mic of headset can't be detected and workable. Codec: Realtek ALC256 Vendor Id: 0x10ec0256 Subsystem Id: 0x102806f2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1477900] Re: Headset mic support for a Dell desktop machine
** Changed in: hwe-next Status: New = Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1477900 Title: Headset mic support for a Dell desktop machine Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: When the headset was plugged in the Dell desktop, the mic of headset can't be detected and workable. Codec: Realtek ALC3234 Vendor Id: 0x10ec0255 Subsystem Id: 0x102806bb To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1477900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1477900] [NEW] Headset mic support for a Dell desktop machine
Public bug reported: When the headset was plugged in the Dell desktop, the mic of headset can't be detected and workable. Codec: Realtek ALC3234 Vendor Id: 0x10ec0255 Subsystem Id: 0x102806bb ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Woodrow Shen (woodrow-shen) Status: Confirmed ** Description changed: - The issue is for tracking only. + This bug is used for tracking only, please do not triage. ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Woodrow Shen (woodrow-shen) ** Changed in: linux (Ubuntu) Status: New = Confirmed ** Description changed: - This bug is used for tracking only, please do not triage. + When the headset was plugged in the Dell desktop, the mic of headset + can't be detected and workable. + + Codec: Realtek ALC3234 + AFG Function Id: 0x1 (unsol 1) + Vendor Id: 0x10ec0255 + Subsystem Id: 0x102806bb ** Description changed: When the headset was plugged in the Dell desktop, the mic of headset can't be detected and workable. Codec: Realtek ALC3234 - AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0255 Subsystem Id: 0x102806bb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1477900 Title: Headset mic support for a Dell desktop machine Status in linux package in Ubuntu: Confirmed Bug description: When the headset was plugged in the Dell desktop, the mic of headset can't be detected and workable. Codec: Realtek ALC3234 Vendor Id: 0x10ec0255 Subsystem Id: 0x102806bb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1477900] [alsa-devel] [PATCH v2] ALSA: hda - Fix the headset mic that will not work on Dell desktop machine
From: Woodrow Shen woodrow.s...@canonical.com
When the headset was plugged in the Dell desktop, the mic of headset can't be
detected and workable.
According to the alsa-info, we found the differece between alsa and
init_pin_configs
on the machine, so we need to add the pin configs to make headset work.
Codec: Realtek ALC3234
Vendor Id: 0x10ec0255
Subsystem Id: 0x102806bb
BugLink: https://bugs.launchpad.net/bugs/1477900
Signed-off-by: Woodrow Shen woodrow.s...@canonical.com
---
sound/pci/hda/patch_realtek.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 742fc62..d94c0e3 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5473,6 +5473,28 @@ static const struct snd_hda_pin_quirk
alc269_pin_fixup_tbl[] = {
{0x1e, 0x41f0},
{0x21, 0x0221103f}),
SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, Dell,
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
+ {0x12, 0x4000},
+ {0x14, 0x90170150},
+ {0x17, 0x41f0},
+ {0x18, 0x41f0},
+ {0x19, 0x41f0},
+ {0x1a, 0x41f0},
+ {0x1b, 0x02011020},
+ {0x1d, 0x4054c029},
+ {0x1e, 0x41f0},
+ {0x21, 0x0221105f}),
+ SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, Dell,
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
+ {0x12, 0x4000},
+ {0x14, 0x90170110},
+ {0x17, 0x41f0},
+ {0x18, 0x41f0},
+ {0x19, 0x41f0},
+ {0x1a, 0x41f0},
+ {0x1b, 0x01014020},
+ {0x1d, 0x4054c029},
+ {0x1e, 0x41f0},
+ {0x21, 0x0221101f}),
+ SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, Dell,
ALC255_FIXUP_DELL1_MIC_NO_PRESENCE,
{0x12, 0x90a60160},
{0x14, 0x90170120},
{0x17, 0x90170140},
--
2.1.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1477900
Title:
Headset mic support for a Dell desktop machine
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
When the headset was plugged in the Dell desktop, the mic of headset
can't be detected and workable.
Codec: Realtek ALC3234
Vendor Id: 0x10ec0255
Subsystem Id: 0x102806bb
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1477900/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
