[Kernel-packages] [Bug 2000465] Re: rt715-sdca codec cannot record audio with internal microphone
Upload debdiff for Kinetic ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000465/+attachment/5638039/+files/alsa-ucm-conf_1.2.6.3-1ubuntu3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000465 Title: rt715-sdca codec cannot record audio with internal microphone Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] rt715-sdca codec cannot record audio with internal microphone [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Internal microphone should work propoerly. [Where problems could occur] Only fix for DUT with rt715-sdca device [Other Info] Upstream bug: https://github.com/alsa-project/alsa-ucm-conf/issues/255 Fix: https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998168] Re: System went crash during Ubuntu 20.04.5 installation
I have tried configure a network which can access internet(like:www.baidu.com)
and ubuntu 20.04.5 can be installed successful in my new environment.
So could you help to point out the root cause of this defect shown in sos
report 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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in subiquity:
New
Status in linux package in Ubuntu:
Invalid
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1998168/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882968] Re: ath10k_pci failed to wake target for write32
@kaihengfeng I try to use only the most vanilla setup, so yes, it has happened with all the mainline Ubuntu kernels coming from 20 LTS upgrades over the last year and also 22.10. Suspend is disabled, I guess by kernel parameter `pcie_aspm=off`, by `HandleLidSwitch=ignore` in `/etc/systemd/logind.conf`, and by the fact that I'm using a tiling window manager without any screen timeout. When suspend was enabled with Gnome, the issue did NOT specially affect waking from suspend. It seems to arise randomly. Occasionally the crash is quite hard and freezes the system for 30 seconds. I believe this scenario is when even a reboot is not enough - the card "fails to wake" even on boot. Only a second reboot will fix it (see #18 above for dmesg). Crazy. It's probably unrelated, but here's some dmesg output from very early in boot: [0.040179] Kernel command line: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro text pcie_aspm=off pcie_port_pm=off [0.040374] PCIe ASPM is disabled [0.040432] Unknown kernel command line parameters "text BOOT_IMAGE=/vmlinuz-5.15.0-56-generic", will be passed to user space. Is this last line expected? More generally, how would I exclude the possibility of hardware failure? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882968 Title: ath10k_pci failed to wake target for write32 Status in linux package in Ubuntu: Expired Bug description: Wifi card stopped working. I use Lubuntu 20.04. Wifi card info: *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:3a:00.0 logical name: wlp58s0 version: 32 serial: 9c:b6:d0:d4:9b:33 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:135 memory:dc00-dc1f Releveant journal log attached. In brief, Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to receive control response completion, polling.. Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to wake target for write32 of 0x0001 at 0x00034430: -110 ... Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110) Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110 Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (29 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal Uname: Linux 5.6.11-050611-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee
Thank you, Chris! I have reached this far with this thread thanks to the #Ubuntu channel on irc.libera.chat - I got lots of help from them. Further to my bug report, I wanted to add the below: 1) I tried nomodeset GRUB option, booting once; the result was, if the system (graphical desktop interface) faded to black screen due to no activity, the screen was black, however, I could still see a slight illumination, meaning not pitch black. In this state, I was able to easily and quickly log back in to the desktop environment. HOWEVER, if I issued the "systemctl suspend" command, the system went into sleep and there was no return. I had to do a hard reset (press power button for 5 seconds to shut the system off and then just restart it). 2) I also tried to adjust settings in the graphical desktop environment, and if I set the Screen Blank to never and Dim Screen to off, the system would not fade the screen, due to inactivity and so, it would keep on running smooth - only tested it for a little while as it is a fresh install, on a new posession -> Dell Latitude 7390. 3) Hardware info: a) CPU: Intel 8th Gen i7-8650U CPU @ 1.90GHz 64-bit b) Graphics card: Intel UHD Graphics 620 (rev 07), lshd says the driver is i915 (when nomodeset WAS NOT ADDED AT BOOT TIME) Looking forward to comments and requests! Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2000491 Title: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non- recoverable after screen lock and screen completely fades to black or after system goes into sleep Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390. The system is non-recoverable after it goes into sleep. Or after the screen is locked by the user and after it fades to complete black. System becomes unresponsive, no mouse or keypress will get the system back on to work. If the systemctl suspend is issued, the system will not wake up again. Hard reset is needed. If Ubuntu 18.04.6 is booted from live USB, the same is happening. Sometimes, when the system is rendered unresponsive as a result of any of the above, the power led is sending the message of "processor failure" (2 x amber blinks followed by 1 x white blink). Any help is greatly appreciated! I will keep the system as is, without applying any updates for now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 27 01:13:12 2022 InstallationDate: Installed on 2022-12-26 (0 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/2000491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
