[Kernel-packages] [Bug 2044592] [NEW] installed system + new install refuse to show GUI (Lubuntu & Xubuntu noble)
Public bug reported:
A couple of days ago I suffered a brownout, causing my noble install to
shutdown (uncleanly) on this box
- hp prodesk 600 g3 sff (i5-7500, 8gb, nvidia geforce gt710 (gk208b) + intel
graphics 630)
On power restore, the system would not allow GUI login, I noted an Xorg
crash in the /var/crash/ directory; but I was unable to ubuntu-bug file
it (out of date packages; though I `apt update; apt full-upgrade` and
nothing changed).
I've attempted a re-install today, and after install the system boots, I
get to see the plymouth screen (xubuntu) then blank screen and cursor
top left.
If I switch to text terminal; I can login and see screen for a few
seconds; before the flashing cursor returns (ie. I'm taken away from
ctrl+alt+f4 terminal and to lightdm trying to restart I suspect).
This is the same behavior I had before this install; ie. I believe the
issue is related to a recent package upgrade (this box is only rebooted
about fornightly; so the power outage was the first reboot in maybe ten
days).
My original install was Lubuntu noble (actually a mantic ISO; as noble
ISOs hadn't started then, but using an updated calamares for noble
installed that tsimonq2 requested I test, that upgraded calamares caused
the installed system to use noble sources & become noble not mantic)
I'm convinced this is a regression due to upgrade; but it also occurs on
recent ISOs too; I also suspect it maybe related to graphic gpus (intel
& nvidia)
FYI: There is a Xorg crash file in /var/crash/ on this box too, it
likewise won't let me `ubuntu-bug` install it, again reporting out of
date packages (libsepol2)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: guiverc1015 F wireplumber
/dev/snd/controlC1: guiverc1015 F wireplumber
/dev/snd/seq:guiverc1012 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Nov 25 18:05:14 2023
InstallationDate: Installed on 2023-11-25 (0 days ago)
InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231125)
IwConfig:
lono wireless extensions.
eno1 no wireless extensions.
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
Bus 001 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_AU.UTF-8
LANGUAGE=en_AU:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1aef793d-b806-4b39-9b05-baea27c51b5e ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.2
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/30/2018
dmi.bios.release: 2.15
dmi.bios.vendor: HP
dmi.bios.version: P07 Ver. 02.15
dmi.board.name: 82B4
dmi.board.vendor: HP
dmi.board.version: KBC Version 06.21
dmi.chassis.asset.tag: AUD8130DCW
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 6.33
dmi.modalias:
dmi:bvnHP:bvrP07Ver.02.15:bd01/30/2018:br2.15:efr6.33:svnHP:pnHPProDesk600G3SFF:pvr:rvnHP:rn82B4:rvrKBCVersion06.21:cvnHP:ct3:cvr:sku1MF39PA#ABG:
dmi.product.family: 103C_53307F HP ProDesk
dmi.product.name: HP ProDesk 600 G3 SFF
dmi.product.sku: 1MF39PA#ABG
dmi.sys.vendor: HP
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
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/2044592
Title:
installed system + new install refuse to show GUI (Lubuntu & Xubuntu
noble)
Status in linux package in Ubuntu:
New
Bug description:
A couple of days ago I suffered a brownout, causing my noble install to
shutdown (uncleanly) on this box
- hp prodesk 600 g3 sff (i5-7500, 8gb, nvidia geforce gt710 (gk208b) + intel
graphics 630)
On power restore, the system would not allow GUI login, I noted an
Xorg crash in the /var/crash/ directory; but I was unable to ubuntu-
bug file it (out of date packages; though I `apt update; apt full-
upgrade` and nothing changed).
I've attempted a re-install today, and after install the system boots,
I get to see the plymouth screen (xubuntu) then blank screen and
cursor top left.
[Kernel-packages] [Bug 2044589] [NEW] [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes
Public bug reported: This request is to add support for SAS5116 controller and few critical bug-fixes in Ubuntu 24.04 LTS. Below is the list of upstream commits that adds support for SAS5116: b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2044589 Title: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes Status in linux package in Ubuntu: New Bug description: This request is to add support for SAS5116 controller and few critical bug-fixes in Ubuntu 24.04 LTS. Below is the list of upstream commits that adds support for SAS5116: b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044589/+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 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
I'd really recommend not open new bug tasks for further source packages on a bug like this; we clearly aren't going to remove any of those other packages from mantic now... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/6.5.0.1008.9)
All autopkgtests for the newly accepted linux-meta-raspi (6.5.0.1008.9) for mantic have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/unknown (arm64) adv-17v35x/unknown (arm64) backport-iwlwifi-dkms/unknown (arm64) bbswitch/unknown (arm64) dahdi-linux/unknown (arm64) ddcci-driver-linux/unknown (arm64) digimend-dkms/unknown (arm64) dm-writeboost/unknown (arm64) dpdk-kmods/unknown (arm64) evdi/unknown (arm64) falcosecurity-libs/unknown (arm64) fwts/unknown (arm64) glibc/unknown (arm64) gost-crypto/unknown (arm64) iptables-netflow/unknown (arm64) jool/unknown (arm64) langford/unknown (arm64) librem-ec-acpi/unknown (arm64) libvpoll-eventfd/unknown (arm64) lime-forensics/unknown (arm64) linux-apfs-rw/unknown (arm64) lttng-modules/unknown (arm64) lxc/unknown (arm64) nat-rtsp/unknown (arm64) openafs/unknown (arm64) openrazer/unknown (arm64) openvpn-dco-dkms/unknown (arm64) r8125/unknown (arm64) r8168/unknown (arm64) rapiddisk/unknown (arm64) rtl8812au/unknown (arm64) rtpengine/unknown (arm64) snapd/unknown (arm64) systemd/unknown (arm64) v4l2loopback/unknown (arm64) west-chamber/unknown (arm64) xilinx-runtime/unknown (arm64) xtables-addons/unknown (arm64) xtrx-dkms/unknown (arm64) zfs-linux/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-laptop/6.5.0.1007.10)
All autopkgtests for the newly accepted linux-meta-laptop (6.5.0.1007.10) for mantic have finished running. The following regressions have been reported in tests triggered by the package: systemd/253.5-1ubuntu6.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta-laptop [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039144] Autopkgtest regression report (linux-meta-laptop/6.5.0.1007.10)
All autopkgtests for the newly accepted linux-meta-laptop (6.5.0.1007.10) for mantic have finished running. The following regressions have been reported in tests triggered by the package: systemd/253.5-1ubuntu6.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta-laptop [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-laptop in Ubuntu. https://bugs.launchpad.net/bugs/2039144 Title: [X13s] Set unique wifi mac address Status in ubuntu-concept: Invalid Status in linux-meta-laptop package in Ubuntu: Fix Committed Bug description: Currently, the wifi NIC comes up with a random MAC address which causes issues in some environments (routers sending out 'new device added' messages after every reboot). Instead, set a unique MAC address at boot and let network manager handle MAC randomization if that is desired. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-concept/+bug/2039144/+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 2041000] Autopkgtest regression report (linux-meta-laptop/6.5.0.1007.10)
All autopkgtests for the newly accepted linux-meta-laptop (6.5.0.1007.10) for mantic have finished running. The following regressions have been reported in tests triggered by the package: systemd/253.5-1ubuntu6.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta-laptop [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-laptop in Ubuntu. https://bugs.launchpad.net/bugs/2041000 Title: [X13s] Bluetooth not enabled Status in ubuntu-concept: Invalid Status in linux-meta-laptop package in Ubuntu: Invalid Status in linux-meta-laptop source package in Mantic: Fix Committed Bug description: [Summary] Bluetooth cannot be turned. [Steps to reproduce] 1. Go to `Settings` > `Bluetooth` 2. Turn it on [Expected result] Turn on successfully. [Actual result] Cannot be turned on. [Failure rate] 5/5 [Additional information] CID: 202308-31941 SKU: Lenovo X13s Gen 1 system-manufacturer: LENOVO system-product-name: 21BYZ9SNUS bios-version: N3HET86W (1.58 ) CPU: GPU: kernel-version: 6.5.0-1004-laptop [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-concept/+bug/2041000/+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 2037534] Autopkgtest regression report (linux-meta-laptop/6.5.0.1007.10)
All autopkgtests for the newly accepted linux-meta-laptop (6.5.0.1007.10) for mantic have finished running. The following regressions have been reported in tests triggered by the package: systemd/253.5-1ubuntu6.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta-laptop [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-laptop in Ubuntu. https://bugs.launchpad.net/bugs/2037534 Title: [X13s] Set unique bluetooth mac address Status in linux-meta-laptop package in Ubuntu: Invalid Status in linux-meta-laptop source package in Mantic: Fix Committed Bug description: On windows side MAC address for WLAN and Bluetooth are similar - like off by 4 from each other. I am guessing that a range of MACs is used per device (i.e. sequentially for wlan, sim cards, bluetooth). On linux side we do not currently have ability to find out the expected device MAC. Currently setting to static one is ok, but will not work when all of us are in Riga with all of our X13s devices. [Unit] Description=Set Bluetooth Address After=bluetooth.target Requires=bluetooth.target [Service] Type=simple ExecStartPre=/usr/bin/sleep 5 ExecStart=/bin/bash -c "/usr/bin/yes | /usr/bin/btmgmt public-addr AD:5A:00:F0:FD:8C" [Install] WantedBy=multi-user.target Imho this should be impoved as follows: 1) make this wantedby individual bluetooth device, not bluetooth.target 2) make it bind to bluetooth device, such that it is stopped/started upon device poweroff/poweron (need to check if needed to set address every time) 3) make it conditional on btmgmt to be available 4) set or derive MAC from /etc/machine-id (maybe systemd should be able to do this for us?) 5) use btmgmt --timeout option for interactive use 6) Hopefully above will mean there is no need to do sleep 5 either To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-laptop/+bug/2037534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-riscv/6.5.0.14.14.1)
All autopkgtests for the newly accepted linux-meta-riscv (6.5.0.14.14.1) for mantic have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/unknown (amd64) casper/unknown (amd64) cryptsetup/unknown (ppc64el, s390x) ipmitool/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta-riscv [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878279]
(In reply to radupantiru from comment #21) Thanks very much for testing this! The dmesg shows what I expected: PCI: [Firmware Info]: ECAM at [mem 0xf800-0xfbff] not reserved in ACPI motherboard resources PCI: ECAM at [mem 0xf800-0xfbff] reserved as EfiMemoryMappedIO PCI: ECAM [mem 0xf800-0xfbff] reserved to work around lack of ACPI motherboard _CRS Just to double-check, I think you were seeing a touchpad issue, right? And I assume that problem is fixed by this patch? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1878279]
Created attachment 305467 attachment-26413-0.html It was indeed the touchpad which failed to work at random intervals. It will be quite obvious if it fails again and my question is if the patch will make its way into the future kernels as I will have not to upgrade my OS in order to monitor the fix. Thanks, Radu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 2043733] Re: HP Zbook 17 G6 internal microphone causes hard crashes
Hi Team, Sorry for the delay, I forgot to mark myself as Out of Office for yesterday. The customer got back to me on this and indicated that there is no sensitive or secret information contained in the bug report as is, so it can be made public. Apologies for any sort of confusion this caused. On Thu, Nov 23, 2023 at 9:50 AM Marc Deslauriers <2043...@bugs.launchpad.net> wrote: > Can I make this bug public so that the appropriate developers can see > it? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2043733 > > Title: > HP Zbook 17 G6 internal microphone causes hard crashes > > Status in linux package in Ubuntu: > New > > Bug description: > Anything that changes the state of the internal microphone on the HP > Zbook 17 G6 can result in a hard crash of the entire system. This > includes things like noise reduction being applied by Google Meets, > but it can be reliably replicated by just changing the volume of the > microphone until the system crashes. When the crashes occur, the logs > cut off just as they would if the system's power were completely cut. > > This behavior only occurs with the internal microphone. External > microphones (both 3.5 mm TRRS and USB microphones) do not exhibit this > same behavior. > > This behavior has been tested on 20.04, 22.04, 23.04, and 23.10 and > reliably occurs on kernels 5.4, 5.15, 6.2, and 6.5. > > This is the system device that should be responsible for handling the > internal microphone. > > description: Multimedia audio controller >product: Cannon Lake PCH cAVS >vendor: Intel Corporation >physical id: 1f.3 >bus info: pci@:00:1f.3 >logical name: card0 >logical name: /dev/snd/controlC0 >logical name: /dev/snd/hwC0D0 >logical name: /dev/snd/hwC0D2 >logical name: /dev/snd/pcmC0D0c >logical name: /dev/snd/pcmC0D0p >logical name: /dev/snd/pcmC0D31p >logical name: /dev/snd/pcmC0D3p >logical name: /dev/snd/pcmC0D4p >logical name: /dev/snd/pcmC0D5p >logical name: /dev/snd/pcmC0D6c >logical name: /dev/snd/pcmC0D7c >version: 10 >width: 64 bits >clock: 33MHz >capabilities: pm msi bus_master cap_list >configuration: driver=sof-audio-pci-intel-cnl latency=64 >resources: iomemory:400-3ff iomemory:400-3ff irq:191 > memory:404a108000-404a10bfff memory:404a00-404a0f > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043733/+subscriptions > > ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043733 Title: HP Zbook 17 G6 internal microphone causes hard crashes Status in linux package in Ubuntu: New Bug description: Anything that changes the state of the internal microphone on the HP Zbook 17 G6 can result in a hard crash of the entire system. This includes things like noise reduction being applied by Google Meets, but it can be reliably replicated by just changing the volume of the microphone until the system crashes. When the crashes occur, the logs cut off just as they would if the system's power were completely cut. This behavior only occurs with the internal microphone. External microphones (both 3.5 mm TRRS and USB microphones) do not exhibit this same behavior. This behavior has been tested on 20.04, 22.04, 23.04, and 23.10 and reliably occurs on kernels 5.4, 5.15, 6.2, and 6.5. This is the system device that should be responsible for handling the internal microphone. description: Multimedia audio controller product: Cannon Lake PCH cAVS vendor: Intel Corporation physical id: 1f.3 bus info: pci@:00:1f.3 logical name: card0 logical name: /dev/snd/controlC0 logical name: /dev/snd/hwC0D0 logical name: /dev/snd/hwC0D2 logical name: /dev/snd/pcmC0D0c logical name: /dev/snd/pcmC0D0p logical name: /dev/snd/pcmC0D31p logical name: /dev/snd/pcmC0D3p logical name: /dev/snd/pcmC0D4p logical name: /dev/snd/pcmC0D5p logical name: /dev/snd/pcmC0D6c logical name: /dev/snd/pcmC0D7c version: 10 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=sof-audio-pci-intel-cnl latency=64 resources: iomemory:4
[Kernel-packages] [Bug 2043733] Re: HP Zbook 17 G6 internal microphone causes hard crashes
Confirmed there is no sensitive data included and set to public. Apologies for any confusion. -- 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/2043733 Title: HP Zbook 17 G6 internal microphone causes hard crashes Status in linux package in Ubuntu: New Bug description: Anything that changes the state of the internal microphone on the HP Zbook 17 G6 can result in a hard crash of the entire system. This includes things like noise reduction being applied by Google Meets, but it can be reliably replicated by just changing the volume of the microphone until the system crashes. When the crashes occur, the logs cut off just as they would if the system's power were completely cut. This behavior only occurs with the internal microphone. External microphones (both 3.5 mm TRRS and USB microphones) do not exhibit this same behavior. This behavior has been tested on 20.04, 22.04, 23.04, and 23.10 and reliably occurs on kernels 5.4, 5.15, 6.2, and 6.5. This is the system device that should be responsible for handling the internal microphone. description: Multimedia audio controller product: Cannon Lake PCH cAVS vendor: Intel Corporation physical id: 1f.3 bus info: pci@:00:1f.3 logical name: card0 logical name: /dev/snd/controlC0 logical name: /dev/snd/hwC0D0 logical name: /dev/snd/hwC0D2 logical name: /dev/snd/pcmC0D0c logical name: /dev/snd/pcmC0D0p logical name: /dev/snd/pcmC0D31p logical name: /dev/snd/pcmC0D3p logical name: /dev/snd/pcmC0D4p logical name: /dev/snd/pcmC0D5p logical name: /dev/snd/pcmC0D6c logical name: /dev/snd/pcmC0D7c version: 10 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=sof-audio-pci-intel-cnl latency=64 resources: iomemory:400-3ff iomemory:400-3ff irq:191 memory:404a108000-404a10bfff memory:404a00-404a0f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043733/+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 2044573] [NEW] Unable to upgrade from Ubuntu 22.o4 to Ubuntu 23.04
Public bug reported: Trying to upgrade Ubuntu to version 23.04 and I keep facing this issue. Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 24 16:55:54 2023 InstallationDate: Installed on 2023-11-23 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2023-11-24 (0 days ago) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2044573 Title: Unable to upgrade from Ubuntu 22.o4 to Ubuntu 23.04 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Trying to upgrade Ubuntu to version 23.04 and I keep facing this issue. Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist- upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 24 16:55:54 2023 InstallationDate: Installed on 2023-11-23 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2023-11-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2044573/+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 2044027] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723199/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-
[Kernel-packages] [Bug 2044027] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723200/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-g
[Kernel-packages] [Bug 2044027] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723196/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89
[Kernel-packages] [Bug 2044027] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723198/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-generi
[Kernel-packages] [Bug 2044027] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723197/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-generi
[Kernel-packages] [Bug 2044027] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723195/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.
[Kernel-packages] [Bug 2044027] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723194/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules
[Kernel-packages] [Bug 2044027] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723192/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.
[Kernel-packages] [Bug 2044027] PaInfo.txt
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723191/+files/PaInfo.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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-generi
[Kernel-packages] [Bug 2044027] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723193/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports
[Kernel-packages] [Bug 2044027] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723190/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-gen
[Kernel-packages] [Bug 2044027] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723187/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-g
[Kernel-packages] [Bug 2044027] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723189/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-gen
[Kernel-packages] [Bug 2044027] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723188/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-generic
[Kernel-packages] [Bug 2044027] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723186/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-generic
[Kernel-packages] [Bug 2044027] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723185/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-g
[Kernel-packages] [Bug 2044027] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723184/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.1
[Kernel-packages] [Bug 2044027] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723183/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-generic N
[Kernel-packages] [Bug 2044027] AlsaInfo.txt
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2044027/+attachment/5723182/+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/2044027
Title:
[Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
rebooting on ubuntu os only
Status in linux package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
the following video can prove my problem on ubuntu
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 843 F pulseaudio
/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
/dev/snd/controlC0: oem 843 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2023-11-20 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-30-generic N/A
linux-backports-modules-5.13.0-30-generic N/A
linux-firmware 1.187.39
Tags: focal
Uname: Linux 5.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/06/2012
dmi.bios.release: 6.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Pumori
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.60
dmi.modalias:
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855D-11X
dmi.product.sku: PSKCYE-009002N5
dmi.product.version: PSKCYE-009002N5
dmi.sys.vendor: TOSHIBA
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem 879 F pulseaudio
/dev/snd/controlC0: oem 879 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: TOSHIBA SATELLITE C855D-11X
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 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
RelatedPackageVersions:
linux-restricted-modules-5.15.0-89-generic N/A
linux-backports-modules-5.15.0-89-g
Re: [Kernel-packages] [Bug 2044027] Re: [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after rebooting on ubuntu os only
the same problem even if i upgraqded to ubuntu 22.04
Note that 1login can the keyboard internal and mouse internal can work and
restarts normally T 1 TIME
and the other time it is not ,
if i upgtraded to ubuntu 24.04 the same remains
fix this problem
On Thu, 23 Nov 2023 at 05:40, Daniel van Vugt <2044...@bugs.launchpad.net>
wrote:
> Since this is probably a kernel issue and you can't officially increase
> the kernel version any further on this older Ubuntu release, I suggest
> trying a newer Ubuntu release like 22.04.3:
>
> https://ubuntu.com/download/desktop
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2044027
>
> Title:
> [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
> rebooting on ubuntu os only
>
> Status in linux package in Ubuntu:
> New
>
> Bug description:
> For input devices : gnome-shell
>For rebooting process : init system
> the following is what appears on my screen when i login to gnome-shell
> desktop environment (ubuntu-desktop) the below message appears twice times
> ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous
> error (AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
> ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is
> beyond end of object (length 0xA) (20210331/exoparg2-393)
> __common_interrupt: 1.55 No irq handler for vector")
> At the start process : both keyboard and mouse internal doesnot work
> with the issue above , at the end when performing a reboot process after
> rebooting my device it appears on my screen a black screen resulting to
> turning off from the btn on my laptop. always this incident happens with
> me and only on ubuntu 16.04 and later systems the problem occurs while on
> other oses the problem does not occur any more (rebooting keyboard and
> mouse "internal")
>
> note : secondary storage ,optical disks external devices like keyboard
> are working fine on ubuntu systems with all versions and all other os
> including windows os
> the following video can prove my problem on ubuntu
> ---
> ProblemType: Bug
> ApportVersion: 2.20.11-0ubuntu27.27
> Architecture: amd64
> AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1: oem 843 F pulseaudio
>/dev/snd/pcmC1D0c: oem 843 F...m pulseaudio
>/dev/snd/pcmC1D0p: oem 843 F...m pulseaudio
>/dev/snd/controlC0: oem 843 F pulseaudio
> CasperMD5CheckResult: skip
> DistroRelease: Ubuntu 20.04
> InstallationDate: Installed on 2023-11-20 (0 days ago)
> InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64
> (20220223)
> MachineType: TOSHIBA SATELLITE C855D-11X
> Package: linux (not installed)
> ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
> root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
> PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
> RelatedPackageVersions:
>linux-restricted-modules-5.13.0-30-generic N/A
>linux-backports-modules-5.13.0-30-generic N/A
>linux-firmware 1.187.39
> Tags: focal
> Uname: Linux 5.13.0-30-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: N/A
> _MarkForUpload: True
> dmi.bios.date: 12/06/2012
> dmi.bios.release: 6.30
> dmi.bios.vendor: Insyde Corp.
> dmi.bios.version: 6.30
> dmi.board.asset.tag: Base Board Asset Tag
> dmi.board.name: Pumori
> dmi.board.vendor: AMD
> dmi.board.version: Base Board Version
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: OEM Chassis Manufacturer
> dmi.chassis.version: OEM Chassis Version
> dmi.ec.firmware.release: 1.60
> dmi.modalias:
> dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
> dmi.product.family: Type1Family
> dmi.product.name: SATELLITE C855D-11X
> dmi.product.sku: PSKCYE-009002N5
> dmi.product.version: PSKCYE-009002N5
> dmi.sys.vendor: TOSHIBA
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044027/+subscriptions
>
>
** Tags added: jammy wayland-session
** Description changed:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._B
[Kernel-packages] [Bug 1984203] Re: /var/run/reboot-required not created after installing new kernel
Installing update-notifier-common seems to solve the problem. -- 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/1984203 Title: /var/run/reboot-required not created after installing new kernel Status in linux package in Ubuntu: Confirmed Bug description: I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of them, this resulted in /var/run/reboot-required and /var/run/reboot- required.pkgs being created: jik@jik-x1:~$ ls -l /var/run/reboot-required* -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs jik@jik-x1:~$ cat /var/run/reboot-required.pkgs linux-image-5.15.0-46-generic linux-base jik@jik-x1:~$ On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to create this issue) the same kernel package was installed during the `apt-get dist-upgrade -y` run, but /var/run/reboot-required and /var/run/reboot-required.pkgs were NOT created. This seems... problematic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dpkg 1.21.1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 10 10:17:55 2022 InstallationDate: Installed on 2019-01-02 (1315 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dpkg UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-01-02 (1316 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers wireshark _MarkForUpload: True dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+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 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
- played with linux-image-6.5.0-1003-intel-opt -bluetooth stopped working at all
- installed linux 6.5.0-13-generic
- installed linux-modules-extra-6.5.0-13-generic
- after reboot everything was fixed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in Linux Firmware:
New
Status in bluez package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
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.ec.firmware.release: 1.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2037906/+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 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal
This bug is awaiting verification that the linux/5.4.0-169.187 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux' to 'verification-done-focal-linux'. If the problem still exists, change the tag 'verification-needed-focal- linux' to 'verification-failed-focal-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043197 Title: USB bus error after upgrading to proposed kernel on lunar, jammy and focal Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No su
[Kernel-packages] [Bug 1839450] Re: ubuntu_ftrace_smoke_test failed on D-aws a1.medium arm64 instance
Disco EOL. ** Changed in: linux-aws (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839450 Title: ubuntu_ftrace_smoke_test failed on D-aws a1.medium arm64 instance Status in ubuntu-kernel-tests: Won't Fix Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Won't Fix Bug description: Issue found on AWS ARM64 instance a1.medium, passed on the other 2 (a1.2xlarge / a1.large) Test failed with: FAILED (irq traces found must be > 32, got 18) PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-5.0.0-1011-aws) PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-5.0.0-1011-aws) PASSED (CONFIG_STACK_TRACER=y in /boot/config-5.0.0-1011-aws) PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-5.0.0-1011-aws) PASSED all expected /sys/kernel/debug/tracing files exist PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers) PASSED (function in /sys/kernel/debug/tracing/available_tracers) PASSED (nop in /sys/kernel/debug/tracing/available_tracers) PASSED (function can be enabled) FAILED (irq traces found must be > 32, got 18) PASSED (function_graph can be enabled) PASSED (irq traces found must be > 32, got 9279) PASSED (tracer hwlat can be enabled (got 12 lines of tracing output)) PASSED (tracer blk can be enabled (got 2 lines of tracing output)) PASSED (tracer function_graph can be enabled (got 1374 lines of tracing output)) PASSED (tracer wakeup_dl can be enabled (got 2 lines of tracing output)) PASSED (tracer wakeup_rt can be enabled (got 66 lines of tracing output)) PASSED (tracer wakeup can be enabled (got 64 lines of tracing output)) PASSED (tracer function can be enabled (got 757 lines of tracing output)) Summary: 18 passed, 1 failed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12 ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15 Uname: Linux 5.0.0-1011-aws aarch64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: arm64 Date: Thu Aug 8 10:56:19 2019 Ec2AMI: ami-0ac1a3bc4f5c85238 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839450/+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 2044554] [NEW] Turn off non-zynqmp arch support
Public bug reported: [ Impact ] * This is an optimized kernel for zynqmp range of devices. * Currently about 14% of kernel build is targeting non-zynqmp devices, which is dead code unused in production * This reduces kernel build time, kernel image & modules size, amount of required firmware, and makes initrd smaller. * This reduces peak memory usage on boot as well * This will loose ability to execute this exact same kernel build on non-zynqmp device, for benchmarking purposes generic kernel should be used instead. [ Test Plan ] * Ensure newly produced kernel installs and boots on Ubuntu Server and Ubuntu Core target devices without any loss of peripherals and stock devices. [ Where problems could occur ] * This changes may limit ability to smoke-test this kernel on non-zynqmp devices, if needed support for individual CPUs can be turned back on. Or ideally any such testing should move to zynqmp devices. (examples of potentially interesting things to turn back on upon request are QCOM APPLE suppport for running this kernel on Arm Laptops for developer convenience) * It is expected for KVM and QEMU to continue to work as both host and guest [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2044554 Title: Turn off non-zynqmp arch support Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] * This is an optimized kernel for zynqmp range of devices. * Currently about 14% of kernel build is targeting non-zynqmp devices, which is dead code unused in production * This reduces kernel build time, kernel image & modules size, amount of required firmware, and makes initrd smaller. * This reduces peak memory usage on boot as well * This will loose ability to execute this exact same kernel build on non-zynqmp device, for benchmarking purposes generic kernel should be used instead. [ Test Plan ] * Ensure newly produced kernel installs and boots on Ubuntu Server and Ubuntu Core target devices without any loss of peripherals and stock devices. [ Where problems could occur ] * This changes may limit ability to smoke-test this kernel on non-zynqmp devices, if needed support for individual CPUs can be turned back on. Or ideally any such testing should move to zynqmp devices. (examples of potentially interesting things to turn back on upon request are QCOM APPLE suppport for running this kernel on Arm Laptops for developer convenience) * It is expected for KVM and QEMU to continue to work as both host and guest [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2044554/+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 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
Is there an alternative patch in development? This bug (or at least it seems to be this bug) still affects us. -- 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/2032164 Title: A general-proteciton exception during guest migration to unsupported PKRU machine Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Triaged Bug description: [Impact] When a host that supports PKRU initiates a guest that lacks PKRU support, the flag is enabled on the guest's fpstate. This information is then passed to userspace through the vcpu ioctl KVM_GET_XSAVE. However, a problem arises when the user opts to migrate the mentioned guest to another machine that does not support PKRU. In this scenario, the new host attempts to restore the guest's fpu registers. Nevertheless, due to the absence of PKRU support on the new host, a general-protection exception takes place, leading to a guest crash. [Fix] The problem is resolved by the following upstream commit: ad856280ddea x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 Additionally, a subsequent fix tackles the migration problem stemming from the earlier commit: a1020a25e697 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES [Test Plan] 1. Set up two machines: one with PKRU support and the other without. 2. Initiate a guest that lacks PKRU support on the machine with PKRU support. 3. Utilize libvirt to migrate the aforementioned guest to a different machine that lacks PKRU support. 4. The error emerges on the destination machine: KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=86cf7970 EBX= ECX=0001 EDX=005b0036 ESI=0087 EDI=0087 EBP=87c03e38 ESP=87c03e18 EIP=86cf7d5e EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2023-07-09T03:03:14.911750Z qemu-system-x86_64: terminating on signal 15 from pid 4134 (/usr/sbin/libvirtd) 2023-07-09 03:03:15.312+: shutting down, reason=destroyed [Where problems could occur] The introduced commits will impact the guest migration process, potentially leading to failures and preventing the guest from operating successfully on the migration destination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032164/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
This bug was fixed in the package alsa-ucm-conf - 1.2.10-1ubuntu1 --- alsa-ucm-conf (1.2.10-1ubuntu1) noble; urgency=medium * Merge with Debian unstable. Remaining changes: - d/p/0001-Add-initial-support-for-MediaTek-mt8390-evk-and-mt83.patch - add initial support for MediaTek mt8390-evk and mt8395-evk (LP: 2000228) * Dropped changes [all in upstream 1.2.10]: - d/p/0001-ucm2-Qualcomm-sc8280xp-fix-device-numbers.patch - ucm2: Qualcomm: sc8280xp: fix device numbers (LP: 2036731) - d/p/0001-acp63-add-initial-support-for-AMD-Pink-Sardine-ACP63.patch d/p/0002-acp63.conf-use-symbolic-link.patch d/p/0003-acp62-add-initial-support-for-AMD-ACP-v6.2-RPL.patch - Backport patches to add support AMD ACP RPL and Pink Sardine. (LP: 2025353) * Added changes - added headers and background info to d/p/0001-Add-initial-support-for-MediaTek-mt8390-evk-and-mt83.patch [Artur Pak] * d/p/0001-ucm2-soundwire-add-rt713-SDCA-device.patch: - Backport patch to add rt713 SDCA device (LP: #2042902) -- Christian Ehrhardt Fri, 24 Nov 2023 09:12:05 +0100 ** Changed in: alsa-ucm-conf (Ubuntu Noble) Status: Fix Committed => Fix Released -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Released Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 1959424] Re: ubuntu_kernel_selftests / ftrace:ftracetest hangs on arm64 on Jammy realtime
*** This bug is a duplicate of bug 2029405 *** https://bugs.launchpad.net/bugs/2029405 ** This bug has been marked a duplicate of bug 2029405 Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 -- 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/1959424 Title: ubuntu_kernel_selftests / ftrace:ftracetest hangs on arm64 on Jammy realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: d2021.10.26/jammy/linux-realtime/5.15.0-1004.4, only on node appleton-kernel.arm64, hangs (timeouts) on ubuntu_kernel_selftests / ftrace:ftracetest test: 01:28:34 DEBUG| [stdout] # === Ftrace unit tests === 01:28:34 DEBUG| [stdout] # [1] Basic trace file check[PASS] 01:28:38 DEBUG| [stdout] # [2] Basic test for tracers[PASS] 01:28:38 DEBUG| [stdout] # [3] Basic trace clock test[PASS] 01:28:38 DEBUG| [stdout] # [4] Basic event tracing check[PASS] 01:28:39 DEBUG| [stdout] # [5] Change the ringbuffer size[PASS] 01:28:39 DEBUG| [stdout] # [6] Snapshot and tracing setting[PASS] 01:28:40 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS] 01:28:40 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 01:28:40 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 01:28:40 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe events[PASS] 01:28:41 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe events[PASS] 01:28:41 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic events[PASS] 01:28:41 DEBUG| [stdout] # [13] Generic dynamic event - selective clear (compatibility)[PASS] 01:28:41 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event [PASS] 01:28:42 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate events are caught[PASS] 01:58:36 INFO | Timer expired (1800 sec.), nuking pid 161336 The issue was not reproduced on mcdivitt36 (HP ProLiant m400 server cartridge with AppliedMicro X-Gene 64-bit ARM). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1959424/+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 2044512] Re: Build failure if run in a console
LP builds don't fail but the logs show funny characters: # Compress kernel modules find debian/linux-buildinfo-6.5.0-1007-laptop -name '*.ko' -print0 | xargs -0 -n1 -P 4 zstd -19 --quiet --rm (�/�$��Qdh_fixperms -plinux-buildinfo-6.5.0-1007-laptop -X/boot/ dh_shlibdeps -plinux-buildinfo-6.5.0-1007-laptop -- -l/usr/aarch64-linux-gnu/lib ** No longer affects: linux (Ubuntu Lunar) -- 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/2044512 Title: Build failure if run in a console Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: [Impact] Build fails if run in a console: $ debian/rules binary ... # Compress kernel modules find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 -P 8 zstd -19 --quiet --rm stdout is a console, aborting make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123 [Test Case] See above. [Where Problems Could Occur] Build failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044512/+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 2044512] [NEW] Build failure if run in a console
Public bug reported: [Impact] Build fails if run in a console: $ debian/rules binary ... # Compress kernel modules find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 -P 8 zstd -19 --quiet --rm stdout is a console, aborting make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123 [Test Case] See above. [Where Problems Could Occur] Build failures. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Summary changed: - Build failure when run in a console + Console build failure ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Description changed: [Impact] Build fails if run in a console: $ debian/rules binary ... # Compress kernel modules find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 -P 8 zstd -19 --quiet --rm stdout is a console, aborting make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123 + + [Test Case] + + See above. + + [Where Problems Could Occur] + + Build failures. ** Summary changed: - Console build failure + Build failure if run in a console -- 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/2044512 Title: Build failure if run in a console Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: [Impact] Build fails if run in a console: $ debian/rules binary ... # Compress kernel modules find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 -P 8 zstd -19 --quiet --rm stdout is a console, aborting make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123 [Test Case] See above. [Where Problems Could Occur] Build failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044512/+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 2044131] Re: i915 regression introduced with 5.5 kernel
Fields in the "Modeline" output are: (m)->name, drm_mode_vrefresh(m), (m)->clock, \ (m)->hdisplay, (m)->hsync_start, (m)->hsync_end, (m)->htotal, \ (m)->vdisplay, (m)->vsync_start, (m)->vsync_end, (m)->vtotal, \ (m)->type, (m)->flags -- 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/2044131 Title: i915 regression introduced with 5.5 kernel Status in linux package in Ubuntu: New Bug description: There is a regression preventing a user to upgrade from 5.4 kernel to anything that's higher than 5.5. When using such kernel the image orientation is wrong (rotated by 90°C). Also the kernel log contains: wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06 wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25 wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga console wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory information wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:o> wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v> wrz 15 09:19:49 desktop kernel: wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.> wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]' (full stack trace attached) The video hardware in use is: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) (...) Kernel driver in use: i915 Kernel modules: i915 The user wanted to upgrade from bionic to focal with HWE kernel (they needed it due to some networking hardware they wanted to have supported by the newer kernel). The user was testing mainline stable kernels and noticed that the last working kernel was the 5.4 series, while anything starting from 5.5 and above is BROKEN (symptoms as described in the first paragraph above). Together with the user we have run a bisection between v5.4 and v5.5 on the upstream stable kernel and we were able to identify the first broken commit to be: 8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder timing minimum limits To confirm I have reverted this change on top of the HWE kernel for focal and the user have confirmed that this resolved the issue (test build available at ppa:dgadomski/kernel-sf368743). I am not fully sure what the purpose of this patch was, but I assume the regression was not intended and the hardware should be still supported. Attaching lshw and lspci output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044131/+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 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels
** Also 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1812189 Title: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: New Status in linux-gke package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: New Bug description: This test will attempt to insert the test_bpf module, but this module does not exist in KVM kernels: $ sudo modprobe test_bpf modprobe: FATAL: Module test_bpf not found in directory /lib/modules/4.15.0-1028-kvm The script: $ sudo ./test_bpf.sh test_bpf: [FAIL] $ cat test_bpf.sh #!/bin/sh # SPDX-License-Identifier: GPL-2.0 # Runs bpf test using test_bpf kernel module if /sbin/modprobe -q test_bpf ; then /sbin/modprobe -q -r test_bpf; echo "test_bpf: ok"; else echo "test_bpf: [FAIL]"; exit 1; fi This test_bpf module will need the CONFIG_TEST_BPF to be enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 08:29:29 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812189/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
I hope the links and explanations added will help you in future uploads. Even better, next time be available on IRC after the ping, but I understand it might be rather late for you - so this isn't a complaint but a recommendation. The upload to noble should unblock you there, once you verified all is indeed fine there you can update the SRU uploads accordingly (patch headers). If you want to overachieve (=this is optional and depends how sure or not you are), pre-build in PPAs and demonstrate you have tested it there successfully. Then you can ping sponsors again to sponsor the uploads to -unapproved for the SRU team to have a look. ** Changed in: alsa-ucm-conf (Ubuntu Noble) Status: New => Fix Committed -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
For now https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.10-1ubuntu1 looks just as good as in my tests. -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
I've created the merge of 1.2.10 by following [1], then re-added the patch of Ethan and that of you Artur. I hope I didn't add too many issues :-) At least I'm sure I got this whole topic much forward. The merge including all I mentioned can be seen here (As training material for how this upload could have been for noble) => https://code.launchpad.net/~paelzer/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/456227 I tested the build in a PPA and while I couldn't test on much real HW (just a super old NUC and I didn't fully know what to check - it had sound at least) it is early enough in the noble cycle for you to have a look at that. I hope that also is easier for you as you might be closer to HW to test. And in general it seems 1.2.10 is the version for noble, as 1.2.11 would be expected in ~May 2024. So the merge should have been done at some point. [1]: https://github.com/canonical/ubuntu-maintainers- handbook/blob/main/PackageMerging.md -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
I contacted Ethan who created the one patch I could not track down. He had all the information that I needed: - This is actually from - https://github.com/alsa-project/alsa-ucm-conf/pull/321 - https://github.com/alsa-project/alsa-ucm-conf/pull/322 - related to private LP bug 2037058 - Not yet upstream accepted, but discussed with sil2100 and accepted as-is for now - Ethan plans to file a public LP and update it once upstream accepted a final form of it I'll put all of that into the patch headers to help the next person that comes by. -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
Analyze for merge readiness: The current delta is: * d/p/0001-ucm2-Qualcomm-sc8280xp-fix-device-numbers.patch * d/p/0001-acp63-add-initial-support-for-AMD-Pink-Sardine-ACP63.patch * d/p/0002-acp63.conf-use-symbolic-link.patch * d/p/0003-acp62-add-initial-support-for-AMD-ACP-v6.2-RPL.patch => Those are in 1.2.10 and can be dropped on a merge * d/p/0001-Add-initial-support-for-MediaTek-mt8390-evk-and-mt83.patch => This is not upstream AFAICS => It does not have the dep-3 patch headers for Forwarded or Origin and sadly such moments trying to find what happened is just why they should always be added. This is a sin of the past and not your fault Artur, but your patch also misses those, so let me teach you about that ... Learning links: - Standard for patch headers: https://dep-team.pages.debian.net/deps/dep3/ - If you want it a bit more consumable https://github.com/canonical/ubuntu-maintainers-handbook/blob/a5a386be1be1507fbd1dd8842699b0758042169c/DebianPatch.md#the-patchfile-header Also your git export is not of the hash that is in the final repository Instead it is from the PR which might go away and is therefore harder to find. And finally, no trace back from the patch to the bug that made it being added. So overall your patch should ideally be like: - use correct git hash - add Origin - add Applied-Upstream - Add last-update Which makes it start like: From b422a8e08cb3845053ece1fc832294adca21a684 Mon Sep 17 00:00:00 2001 From: Shuming Fan Date: Thu, 12 Oct 2023 10:07:36 +0800 Subject: [PATCH] ucm2: soundwire: add rt713 SDCA device Closes: https://github.com/alsa-project/alsa-ucm-conf/pull/363 Signed-off-by: Shuming Fan Signed-off-by: Jaroslav Kysela Origin: upstream, https://github.com/alsa-project/alsa-ucm-conf/commit/b422a8e08cb3845053ece1fc832294adca21a684 Bug: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902 Applied-Upstream: v1.2.11 Last-Update: 2023-11-24 --- ... I'll do that for you here for noble to make some progress, but you can still fix this up for the SRU uploads. It really would have helped if you'd have been available after you pinged me on IRC. At the end of the day we want to teach, not just correct uploads. -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
I got a ping on patch pilot duty, sadly on my ping back if they would be available for questions if I find more that needs to be sorted out was unanswered. So I need to carry all into this bug. This is kind of a log of my own understanding process, feel free to ignore it: Proposed change: - It adds a few regex expressions to allow matching the new HW - and then configuration for those new matches - Accepted upstream - Other than fixup releases Upstream seems to tag two releases per year, one in Q2 one in Q4 - Due to that I'd this to be in a new revision v1.2.11 by May 2024 - that might be worth to mention for packages to know when they will be able to drop it Paride and Athos guided you to correctly obey the usual "fix -devel first" rule and due to noble being new that you need to start there. We are adding one particular device, but I see that due to having added Ubuntu delta in the past we have not yet picked up 1.2.10 which would have picked up plenty of other fixes and devices. => https://github.com/alsa-project/alsa-ucm-conf/releases/tag/v1.2.10 alsa-ucm-conf | 1.2.10-1 | unstable | source, all alsa-ucm-conf | 1.2.9-1ubuntu3 | noble | source, all The SRU fix is fine, those are meant to be surgical based on the need of our users, but for noble it feels we should aim for 1.2.10 + this. Checking who usually did that, ah Jürg and Ethan - fine we can ask them for opinions as they might know the subject matter. Great, so I'd propose we combine a merge of 1.2.10 with your fix on top. -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 2011768] Re: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2011768 Title: Fix NVME storage with RAID ON disappeared under Dell factory WINPE environment Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] NVME storage disappeared under Dell factory WINPE environment with RAID ON mode when this WINPE boot entry touched by efibootmgr [Fix] Reset the VMD msi remapping during shutdown. [Test Case] 1. Install Ubuntu 2. Then, system will reboot to WINPE to do some cleanup work. 3. in WINPE, the NVME storage could be listed. [Where problems could occur] Low, the issue may be observed on VMD MSI remapping. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011768/+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 2044199] Re: package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dkms (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2044199 Title: package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: Confirmed Bug description: Maybe the issue is related to power saving. The system tried to download and update a package (new kernel image), AFAIK, without my intervention. Then one of the DKMS steps failed, and the install procedure failed. the dmesg command shows nothing particularly interesting. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38 ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pag2341 F wireplumber /dev/snd/controlC0: pag2341 F wireplumber /dev/snd/seq:pag2330 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Nov 21 19:12:16 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-09-13 (434 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XCJ/550XCR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=/dev/mapper/vg1_ssd-lv1_root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-06-05 (169 days ago) dmi.bios.date: 12/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11RFH.051.201229.HC dmi.board.asset.tag: No Asset Tag dmi.board.name: NP550XCJ-XS2BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLA664A0C-C01-G003-S0001+10.0.19041 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11RFH.051.201229.HC:bd12/29/2020:br5.16:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XCJ/550XCR:pvrP11RFH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XCJ-XS2BR:rvrSGLA664A0C-C01-G003-S0001+10.0.19041:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PRFH: dmi.product.family: Notebook 5 Series dmi.product.name: 550XCJ/550XCR dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PRFH dmi.product.version: P11RFH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2044199/+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 2044003] Re: Don't produce linux-*-tools-{common, host} binary packages
Verified that linux-tools-common and linux-tools-host are no longer
being built:
Built packages
linux-buildinfo-6.5.0-1007-laptop Linux kernel buildinfo for version 6.5.0
on ARMv8 SMP
linux-headers-6.5.0-1007-laptop Linux kernel headers for version 6.5.0 on
ARMv8 SMP
linux-image-6.5.0-1007-laptop Linux kernel image for version 6.5.0 on ARMv8
SMP
linux-image-6.5.0-1007-laptop-dbgsym Linux kernel debug image for version
6.5.0 on ARMv8 SMP
linux-laptop-headers-6.5.0-1007 Header files related to Linux kernel
version 6.5.0
linux-laptop-tools-6.5.0-1007 Linux kernel version specific tools for
version 6.5.0-1007
linux-modules-6.5.0-1007-laptop Linux kernel extra modules for version
6.5.0 on ARMv8 SMP
linux-tools-6.5.0-1007-laptop Linux kernel version specific tools for
version 6.5.0-1007
** Tags removed: verification-needed-mantic-linux-laptop
** Tags added: verification-done-mantic-linux-laptop
** Also affects: linux-laptop (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux-laptop (Ubuntu)
Status: New => Invalid
** Changed in: linux-laptop (Ubuntu Mantic)
Status: New => Fix Committed
** Changed in: linux-laptop (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-laptop in Ubuntu.
https://bugs.launchpad.net/bugs/2044003
Title:
Don't produce linux-*-tools-{common,host} binary packages
Status in linux-laptop package in Ubuntu:
Confirmed
Status in linux-laptop source package in Mantic:
Fix Committed
Bug description:
[Impact]
Some kernels produce linux-*-tools-common and/or linux-*-tools-host
binary deb packages. That is all wrong, only the primary/main linux
source package should produce these. These packages result in install
failures of the regular linux-tools-{common,host} packages.
[Test Case]
Check list of built binary packages in LP and verify the packages are
not built.
[Where Problems Could Occur]
Already installed packages won't upgrade and become stale.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-laptop/+bug/2044003/+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 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
https://lists.ubuntu.com/archives/kernel-team/2023-November/147192.html ** Description changed: - First time seen this since ftrace refactor out from - ubuntu_kernel_selftests to ubuntu-kselftests-ftrace + + [Impact] + On ARM64 systems, tests like event-enable.tc, event-pid.tc in + linux/tools/testing/selftests/ftrace will take too much time to run + and consequently leading to test timeout. + + The culprit is the `cat` command on the changing trace file. + + [Fix] + * 25b9513872 selftests/ftrace: Stop tracing while reading the trace + file by default + + This patch can be cherry-picked into Jammy. I didn't see this issue in + our 5.4 kernels. And it's already landed in newer kernels. + + [Test] + On an ARM64 testing node, apply this patch to the kernel tree and run + event-pid.tc test in linux/tools/testing/selftests/ftrace with: + + sudo ./ftracetest -vvv test.d/event/event-pid.tc + + The test should finish within a few minutes. + + [Regression Potential] + Change limited to testing tools, it should not have any actual impact + to kernel functions. + + == Original Bug Report == + First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: - Running './ftracetest -vvv test.d/event/subsystem-enable.tc' - === Ftrace unit tests === - - [1] event tracing - enable/disable with event level files - + [ 2 -eq 1 ] - + [ -f set_event_pid ] - + echo - + [ -f set_ftrace_pid ] - + echo - + [ -f set_ftrace_notrace ] - + echo - + [ -f set_graph_function ] - + echo - + tee set_graph_function set_graph_notrace - + [ -f stack_trace_filter ] - + echo - + [ -f kprobe_events ] - + echo - + [ -f uprobe_events ] - + echo - + [ -f synthetic_events ] - + echo - + [ -f snapshot ] - + echo 0 - + clear_trace - + echo - + enable_tracing - + echo 1 - + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc - + echo sched:sched_switch - + yield - + ping 127.0.0.1 -c 1 - PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. - 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms - - --- 127.0.0.1 ping statistics --- - 1 packets transmitted, 1 received, 0% packet loss, time 0ms - rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms - + cat trace - + grep sched_switch - + wc -l - Timer expired (600 sec.), nuking pid 20982 + Running './ftracetest -vvv test.d/event/subsystem-enable.tc' + === Ftrace unit tests === + + [1] event tracing - enable/disable with event level files + + [ 2 -eq 1 ] + + [ -f set_event_pid ] + + echo + + [ -f set_ftrace_pid ] + + echo + + [ -f set_ftrace_notrace ] + + echo + + [ -f set_graph_function ] + + echo + + tee set_graph_function set_graph_notrace + + [ -f stack_trace_filter ] + + echo + + [ -f kprobe_events ] + + echo + + [ -f uprobe_events ] + + echo + + [ -f synthetic_events ] + + echo + + [ -f snapshot ] + + echo 0 + + clear_trace + + echo + + enable_tracing + + echo 1 + + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + + echo sched:sched_switch + + yield + + ping 127.0.0.1 -c 1 + PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. + 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms + + --- 127.0.0.1 ping statistics --- + 1 packets transmitted, 1 received, 0% packet loss, time 0ms + rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + + cat trace + + grep sched_switch + + wc -l + Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: - count=`cat trace | grep sched_switch | wc -l` + count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. ** Description changed: - [Impact] - On ARM64 systems, tests like event-enable.tc, event-pid.tc in - linux/tools/testing/selftests/ftrace will take too much time to run - and consequently leading to test timeout. + On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc, + event-pid.tc in linux/tools/testing/selftests/ftrace will take too + much time to run and consequently leads to test timeout. The culprit is the `cat` command on the changing trace file. [Fix] * 25b9513872 selftests/ftrace: Stop tracing while reading the trace - file by default + file by default This patch can be cherry-picked into Jammy. I didn't see this issue in our 5.4 kernels. And it's already landed in newer kernels. [Test] On an ARM64 testing node, apply this patch to the kernel tree and run event-pid.tc test in linux/tools/testing/selftests/ftrace with: - sudo ./ftracetest -vvv test.d/event/event-pid.tc + sudo ./ftracetest -vvv test.d/event/event-pid.tc The tes
[Kernel-packages] [Bug 2042946] Re: sound poping and cracking
*** This bug is a duplicate of bug 2042039 *** https://bugs.launchpad.net/bugs/2042039 ** This bug has been marked a duplicate of bug 2042039 AUDIO POPPING After New Kernel install: 5.15.0-88.98 -- 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/2042946 Title: sound poping and cracking Status in linux package in Ubuntu: New Bug description: since installing kernel 5.15.0-88, my sound is popping and cracking very loudly, I had to deactivate my sound card. No issue with XX.0-87. Realtek ALC255, on hda intel PCH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042946/+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 2044384] Re: crackling sound
*** This bug is a duplicate of bug 2042039 *** https://bugs.launchpad.net/bugs/2042039 ** This bug has been marked a duplicate of bug 2042039 AUDIO POPPING After New Kernel install: 5.15.0-88.98 -- 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/2044384 Title: crackling sound Status in linux package in Ubuntu: New Bug description: Still the same problem of cracking sound since 5.15.0-88. Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71 Sound Server-1: ALSA v: k5.15.0-87-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044384/+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 2044003] Re: Don't produce linux-*-tools-{common, host} binary packages
This bug is awaiting verification that the linux-laptop/6.5.0-1007.10
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-laptop' to 'verification-done-
mantic-linux-laptop'. If the problem still exists, change the tag
'verification-needed-mantic-linux-laptop' to 'verification-failed-
mantic-linux-laptop'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-mantic-linux-laptop-v2
verification-needed-mantic-linux-laptop
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-laptop in Ubuntu.
https://bugs.launchpad.net/bugs/2044003
Title:
Don't produce linux-*-tools-{common,host} binary packages
Status in linux-laptop package in Ubuntu:
New
Bug description:
[Impact]
Some kernels produce linux-*-tools-common and/or linux-*-tools-host
binary deb packages. That is all wrong, only the primary/main linux
source package should produce these. These packages result in install
failures of the regular linux-tools-{common,host} packages.
[Test Case]
Check list of built binary packages in LP and verify the packages are
not built.
[Where Problems Could Occur]
Already installed packages won't upgrade and become stale.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-laptop/+bug/2044003/+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 2044131] Re: i915 regression introduced with 5.5 kernel
Looks like this is hardware-specific and read from BIOS: [drm:intel_bios_init [i915]] Found panel mode in BIOS VBT legacy lfp table: [drm:drm_mode_debug_printmodeline [drm]] Modeline "800x1280": 50 54000 800 810 820 830 1280 1290 1300 1310 0x8 0xa -- 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/2044131 Title: i915 regression introduced with 5.5 kernel Status in linux package in Ubuntu: New Bug description: There is a regression preventing a user to upgrade from 5.4 kernel to anything that's higher than 5.5. When using such kernel the image orientation is wrong (rotated by 90°C). Also the kernel log contains: wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06 wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12 wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 80x25 wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga console wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory information wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:o> wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/glk_dmc_ver1_04.bin (v> wrz 15 09:19:49 desktop kernel: wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.> wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]' (full stack trace attached) The video hardware in use is: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) (...) Kernel driver in use: i915 Kernel modules: i915 The user wanted to upgrade from bionic to focal with HWE kernel (they needed it due to some networking hardware they wanted to have supported by the newer kernel). The user was testing mainline stable kernels and noticed that the last working kernel was the 5.4 series, while anything starting from 5.5 and above is BROKEN (symptoms as described in the first paragraph above). Together with the user we have run a bisection between v5.4 and v5.5 on the upstream stable kernel and we were able to identify the first broken commit to be: 8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder timing minimum limits To confirm I have reverted this change on top of the HWE kernel for focal and the user have confirmed that this resolved the issue (test build available at ppa:dgadomski/kernel-sf368743). I am not fully sure what the purpose of this patch was, but I assume the regression was not intended and the hardware should be still supported. Attaching lshw and lspci output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044131/+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 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9
** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042060 Title: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume from suspend. The audio play and capture functions are not working after resume from S3. [Fix] Backport the fix from Cirrus on linux-next https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/. [Test Case] 1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA . 2. Perform system suspend/resume at least 3 times. 3. Verify the audio functions, including playback and capture [Where problems could occur] Only affect specific laptops with the CS35L41 HDA. The impact is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042060/+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 2044131] Re: i915 regression introduced with 5.5 kernel
The commit in question (8f4b1068e7fc3df1a77ac8151767e56b208cc87f)
introduces the following logic in intel_mode_valid function
(drivers/gpu/drm/i915/display/intel_display.c):
+ if (DISPLAY_VER(dev_priv) >= 5) {
+ if (mode->hdisplay < 64 ||
+ mode->htotal - mode->hdisplay < 32)
+ return MODE_H_ILLEGAL;
+
+ if (mode->vtotal - mode->vdisplay < 5)
+ return MODE_V_ILLEGAL;
+ } else {
+ if (mode->htotal - mode->hdisplay < 32)
+ return MODE_H_ILLEGAL;
+
+ if (mode->vtotal - mode->vdisplay < 3)
+ return MODE_V_ILLEGAL;
+ }
In case of this particular hardware the following condition is met:
if (mode->htotal - mode->hdisplay < 32)
return MODE_H_ILLEGAL;
with values: htotal==830 and hdisplay=800 resulting in returning
MODE_H_ILLEGAL.
I am looking into where does the htotal value come from.
--
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/2044131
Title:
i915 regression introduced with 5.5 kernel
Status in linux package in Ubuntu:
New
Bug description:
There is a regression preventing a user to upgrade from 5.4 kernel to
anything that's higher than 5.5. When using such kernel the image orientation
is wrong (rotated by 90°C). Also the kernel log contains:
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version
24.8.0, H2C version 12
wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device
80x25
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga
console
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory
information
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA
decodes: olddecodes=io+mem,decodes=io+mem:o>
wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC
firmware i915/glk_dmc_ver1_04.bin (v>
wrz 15 09:19:49 desktop kernel:
wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'
(full stack trace attached)
The video hardware in use is:
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
(...)
Kernel driver in use: i915
Kernel modules: i915
The user wanted to upgrade from bionic to focal with HWE kernel (they
needed it due to some networking hardware they wanted to have
supported by the newer kernel).
The user was testing mainline stable kernels and noticed that the last
working kernel was the 5.4 series, while anything starting from 5.5
and above is BROKEN (symptoms as described in the first paragraph
above).
Together with the user we have run a bisection between v5.4 and v5.5 on the
upstream stable kernel and we were able to identify the first broken commit to
be:
8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder
timing minimum limits
To confirm I have reverted this change on top of the HWE kernel for
focal and the user have confirmed that this resolved the issue (test
build available at ppa:dgadomski/kernel-sf368743).
I am not fully sure what the purpose of this patch was, but I assume
the regression was not intended and the hardware should be still
supported.
Attaching lshw and lspci output.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044131/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/456227 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/456228 -- 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/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: New Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: New Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+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 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
** Summary changed: - ftrace:test.d--event--subsystem-enable.tc fails with timeout on focal:linux-hwe-5.15 ARM64 + Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 -- 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/2029405 Title: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: First time seen this since ftrace refactor out from ubuntu_kernel_selftests to ubuntu-kselftests-ftrace Issue found on ARM64 nodes with both generic / generic-64k kernel. Partial test log: Running './ftracetest -vvv test.d/event/subsystem-enable.tc' === Ftrace unit tests === [1] event tracing - enable/disable with event level files + [ 2 -eq 1 ] + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc + echo sched:sched_switch + yield + ping 127.0.0.1 -c 1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms + cat trace + grep sched_switch + wc -l Timer expired (600 sec.), nuking pid 20982 From the code (tools/testing/selftests/ftrace/test.d/event/event- enable.tc) this test is trying to run: count=`cat trace | grep sched_switch | wc -l` This command caused the timeout as `cat trace` seems to be never ending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+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
