[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
>From comment #9, some users reported Lenovo ThinkBook 15 IIL takes additional IDs in the elan i2c ID list to be recognized. Apparently the are some more issues with these Lenovo ThinkBook models, maybe even the same model with different BIOS version, but the addition of these new IDs can still be the first step to make some of them working. While we don't have all the hardware to work on at the same time, progress will still be made. Checked the proposed change is already included in eoan-proposed as version 5.3.0-56.50. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan ** Tags added: hwe-touchpad -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1875863] Re: ceph -- Unable to mount ceph volume on s390x
@Tuan, would you be able to verify this LP ticket again? The patch should be included in the kernel that is currently in proposed (the re-spin was done). Thx -- 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/1875863 Title: ceph -- Unable to mount ceph volume on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * Unable to mount ceph volumes on big endian systems, like s390x. * The mount operation always fails with an IO error. * This is caused by an endiness issue in function handle_session where variable features is always little endian. * But test_bit assumes the host order of bytes, hence causes a problem on big endian systems. [Fix] * 0fa8263367db9287aa0632f96c1a5f93cc478150 0fa8263367db "ceph: fix endianness bug when handling MDS session feature bits" [Test Case] * Setup ceph on s390x. * Try to mount a ceph volume. * If it mounts correctly the patch is applied and working. * Without the patch a mount always fails on big endian / s390x. [Regression Potential] * There is regression potential with having code changes in ceph's session handler, which is common code. * However, the patch was accepted (slightly changed) by the ceph maintainers and with that got upstream accepted, too. * The patch is fairly limited (5 lines removed, 3 added), hence the changes are quite traceable. __ When mounting a ceph volume, mount operation fails with an IO error. The problem is always reproducible. Identified potential root cause as kernel endian bug: In the function handle_session() variable @features always contains little endian order of bytes. Just because The feature mask sent by the MDS is little-endian (bits are packed bytewise from left to right in encode_supported_features()). However, test_bit(), called to check features availability, assumes the host order of bytes in that variable. This leads to problems on big endian architectures. Specifically it is impossible to mount ceph volume on s390. A fixup was proposed to convert little-endian order of bytes to the host one. That fixup was modified by ceph maintainers to use existing unpacking means for the conversion. The resulted patch attached. Related discussion in the ceph-development mailing list: https://marc.info/?l=ceph-devel&m=158815357301332&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1875863/+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 1881869] Re: linux-aws: Xen / hibernation: xen-netfront panic + resume hangs
** Changed in: linux-aws (Ubuntu Eoan) Status: Confirmed => Fix Committed ** Changed in: linux-aws (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1881869 Title: linux-aws: Xen / hibernation: xen-netfront panic + resume hangs Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Eoan: Fix Committed Status in linux-aws source package in Focal: Fix Committed Bug description: [Impact] During our AWS testing we were able to trigger some hibernation failures in some Xen instance types. One problem is a kernel panic in the resume callback of the xen- netfront driver. A workaround to this problem is to compile the driver as a module and reload it at resume (we were already doing this reload with the bionic kernel that had this driver compiled as a module, but for some reasons eoan and focal had this statically compiled). Other issues were showing up as hangs on resume, these seem to be prevented by using the new Xen/hibernation patch set posted by Anchal to the LKML: https://lore.kernel.org/lkml/cover.1589926004.git.ancha...@amazon.com/ This new patch set is still being reviewed, but according to our tests it really seems to fix some of these hangs on resume. In addition to that we can improve hibernation reliability and performance even more by applying the updated swapoff optimization patch (that has been merged upstream). [Test case] Create a Xen instance in AWS, hibernate/resume multiple times. [Fix] The following set of fixes can be used to improve hibernation performance and reliability: - new Xen/hibernation patch set from the LKML (see link above) - config change to compile xen-netfront as a module - new swapoff optimization patch [Regression potential] The xen-netfront config change and the new swapoff optimization patch are pretty safe (one is a config change that affects only the xen- netfront driver, the other is a clean cherry-pick of an upstream commit). The new Xen/hibernation update is pretty big and the new patches are still under review, however according to our tests it really seems to fix some of the hang issues (it definitely makes things better). Moreover, all the changes are affecting Xen and they are restricted to the hibernation/resume code paths, so, in conclusion, the overall regression potential is minimal. [See also] NOTE: the fix mentioned in LP: #1879711 (disable CONFIG_DMA_CMA) was also applied during our tests and it is also required to make hibernation stable in Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1881869/+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 1882303] Re: Eoan update: upstream stable patchset 2020-06-05
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882303 Title: Eoan update: upstream stable patchset 2020-06-05 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-06-05 Ported from the following upstream stable releases: v4.19.125, v5.4.43 from git://git.kernel.org/ i2c: dev: Fix the race between the release of i2c_dev and cdev KVM: SVM: Fix potential memory leak in svm_cpu_init() ima: Set file->f_mode instead of file->f_flags in ima_calc_file_hash() evm: Check also if *tfm is an error pointer in init_desc() ima: Fix return value of ima_write_policy() mtd: spinand: Propagate ECC information to the MTD structure fix multiplication overflow in copy_fdtable() ubifs: remove broken lazytime support iommu/amd: Fix over-read of ACPI UID from IVRS table i2c: mux: demux-pinctrl: Fix an error handling path in 'i2c_demux_pinctrl_probe()' ubi: Fix seq_file usage in detailed_erase_block_info debugfs file gcc-common.h: Update for GCC 10 HID: multitouch: add eGalaxTouch P80H84 support HID: alps: Add AUI1657 device ID HID: alps: ALPS_1657 is too specific; use U1_UNICORN_LEGACY instead scsi: qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV scsi: qla2xxx: Delete all sessions before unregister local nvme port configfs: fix config_item refcnt leak in configfs_rmdir() vhost/vsock: fix packet delivery order to monitoring devices aquantia: Fix the media type of AQC100 ethernet controller in the driver component: Silence bind error on -EPROBE_DEFER scsi: ibmvscsi: Fix WARN_ON during event pool release HID: i2c-hid: reset Synaptics SYNA2393 on resume x86/apic: Move TSC deadline timer debug printk gtp: set NLM_F_MULTI flag in gtp_genl_dump_pdp() HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K12A keyboard-dock ceph: fix double unlock in handle_cap_export() stmmac: fix pointer check after utilization in stmmac_interrupt USB: core: Fix misleading driver bug report platform/x86: asus-nb-wmi: Do not load on Asus T100TA and T200TA ARM: futex: Address build warning padata: Replace delayed timer with immediate workqueue in padata_reorder padata: initialize pd->cpu with effective cpumask padata: purge get_cpu and reorder_via_wq from padata_do_serial ALSA: iec1712: Initialize STDSP24 properly when using the model=staudio option ALSA: pcm: fix incorrect hw_base increase ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Xtreme ALSA: hda/realtek - Add more fixup entries for Clevo machines drm/etnaviv: fix perfmon domain interation apparmor: fix potential label refcnt leak in aa_change_profile apparmor: Fix aa_label refcnt leak in policy_update dmaengine: tegra210-adma: Fix an error handling path in 'tegra_adma_probe()' dmaengine: owl: Use correct lock in owl_dma_get_pchan() drm/i915/gvt: Init DPLL/DDI vreg for virtual display instead of inheritance. powerpc: Remove STRICT_KERNEL_RWX incompatibility with RELOCATABLE powerpc/64s: Disable STRICT_KERNEL_RWX media: fdp1: Fix R-Car M3-N naming in debug message Revert "net/ibmvnic: Fix EOI when running in XIVE mode" Revert "gfs2: Don't demote a glock until its revokes are written" staging: iio: ad2s1210: Fix SPI reading staging: greybus: Fix uninitialized scalar variable iio: sca3000: Remove an erroneous 'get_device()' iio: dac: vf610: Fix an error handling path in 'vf610_dac_probe()' misc: rtsx: Add short delay after exit from ASPM mei: release me_cl object reference ipack: tpci200: fix error return code in tpci200_register() rapidio: fix an error in get_user_pages_fast() error handling rxrpc: Fix a memory leak in rxkad_verify_response() x86/unwind/orc: Fix unwind_get_return_address_ptr() for inactive tasks iio: adc: stm32-adc: Use dma_request_chan() instead dma_request_slave_channel() iio: adc: stm32-adc: fix device used to request dma iio: adc: stm32-dfsdm: Use dma_request_chan() instead dma_request_slave_channel() iio: adc: stm32-dfsdm: fix device used to request dma rxrpc: Trace discarded ACKs rxrpc: Fix ack discard ubifs: fix wrong use of crypto_shash_descsize() i2c: fix missing pm_runtime_put_sync in i2c_device_probe evm:
[Kernel-packages] [Bug 1880388] Re: rpi3b+ becomes unresponsive after closing a program
Can you attach kern.log? ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1880388 Title: rpi3b+ becomes unresponsive after closing a program Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: New Bug description: I am running ROS2 on this raspberry pi 3B+ that is running as the main computer on a turtlebot3. There is two USB devices connected to the RPi, one is to communicate with the LIDAR and the other is to communicate with the control board, a OpenCR board. After "bringing the robot up" I open a new shell in tmux, and run `ros2 topic echo battery_state` which starts outputting ROS2 messages to the terminal. Upon ctrl+c'ing out of this, the system become unresponsive. I repeated this while connected to the serial console and captured the error messages that are being output. Issue I rose on github: https://github.com/ROBOTIS-GIT/turtlebot3/issues/593 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1011-raspi 5.4.0-1011.11 ProcVersionSignature: User Name 5.4.0-1011.11-raspi 5.4.34 Uname: Linux 5.4.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Sun May 24 10:31:26 2020 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) Serial console output: MMC: mmc@7e202000: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In:serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... Bus usb@7e98: scanning bus usb@7e98 for devices... 6 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found ## Info: input data size = 6 = 0x6 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 2603 bytes read in 6 ms (422.9 KiB/s) ## Executing script at 0240 8378005 bytes read in 364 ms (21.9 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 29426757 bytes read in 1262 ms (22.2 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 02609f2f Starting kernel ... [1.966598] spi-bcm2835 3f204000.spi: could not get clk: -517 ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory ext4 Thu Jan 1 00:00:07 UTC 1970 date: invalid date ' Wed Apr 1 17:23:46 2020' -.mount dev-mqueue.mount sys-kernel-debug.mount sys-kernel-tracing.mount kmod-static-nodes.service systemd-modules-load.service systemd-remount-fs.service ufw.service sys-fs-fuse-connections.mount sys-kernel-config.mount systemd-sysctl.service systemd-random-seed.service systemd-sysusers.service keyboard-setup.service systemd-tmpfiles-setup-dev.service swapfile.swap lvm2-monitor.service systemd-udevd.service systemd-journald.service systemd-udev-trigger.service systemd-journal-flush.service [ 14.813759] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 15.128676] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 15.174878] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 systemd-rfkill.service systemd-udev-settle.service netplan-wpa-wlan0.service multipathd.service [ 17.840942] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled systemd-fsckd.service snap-core18-1708.mount snap-core18-1753.mount snap-lxd-14808.mount snap-lxd-15066.mount snap-snapd-7267.mount systemd-fsck@dev-disk-by\x2dlabel-system\x2dboot.service boot-firmware.mount console-setup.service Mounting Arbitrary Executable File Formats File System... finalrd.service [ OK ] Finished Tell Plymouth To Write Out Runtime Data. [ OK ] Mounted Arbitrary Executable File Formats File System. proc-sys-fs-binfmt_misc.mount [ OK ] Finished Create Volatile Files and Directories. systemd-tmpfiles-setup.service Starting Network Time Synchronization... Starting Update UTMP about System Boot/Shutdown... [ OK ] Finished Enable support for…onal executable binary formats. binfmt-support.service [ OK ] Finished Update UTMP about System Boot/Shutdown. systemd-update-utmp.service [ OK ] Finished Load AppArmor profiles. apparmor.service Starting Load AppArmor prof… managed internally by snapd...
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => hugh chao (hugh712) -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Uns
[Kernel-packages] [Bug 1880334] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels
Is this a bug against the Focal 5.4 kernel or Bionic 4.15 or both? Could
you please adjust the bug title accordingly?
** Summary changed:
- Cloud-init causes potentially huge boot delays with 4.15 kernels Edit
+ Cloud-init causes potentially huge boot delays with 4.15 kernels
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1880334
Title:
Cloud-init causes potentially huge boot delays with 4.15 kernels
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
portion of bug report for bionic:
Newer 4.15 kernels contain the following fix for CVE-2018-1108:
43838a23a05fb ("random: fix crng_ready() test")
This causes cloud-init to stall for a potentially long time during
boot (waiting for entropy I presume). Google reported boot delays of
75 minutes.
I've tracked this down to the following import in templater.py which causes
the delay:
from jinja2 import Template as JTemplate
Which is called when cc_update_etc_hosts is imported.
NOTE: I'm experiencing this with focal repeatedly - just hangs
forever!
ubunutu 20.04 server - live
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1880334/+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 1882376] Re: Can't connect to external audio TaoTronics TT-BA07
Looks like an aptX device, which Ubuntu doesn't support audio on yet. But that should not prevent pairing... -- 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/1882376 Title: Can't connect to external audio TaoTronics TT-BA07 Status in bluez package in Ubuntu: New Bug description: From my iphone and chromebook I can see the external speakers plugged to a TaoTronics TT-BA07 bluetooth device. But from Ubuntu 20.04, the device doesn't appear listed in the settings. There is listed a deviced named "1" that, when connecting to, appears to be a sound device, but from the sound settings "test" buttons I can't get any sound to play. Any hints as to how I could triage this issue and collect more details? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 17:22:16 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1442 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:705a Lite-On Technology Corp. Integrated Camera Bus 001 Device 006: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 056a:5040 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FQCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=972ac4f9-34e5-4cf0-a6ba-2fa4322fd70a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-20 (17 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FQCTO1WW dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:B3:18:78:A6:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:43684 acl:117 sco:0 events:3823 errors:0 TX bytes:705943 acl:202 sco:0 commands:2991 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1882376/+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 1880125] Re: v3d driver clock problem forces OpenGL to use software rendering
** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1880125 Title: v3d driver clock problem forces OpenGL to use software rendering Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: New Bug description: release: 32-bit ubuntu 20.04 running on a raspberry pi 4 package: linux-raspi 5.4.0.1008.8 I made the configuration change described in: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862 and am running a kernel with v3d on a raspberry pi 4. Unfortunately, OpenGL is still not using the GPU; it's using the software renderer, llvmpipe. Setting LIBGL_DEBUG=verbose and running an OpenGL program shows that OpenGL can't open any /dev/dri/renderD* device. Looking in /dev/dri, there are no device files that begin with "render," indicating the v3d driver isn't starting up properly. Adding debugging code to the kernel, I find that: (1) drivers/gpu/drm/v3d/v3d_drv.c:v3d_platform_drm_probe() fails because it can't get a clock - devm_clk_get() returns an error. (2) in drivers/clk/clk.c:of_clk_get_hw(), the call to of_parse_clkspec() for the v3d driver yields a desired clock source of "firmware-clocks". (3) drivers/clk/clk.c:of_clk_get_hw_from_clkspec() fails because it can only find six clock providers (aux@7e215000, cprman@7e101000, clock@7ef0, clk-108M, clk-usb, clk-osc) none of which match the requested "firmware-clocks". The solution is to add a clock definition to the kernel source and a corresponding change to the device tree, but I'm not familiar enough with either to create that solution myself. In the raspbian kernel source tree, drivers/clk/bcm/clk-raspberrypi.c defines BCM2835_CLOCK_V3D, but there is no corresponding definition in the ubuntu source tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
I also experience this issue with 2 different Brand of Bluetooth Headset: ATH-CRK75BTH Edifier W200BT Problem also appears every time I switch bluetooh devices as INPUT device and OUTPUT using HEADSET Unit (HSP/HFP). Input indicator bar doesn't move and test OUTPUT doesn't produce any sound. When I tried video conferencing with my friend, he couldn't hear my voice and of course I can't hear him either. This is fresh installation using Ubuntu 20.04 (no prior Ubuntu or other Linux distro in this laptop). A2DP mode works normal. Currently I'm using internal laptop microphone and A2DP combination for video conferencing. Just now, I ran "sudo apt dist-upgrade, some packages were updated. But still not work for HSP/HFP mode output and Bluetooth mic input. -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1881097] Re: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached.
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- 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/1881097 Title: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached. Status in linux package in Ubuntu: Confirmed Bug description: Problem Description: Using Ubuntu 20.04 on a Thinkpad X1C7 machine. Speaker(F1) and Microphone(F4) Hotkey LED Light Stays ON/OFF when USB Headset is attached. - $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Ubuntu Software: 3.36.1 - Expected Result: When LED light of Speaker(F1)/Microphone (F4) hotkeys is ON/OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light state will change accordingly. Actual Result: 1. When LED light of Speaker(F1)/Microphone (F4) hotkeys is OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light will STAY OFF and remains in OFF State always on the duration that the USB headset is attached to the machine. 2. If LED light of Speaker(F1)/Microphone (F4) hotkeys is ON and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED will STAY ON and remains in ON State on the duration that the USB headset is attached to the machine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1410 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 18:48:04 2020 InstallationDate: Installed on 2020-05-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20U9SITR38 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ab59da99-085b-4f8d-af14-4fc4240a8f83 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR38 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR38:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR38:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR38 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881097/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
I also experience this issue with 2 different Brand of Bluetooth Headset: ATH-CRK75BTH Edifier W200BT Problem also appears every time I switch bluetooh devices as INPUT device and OUTPUT using HEADSET Unit (HSP/HFP). Input indicator bar doesn't move and test OUTPUT doesn't produce any sound. When I tried video conferencing with my friend, he couldn't hear my voice and of course I can't hear him either. This is fresh installation using Ubuntu 20.04 (no prior Ubuntu or other Linux distro in this laptop). A2DP mode works normal. Currently I'm using internal laptop microphone and A2DP combination for video conferencing. Just now, I ran "sudo apt dist-upgrade, some packages were updated. But still not work for HSP/HFP mode output and Bluetooth mic input. -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
Thanks for the verification @vali !! ** Tags removed: verification-needed-eoan verification-needed-focal verification-needed-xenial ** Tags added: verification-done-eoan verification-done-focal verification-done-xenial -- 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/1821434 Title: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: With efi-pstore activated I get the following panic in Linux 4.15.0-46 after resume: <6>[12007.593358] ata10.01: SATA link down (SStatus 0 SControl 330) <6>[12007.593469] ata10.02: hard resetting link <6>[12007.908353] ata10.02: SATA link down (SStatus 0 SControl 330) <6>[12007.911149] ata10.00: configured for UDMA/133 <0>[12007.972508] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40 <0>[12007.972508] <4>[12007.972515] CPU: 2 PID: 230 Comm: scsi_eh_9 Tainted: P OE 4.15.0-46-generic #49-Ubuntu <4>[12007.972517] Hardware name: System manufacturer System Product Name/A320M-C, BIOS 1001 12/10/2017 <4>[12007.972518] Call Trace: <4>[12007.972525] dump_stack+0x63/0x8b <4>[12007.972530] panic+0xe4/0x244 <4>[12007.972533] ? sata_pmp_eh_recover+0xa2b/0xa40 <4>[12007.972536] __stack_chk_fail+0x19/0x20 <4>[12007.972538] sata_pmp_eh_recover+0xa2b/0xa40 <4>[12007.972543] ? ahci_do_softreset+0x260/0x260 [libahci] <4>[12007.972545] ? ahci_do_hardreset+0x140/0x140 [libahci] <4>[12007.972547] ? ata_phys_link_offline+0x60/0x60 <4>[12007.972549] ? ahci_stop_engine+0xc0/0xc0 [libahci] <4>[12007.972552] sata_pmp_error_handler+0x22/0x30 <4>[12007.972554] ahci_error_handler+0x45/0x80 [libahci] <4>[12007.972556] ata_scsi_port_error_handler+0x29b/0x770 <4>[12007.972558] ? ata_scsi_cmd_error_handler+0x101/0x140 <4>[12007.972559] ata_scsi_error+0x95/0xd0 <4>[12007.972562] ? scsi_try_target_reset+0x90/0x90 <4>[12007.972563] scsi_error_handler+0xd0/0x5b0 <4>[12007.972566] kthread+0x121/0x140 <4>[12007.972567] ? scsi_eh_get_sense+0x200/0x200 <4>[12007.972569] ? kthread_create_worker_on_cpu+0x70/0x70 <4>[12007.972572] ret_from_fork+0x22/0x40 <0>[12007.972591] Kernel Offset: 0xcc0 from 0x8100 (relocation range: 0x8000-0xbfff) I have also tried 4.18 and 4.20 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ but I get the same problem. The problem seems to be related to an add-on PCI-E SATA card: 22:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) When disks are connected to the card port -> panic, no disks connected -> no panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821434/+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 1882483] Re: ThinkPad P1 Gen 2 does not boot
nvidia drivers are not loaded, please install nvidia-driver-440 and try again. -- 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/1882483 Title: ThinkPad P1 Gen 2 does not boot Status in linux package in Ubuntu: Confirmed Bug description: Hi, Kernels > 5.4.0-28 can not boot Ubuntu 20.04 when *NO* HDMI monitor plugged. Kernels > 5.4.0-28 can boot Ubuntu 20.04 when HDMI monitor plugged. There is also a separate problem: No wake up after hibernation, only repeated sound without screen image - physical shutdown is only workaround I have. Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: igor 2358 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 05:37:59 2020 Dependencies: InstallationDate: Installed on 2020-04-01 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882483/+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 1856434] Re: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Thanks Joel, the firmware you posted worked for us. I will note we have the HBA330 mini, which has it's own distinct upgrade file as opposed to the regular HBA330. HBA330 mini: https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=124x2 i'm still a bit puzzled why a firmware update fixed this, since our rhel7 servers did not experience the issue, only Ubuntu (hence i was expecting a kernel driver issue/regression). -- 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/1856434 Title: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Status in linux package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) unknown 3) no error 4) error in log app. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: htpc 9157 F pulseaudio /dev/snd/controlC1: htpc 9157 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (48 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lxcbr0no wireless extensions. lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H 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.3.0-23-generic root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: wayland-session eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6b dmi.board.name: GA-MA780G-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA780G-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856434/+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 1871562] Re: [ThinkPad P1 and ThinkPad X1 Extreme] System got hang during the first boot.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871562 Title: [ThinkPad P1 and ThinkPad X1 Extreme] System got hang during the first boot. Status in linux package in Ubuntu: Expired Bug description: [Summary] System got hang during the first boot. [Steps to reproduce] 1. Install Ubuntu 20.04 beta image on ThinkPad X1 Extreme or P1 2. Unplug USB Live CD 3. Boot system and verify the result [Expected result] System boots up smoothly [Actual result] System got hang during the first boot. [Failure rate] 100% [Note] The ThinkPad P1 and ThinkPad X1 Extreme are I+N configs Even though system installed successfully in 'Safe mode', when user want to boot it up, system will got hang always. There is a workaround: 1. Install Ubuntu 20.04 beta image on ThinkPad X1 Extreme or P1 2. Unplug USB Live CD 3. Boot system and enter grub 4. Add the kernel parameter 'nomodeset' and press 'Ctrl+X' 5. After log in successfully, install nvidia display driver 6. After the driver installed, reboot system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871562/+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 1882480] Re: nvme driver issue causing massive system lag on resume from suspend
** Description changed: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. + UPDATE: this would appear to be happening only when I run my CPU in + powersave mode (reduced speed and 4-6 vCPUs disabled). + release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux also tried kernel: Linux Dapple 5.4.0-34-generic #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (developer repository) - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- 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/1882480 Title: nvme driver issue causing massive system lag on resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. UPDATE: this would appear to be happening only when I run my CPU in powersave mode (reduced speed and 4-6 vCPUs disabled). release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux also tried kernel: Linux Dapple 5.4.0-34-generic #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (developer repository) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersi
[Kernel-packages] [Bug 1882478] Re: smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1882478 [Impact] Intel Skylake server processors and onward have a different Last Level Cache (LLC) topology than earlier processors, and such processors have a new feature called Sub-NUMA-Clustering (SNC) which is similar to the existing Cluster-On-Die (CoD) feature earlier server processors has. Sub-NUMA-Clustering divides the system into two "slices", each of which are allocated half the CPU cores, half the Last Level Cache and one memory controller. Each slice is enumerated as a NUMA node. The difference between Sub-NUMA-Clustering and Cluster-On-Die is how the Last Level Cache is exposed to each NUMA node. CoD had the same cache line present in each half of the LLC. In SNC, each cache line is only present in its respective slice. Because of this, the semantics around accessing LLC changes, with a process accessing NUMA-local memory only seeing half the LLC capacity. On systems with Sub-NUMA-Clustering enabled, on the Xenial 4.4 and Bionic 4.15 kernels we see the following oops during NUMA node enumeration: node #0, CPUs: #1 #2 #3 #4 #5 #6 node #1, CPUs: #7 sched: CPU #7's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. WARNING: CPU: 7 PID: 0 at /build/linux-hwe-F5opqf/linux-hwe-4.15.0/arch/x86/kernel/smpboot.c:375 topology_sane.isra.4+0x6c/0x70 Modules linked in: CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.15.0-47-generic #50~16.04.1-Ubuntu Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 10/02/2018 RIP: 0010:topology_sane.isra.4+0x6c/0x70 Call Trace: set_cpu_sibling_map+0x153/0x540 start_secondary+0xb2/0x200 secondary_startup_64+0xa5/0xb0 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs This was with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10. The oops happens because topology_sane() checks to see if the Last Level Cache line matches across different CPUs, which it no longer does. [Fix] The fix comes in the form of the following upstream commit, which landed in Linux 4.17: commit 1340ccfa9a9afefdbab90d7935d4ed19817e37c2 Author: Alison Schofield Date: Fri Apr 6 17:21:30 2018 -0700 Subject: x86,sched: Allow topologies where NUMA nodes share an LLC Link: https://github.com/torvalds/linux/commit/1340ccfa9a9afefdbab90d7935d4ed19817e37c2 The commit adds a check for this particular family of Intel processors, and if the CPU family matches, it simply skips the check to topology_sane(). The commit needs minor backports to Xenial 4.4 and Bionic 4.15, with the only remarks being re-arranging #includes and small context fixups. [Testcase] Unfortunately, this is hardware specific. To test this, you need a Intel Skylake server processor which supports Sub-NUMA-Clustering. We have a customer with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10 that has successfully tested the below test kernels, with good results. Xenial 4.4 ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-ga Xenial 4.15 HWE ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-hwe Running the test kernel, the oops does not reproduce: smp: Bringing up secondary CPUs ... x86: Booting SMP configuration: node #0, CPUs: #1 NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. #2 #3 #4 #5 #6 node #1, CPUs: #7 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs smpboot: Max logical packages: 1 smpboot: Total of 28 processors activated [Regression Potential] The commit modifies a small section of smpboot code, which every machine will execute on boot. The majority of the commit breaks up a large if statement into smaller blocks than it was previously, and adds an extra if statement to check for a specific processor family. If a regression were to occur, some machines would or would not make their calls to topology_sane(), which in the worst case, would result in a oops message and slightly degraded performance. The system would still function normally. The commit has been present since 4.17-rc2 and is present in Eoan and Focal. There are no fixup commits, and no additional processor families have been added since. Because of the small re-arrangement in logic, and the addition of a - processor family check, these changes a fairly minor, and I don't think - it will cause any regressions. + processor family check, these changes are fairly minor, and I don't + think it will cause any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.laun
[Kernel-packages] [Bug 1882483] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882483 Title: ThinkPad P1 Gen 2 does not boot Status in linux package in Ubuntu: Confirmed Bug description: Hi, Kernels > 5.4.0-28 can not boot Ubuntu 20.04 when *NO* HDMI monitor plugged. Kernels > 5.4.0-28 can boot Ubuntu 20.04 when HDMI monitor plugged. There is also a separate problem: No wake up after hibernation, only repeated sound without screen image - physical shutdown is only workaround I have. Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: igor 2358 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 05:37:59 2020 Dependencies: InstallationDate: Installed on 2020-04-01 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882483/+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 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
Seen on ThinkPad E495. Updated BIOS to 1.16 -- good but did NOT solve this particular issue. Still getting the boot-to-black issue on battery power, on a random basis. Attempting the workaround from Alexander in #3 and #5. -- 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/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API Status in linux package in Ubuntu: Confirmed Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45 kernel: Call Trace: апр 05 20:46:45 kernel: amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu] апр 05 20:46:45 kernel: amdgpu_job_timedout+0x103/0x130 [amdgpu] апр 05 20:46:45 kernel: drm_sched_job_timedout+0x
[Kernel-packages] [Bug 1882483] [NEW] ThinkPad P1 Gen 2 does not boot
Public bug reported: Hi, Kernels > 5.4.0-28 can not boot Ubuntu 20.04 when *NO* HDMI monitor plugged. Kernels > 5.4.0-28 can boot Ubuntu 20.04 when HDMI monitor plugged. There is also a separate problem: No wake up after hibernation, only repeated sound without screen image - physical shutdown is only workaround I have. Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: igor 2358 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 05:37:59 2020 Dependencies: InstallationDate: Installed on 2020-04-01 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882483 Title: ThinkPad P1 Gen 2 does not boot Status in linux package in Ubuntu: New Bug description: Hi, Kernels > 5.4.0-28 can not boot Ubuntu 20.04 when *NO* HDMI monitor plugged. Kernels > 5.4.0-28 can boot Ubuntu 20.04 when HDMI monitor plugged. There is also a separate problem: No wake up after hibernation, only repeated sound without screen image - physical shutdown is only workaround I have. Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: igor 2358 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 05:37:59 2020 Dependencies: InstallationDate: Installed on 2020-04-01 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882483/+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 1882480] Re: nvme driver issue causing massive system lag on resume from suspend
** Description changed: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux + also tried kernel: Linux Dapple 5.4.0-34-generic #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (developer repository) + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jurgen 1998 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: - lono wireless extensions. - - enp10s0 no wireless extensions. + lono wireless extensions. + + enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-33-generic N/A - linux-backports-modules-5.4.0-33-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-33-generic N/A + linux-backports-modules-5.4.0-33-generic N/A + linux-firmware1.187 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- 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/1882480 Title: nvme driver issue causing massive system lag on resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux also tried kernel: Linux Dapple 5.4.0-34-generic #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (developer repository) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
$ rmadison linux When groovy jumps to 5.7, it's time to change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808418 Title: Thinkpad T430u won't boot without noapic workaround Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 - 4.20.0-rc7 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. This bug seems very similar to what's described here for the Thinkpad E485/E585: https://evilazrael.de/node/401 I'll attach screenshots of various times I've encountered this bug over the last year. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy linux-image-4.15.0-42-generic linux-image-4.15.0-42-generic: Installed: 4.15.0-42.45 Candidate: 4.15.0-42.45 Version table: *** 4.15.0-42.45 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882480] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882480 Title: nvme driver issue causing massive system lag on resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+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 1882480] Re: nvme driver issue causing massive system lag on resume from suspend
I am including the output of the dmesg command as ran immediately after resume from suspend - it shows the stack trace I am referring to in my bug report. ** Attachment added: "dmesg_2020-06-08_04:12.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+attachment/5381446/+files/dmesg_2020-06-08_04%3A12.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/1882480 Title: nvme driver issue causing massive system lag on resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882480/+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 1882480] [NEW] nvme driver issue causing massive system lag on resume from suspend
Public bug reported: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b0aa93b-fb72-4ce6-a28a-0569be4848ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882480 Title: nvme driver issue causing massive system lag on resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: When I resume from suspend, my system initially appears to be frozen. The screen is black and/or the input devices are not working. After several minutes, I can switch to a console (and then to the desktop) but the system is under full load, to the point that even trivial commands will take up to three minutes to execute. The only way out of this situation is to do a reboot. I see that dmesg is showing an NVME related stack trace and then the repeating message "timeout, completion polled". I ran into the same issue a few months ago when I started using my current motherboard (ASUS Prime x470-PRO). It got solved by flashing my BIOS to the latest version. ASUS have not put out any newer since then so I guess this will require a kernel fix. release: ubuntu 20.04 kernel: Linux Dapple 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jurgen 1998 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 04:43:36 2020 InstallationDate: Installed on 2020-04-05 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp10s0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=
[Kernel-packages] [Bug 1882478] [NEW] smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/1882478 [Impact] Intel Skylake server processors and onward have a different Last Level Cache (LLC) topology than earlier processors, and such processors have a new feature called Sub-NUMA-Clustering (SNC) which is similar to the existing Cluster-On-Die (CoD) feature earlier server processors has. Sub-NUMA-Clustering divides the system into two "slices", each of which are allocated half the CPU cores, half the Last Level Cache and one memory controller. Each slice is enumerated as a NUMA node. The difference between Sub-NUMA-Clustering and Cluster-On-Die is how the Last Level Cache is exposed to each NUMA node. CoD had the same cache line present in each half of the LLC. In SNC, each cache line is only present in its respective slice. Because of this, the semantics around accessing LLC changes, with a process accessing NUMA-local memory only seeing half the LLC capacity. On systems with Sub-NUMA-Clustering enabled, on the Xenial 4.4 and Bionic 4.15 kernels we see the following oops during NUMA node enumeration: node #0, CPUs: #1 #2 #3 #4 #5 #6 node #1, CPUs: #7 sched: CPU #7's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. WARNING: CPU: 7 PID: 0 at /build/linux-hwe-F5opqf/linux-hwe-4.15.0/arch/x86/kernel/smpboot.c:375 topology_sane.isra.4+0x6c/0x70 Modules linked in: CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.15.0-47-generic #50~16.04.1-Ubuntu Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 10/02/2018 RIP: 0010:topology_sane.isra.4+0x6c/0x70 Call Trace: set_cpu_sibling_map+0x153/0x540 start_secondary+0xb2/0x200 secondary_startup_64+0xa5/0xb0 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs This was with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10. The oops happens because topology_sane() checks to see if the Last Level Cache line matches across different CPUs, which it no longer does. [Fix] The fix comes in the form of the following upstream commit, which landed in Linux 4.17: commit 1340ccfa9a9afefdbab90d7935d4ed19817e37c2 Author: Alison Schofield Date: Fri Apr 6 17:21:30 2018 -0700 Subject: x86,sched: Allow topologies where NUMA nodes share an LLC Link: https://github.com/torvalds/linux/commit/1340ccfa9a9afefdbab90d7935d4ed19817e37c2 The commit adds a check for this particular family of Intel processors, and if the CPU family matches, it simply skips the check to topology_sane(). The commit needs minor backports to Xenial 4.4 and Bionic 4.15, with the only remarks being re-arranging #includes and small context fixups. [Testcase] Unfortunately, this is hardware specific. To test this, you need a Intel Skylake server processor which supports Sub-NUMA-Clustering. We have a customer with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10 that has successfully tested the below test kernels, with good results. Xenial 4.4 ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-ga Xenial 4.15 HWE ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-hwe Running the test kernel, the oops does not reproduce: smp: Bringing up secondary CPUs ... x86: Booting SMP configuration: node #0, CPUs: #1 NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. #2 #3 #4 #5 #6 node #1, CPUs: #7 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs smpboot: Max logical packages: 1 smpboot: Total of 28 processors activated [Regression Potential] The commit modifies a small section of smpboot code, which every machine will execute on boot. The majority of the commit breaks up a large if statement into smaller blocks than it was previously, and adds an extra if statement to check for a specific processor family. If a regression were to occur, some machines would or would not make their calls to topology_sane(), which in the worst case, would result in a oops message and slightly degraded performance. The system would still function normally. The commit has been present since 4.17-rc2 and is present in Eoan and Focal. There are no fixup commits, and no additional processor families have been added since. Because of the small re-arrangement in logic, and the addition of a processor family check, these changes a fairly minor, and I don't think it will cause any regressions. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Tags: sts ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu
[Kernel-packages] [Bug 1878544] Re: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub)
@Victor, Sorry, it's my fault. please wait the next released(>= 5.4.0-34) -- 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/1878544 Title: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub) Status in linux package in Ubuntu: In Progress Bug description: Asus Zenbook Flip S (UX-370UAR). Intel Core i7-8550U CPU). The X freezes and doesnt even allow to start a console session. Only happening on Ubuntu 18.04 and 20.04. Does not happen in the same computer under Ubuntu 16.04 or Windows 10. Can be replicated easily. Every time I plug/unplug the power USB-C or the USB-c hub. Mostly, on any interaction with the USB-c or I/O ports. If I plug/unplug the USB-c without X in a console session (CTRL+ALT+F3) I get the following: BUG: kernel NULL point dereference, address: 0080 ... Workqueue: events ucsi_connector_change [typec_usci] RIP: 0010:ucsi_displayport_remove_partner+0xe/0x30 [typec_usci] ... Find a picture of the full error attached 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: vks20 1808 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:46:49 2020 InstallationDate: Installed on 2020-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. UX370UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=acc6d87c-574b-4c1e-8e8f-e75c1e9ff1fc 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: 10/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX370UAR.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX370UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.311:bd10/15/2019:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX370UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878544/+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 1560094] Re: Starting bluez service is denied
In progress? ** Changed in: bluez (Ubuntu) Status: In Progress => Incomplete ** Changed in: bluez (Ubuntu) Assignee: Scott Sweeny (ssweeny) => (unassigned) -- 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/1560094 Title: Starting bluez service is denied Status in bluez package in Ubuntu: Incomplete Bug description: If snappy core is updated in the background (on Raspberry Pi 2), and then bluez installed, starting the service is failing. Denials: [ 45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0 [ 46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 [ 46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000 [ 46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0 [ 46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 [ 46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000 [ 46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 sysc0 [ 46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" operation="mknod" profile="bluez5_bluez_5.37-2-armhf" name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2 If trying to start bluetootctl: [ 582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0 [bluetooth]# ubuntu@localhost:~$ snappy list NameDate Version Developer bluez5 2016-02-04 5.37-2-armhf canonical canonical-pi2 2016-02-02 3.0 canonical canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical ubuntu-core 2016-03-08 16.04.0-15.armhf canonical ubuntu@localhost:~$ ubuntu@localhost:~$ snappy info release: core/rolling architecture: armhf frameworks: bluez5.canonical apps: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+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 1880441] Re: nvidia-driver-390 - brightness control not working for NVIDIA GeForce GTX 670 mx
** Description changed: The same case on Ubuntu 20.04 as on the start of 16.04 for my ASUS Notebook (G75VX): - No brightness control over the Keyboard - No brightness control over the systemsettings - - Screenbrightness what ever i try still on 100% + - Screenbrightness what ever i try is still on 100% - - The Problem is the same at my second System Kubuntu 20.04. - + The Problem is the same at my second System Kubuntu 20.04; + with the nouveau driver the adjustment over the system settings is working. Here some details about my System: - lspci -nnk | grep -i VGA -A2 + lspci -nnk | grep -i VGA -A2 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104M [GeForce GTX 670MX] [10de:11a1] (rev a1) - Subsystem: ASUSTeK Computer Inc. GK104M [GeForce GTX 670MX] [1043:21ab] - Kernel driver in use: nvidia + Subsystem: ASUSTeK Computer Inc. GK104M [GeForce GTX 670MX] [1043:21ab] + Kernel driver in use: nvidia - grep nvidia_drv.so /var/log/Xorg.0.log + grep nvidia_drv.so /var/log/Xorg.0.log [13.808] (II) Loading /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so - dpkg -l nvidia* + dpkg -l nvidia* Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ - Halb installiert/Trigger erWartet/Trigger anhängig + Halb installiert/Trigger erWartet/Trigger anhängig |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) ||/ Name Version Architektur Beschreibung +++----=> un nvidia-304 (keine Beschreibung vorhanden) un nvidia-340 (keine Beschreibung vorhanden) un nvidia-384 (keine Beschreibung vorhanden) un nvidia-390 (keine Beschreibung vorhanden) un nvidia-common(keine Beschreibung vorhanden) ii nvidia-compute-utils-390 390.132-0ubuntu2 amd64NVIDIA compute utilities un nvidia-dkms-390 (keine Beschreibung vorhanden) ii nvidia-driver-390390.132-0ubuntu2 amd64NVIDIA driver metapackage un nvidia-driver-binary (keine Beschreibung vorhanden) un nvidia-kernel-common (keine Beschreibung vorhanden) ii nvidia-kernel-common-390 390.132-0ubuntu2 amd64Shared files used with the kernel module un nvidia-kernel-source (keine Beschreibung vorhanden) ii nvidia-kernel-source-390 390.132-0ubuntu2 amd64NVIDIA kernel source package un nvidia-legacy-304xx-vdpau-driver (keine Beschreibung vorhanden) un nvidia-legacy-340xx-vdpau-driver (keine Beschreibung vorhanden) un nvidia-libopencl1-dev(keine Beschreibung vorhanden) un nvidia-opencl-icd(keine Beschreibung vorhanden) un nvidia-persistenced (keine Beschreibung vorhanden) ii nvidia-prime 0.8.14 all Tools to enable NVIDIA's Prime ii nvidia-settings 440.64-0ubuntu1 amd64Tool for configuring the NVIDIA graphics driv> un nvidia-settings-binary (keine Beschreibung vorhanden) un nvidia-smi (keine Beschreibung vorhanden) un nvidia-utils (keine Beschreibung vorhanden) ii nvidia-utils-390 390.132-0ubuntu2 amd64NVIDIA driver support binaries un nvidia-vdpau-driver (keine Beschreibung vorhanden) -- 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/1880441 Title: nvidia-driver-390 - brightness control not working for NVIDIA GeForce GTX 670 mx Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: The same case on Ubuntu 20.04 as on the start of 16.04 for my ASUS Notebook (G75VX): - No brightness control over the Keyboard - No brightness control over the systemsettings - Screenbrightness what ever i try is still on 100% The Problem is the same at my second System Kubuntu 20.04; with the nouveau driver the adjustment over the system settings is working. Here some details about my System: lspci -nnk | grep -i VGA -A2 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104M [GeForce GTX 670MX] [10de:11a1] (rev a1) Subsystem: ASUSTeK Computer Inc. GK104M [GeForce GTX 670MX] [1043:21
[Kernel-packages] [Bug 1879082] Re: Kernel reporting 100% battery, always
$ ls /sys/class/power_supply/ ACAD BAT1 acpi log attached. Sorry for the wait, I neglected to bring this laptop with me. I now have access :) ** Attachment added: "acpi.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879082/+attachment/5381390/+files/acpi.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879082 Title: Kernel reporting 100% battery, always Status in linux package in Ubuntu: Confirmed Bug description: Running Kubuntu 20.04: Regardless of whether the laptop is plugged- in, or the battery state (Even just before dying) the reported percentage is incorrect and the system believes it is plugged in at all times (see upower -d below, it is always the same). $ cat /proc/version_signature Ubuntu 5.4.0-29.33-generic 5.4.30 $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal $ uname -a Linux Vergil 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ upower -d Device: /org/freedesktop/UPower/devices/line_power_ACAD native-path: ACAD power supply: yes updated: Sat 16 May 2020 12:35:46 PM CDT (909 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT1 native-path: BAT1 vendor: TOSHIBA model:PABAS0241231 serial: power supply: yes updated: Sat 16 May 2020 12:49:47 PM CDT (68 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: fully-charged warning-level: none energy: 4294.84 Wh energy-empty:0 Wh energy-full: 4294.84 Wh energy-full-design: 4294.84 Wh energy-rate: 0 W voltage: 65.535 V percentage: 100% capacity:100% technology: lithium-ion icon-name: 'battery-full-charged-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Sat 16 May 2020 12:32:09 PM CDT (1126 seconds ago) has history: no has statistics: no battery present: yes state: fully-charged warning-level: none energy: 4294.84 Wh energy-full: 4294.84 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-full-charged-symbolic' Daemon: daemon-version: 0.99.11 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep 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/controlC1: sperger1191 F pulseaudio /dev/snd/controlC0: sperger1191 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 16 12:41:59 2020 InstallationDate: Installed on 2020-03-11 (65 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: TOSHIBA Satellite C55-B ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-10 (5 days ago) dmi.bios.date: 07/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.30 dmi.board.asset.tag: * dmi.board.name: ZSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr1.30:bd07/19/2014:svnTOSHIBA:pnSatelliteC55-B:pvrPSCLUU-05M07V:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: Satellite C55-B dmi.product.sku: PSCLUU dmi.product.version: PSCLUU-05M07V dmi.sys.vendor: TOSHIBA To manage noti
[Kernel-packages] [Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
PARTIAL FIX: downgrade the kernel. I can confirm that everything seems to return to normal if you use GRUB2 to select Linux 4.15.0-101-generic as the kernel. I edited /etc/default/grub to - give a boot menu with a reasonable timeout - use the last selected kernel as default ** Description changed: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 - I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external - HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. + I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external + HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not on the internal monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. - The problem seems to be similar to this bug: + The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: david 2012 F pulseaudio - /dev/snd/controlC1: david 2012 F pulseaudio - /dev/snd/controlC0: david 2012 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: david 2012 F pulseaudio + /dev/snd/controlC1: david 2012 F pulseaudio + /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: - linux-restricted-modules-5.4.0-33-generic N/A - linux-backports-modules-5.4.0-33-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-33-generic N/A + linux-backports-modules-5.4.0-33-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. -- 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/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: Confirmed Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not on the internal monitor. In MATE it was a real problem because the pa
[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
I attempted the process you describe, however I cannot find any kernel version which allows for the audio output to work within Ubuntu 20.04. To reiterate, when testing the system with Linux Mint 19.3 with kernel version 5.3.0-51 #44-18.04.2-Ubuntu sound works properly. I used these instructions --> https://wiki.ubuntu.com/Kernel/MainlineBuilds to install these kernel versions from --> http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.20.17 5.0.21 5.1.21 5.2.21 5.3 5.3.1 5.3.2 5.3.2 5.3.4 5.3.5 5.3.6 5.3.7 5.3.8 5.3.9 5.3.18 5.4.45 5.5.19 5.6.17 5.7 5.7.1 None of these kernel versions allowed for the audio output device within the system to be detected from within Ubuntu 20.04. Only the 'dummy' audio output shows within settings. The system is dual-booting Ubuntu 20.04 and Linux Mint 19.3. When I reboot into Linux Mint 19.3, the audio output is recognized and works properly. Please let me know if I can provide more information from either the Ubuntu installation or Linux Mint installation to help troubleshoot the problem and I will be happy to do so. I can also erase the boot drive and reinstall Windows 10 if that helps. Thanks again for all of your help! -- 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/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modali
[Kernel-packages] [Bug 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
I today experienced a hang using the v5.7 kernel above without the "nomodeset" kernel parameter. The hang occurred before the LUKS password prompt. I will attach a screenshot of the message displayed at the time of the hang. I will revert to the v5.4 GA kernel and reapply the "nomodeset" parameter. -- 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/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 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/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet 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: Upgraded to focal on 2020-04-24 (15 days ago) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+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 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
This seems to be a kernel issue: when I switched back to kernel 4.15 in GRUB2, the problems seems to go away. Checking on it. -- 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/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: Confirmed Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+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 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
Hang ** Attachment added: "Screenshot of hang from 2020-06-07. (v5.7 without nomodeset)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+attachment/5381387/+files/IMG_3217.JPG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 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/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet 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: Upgraded to focal on 2020-04-24 (15 days ago) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+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 1882388] Re: Touchpad recognised as generic mouse
I have realised that if I restart the mouse twice in a row, the touchpad is recognised as such and starts working for a period of time. ```sudo modprobe -r psmouse``` ```sudo modprobe psmouse``` Then, it is recognised back as a generic mouse and stops working. -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. I'm new in Ubuntu and I don't know much... ```uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN54WW:bd06/13/2017:svnLENOVO:pn80NV:pvrLenovoideapadY700-15IS
[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
The power-off bug can be fixed by installing .56 kernel. I'm using the following PPA to get that release until it makes into official repos: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed. -- 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/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388] do_syscall_64+0x57/0x190 Oct 21 10:57:26 pc kernel: [ 9475.309392] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b Oct 21 10:57:26
[Kernel-packages] [Bug 1882447] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882447 Title: Touchpad and sound doesn't work after the kernel update Status in linux package in Ubuntu: Confirmed Bug description: My laptop: Lenovo IdeaPad 5 14IIL05 This appeared after update, that I had made 06.06.2020. Sound is disappeared too. Then I reinstall Ubuntu and don't upgrade it. But touchpad doesn't work. And doesn't detect in /proc/bus/input/devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leschev2331 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 21:10:47 2020 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=b86f12a0-6a3e-48db-a62a-5246a95afc77 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN22WW(V1.08) 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:bvrDSCN22WW(V1.08):bd03/06/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/ubuntu/+source/linux/+bug/1882447/+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 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
I can confirm that #61 removes the bug. I'm running Kubuntu 18.04 with a hwe kernel 5.3.0-51-generic #44~18.04.2-Ubuntu. (Not 5.3.0-53 because it contains a power off bug.) Great! Now I hope it will find a way to an "official" update. -- 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/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388] do_syscall_64+0x57/0x190 Oct 21 10:57:26 pc kernel: [ 9475.309392] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1b
[Kernel-packages] [Bug 1882447] [NEW] Touchpad and sound doesn't work after the kernel update
Public bug reported: My laptop: Lenovo IdeaPad 5 14IIL05 This appeared after update, that I had made 06.06.2020. Sound is disappeared too. Then I reinstall Ubuntu and don't upgrade it. But touchpad doesn't work. And doesn't detect in /proc/bus/input/devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leschev2331 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 21:10:47 2020 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=b86f12a0-6a3e-48db-a62a-5246a95afc77 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN22WW(V1.08) 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:bvrDSCN22WW(V1.08):bd03/06/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 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "/proc/bus/input/devices" https://bugs.launchpad.net/bugs/1882447/+attachment/5381321/+files/devices -- 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/1882447 Title: Touchpad and sound doesn't work after the kernel update Status in linux package in Ubuntu: Confirmed Bug description: My laptop: Lenovo IdeaPad 5 14IIL05 This appeared after update, that I had made 06.06.2020. Sound is disappeared too. Then I reinstall Ubuntu and don't upgrade it. But touchpad doesn't work. And doesn't detect in /proc/bus/input/devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leschev2331 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 21:10:47 2020 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=b86f12a0-6a3e-48db-a62a-5246a95afc77 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN22WW(V1.08) 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:bvrDSCN22WW(V1.08):bd03/06/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/ubuntu/+source/linux/+bug/1882447/+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 1166442] Re: Elantech clickpad/touchpad lacks multitouch features.
I have similar issue on my Lenovo ideapad Y700-17ISK; Ubuntu 20.04 I have since 2 or 3 times the correct touchpad recognised, but after a short time, it changes to PS/2 Generic Mouse, and I have no functionalities at all. I have a different bug, reported, as I don't know if the issue it's the same or not... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388 -- 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/1166442 Title: Elantech clickpad/touchpad lacks multitouch features. Status in linux package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux package in Arch Linux: New Bug description: Newer versions of the Elantech multitouch trackpad are not fully supported in Linux. These appear in many of the newer Samsung laptops, for example. elantech.c in the kernel needs to be updated to support these models (up to v7 perhaps?) This bug is confirmed to affect a range of samsung laptops running Ubuntu 12.04 and newer, ArchLinux, Fedora and also affects the current (3.9) upstream kernel. A dkms package was produced in 2011 (see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/681904/comments/64) which may fix certain older laptops affected by this issue, but doesn't fix newer models. == Original Report == Hello, So far I've been having a problem with my Elantech multitouch trackpad in Linux. Basically all i get is right click, left click, and tap to click, along with basic movement. The problem seems to be rooted in improper detection of the trackpad, likely b/c its a new revision or whatnot. Of note is that working elantech trackpads of the past in forums i scouted through show up as "ETPS/2 Elantech Touchpad". Mine just shows up in xinput as "PS/2 Elantech Touchpad". I think this might be a simple fix in the end, just improper detection, I hope. For reference, I've tried kernel 3.5 on Ubuntu 12.10 and kernel 3.8.0-17 on Ubuntu 13.04 thus far, with all combinations of psmouse. -- What's expected: touchpad multitouch support What happened: basic touchpad support Laptop mode: Samsung Series 7 NP780 series Ubuntu distro(s) tested: Ubuntu 12.10, Ubuntu 13.04 Kernels used: 3.5 signed (Ubuntu 12.10 default), 3.8.0-16, 3.8.0-17 signed Other tests: Attempted using psmouse-elantech-v6, psmouse-alps, and psmouse-alps-dst. No improvements so removed. synclient -l reports "Couldn't find synaptics properties. No synaptics driver loaded?" -- See attached for more info. Ask anything you need! --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gscoppino 2272 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f683852c-7aa0-4f32-8b86-56f0a018989d InstallationDate: Installed on 2013-04-06 (3 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 770Z5E/780Z5E/870Z5E/880Z5E MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed root=UUID=cf39fbe5-c8ff-4d16-b11e-a41a4f3ae955 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-17-generic N/A linux-backports-modules-3.8.0-17-generic N/A linux-firmware1.104 StagingDrivers: rts5139 Tags: raring staging Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-06 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03ABU.139.130226.SK dmi.board.asset.tag: No Asset Tag dmi.board.name: NP780Z5E-S01UB dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03ABU.139.130226.SK:bd02/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn770Z5E/780Z5E/870Z5E/880Z5E:pvrP03ABU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP780Z5E-S01UB:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
** Summary changed: - Touchpad recognised as Logitech mouse + Touchpad recognised as generic mouse -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. I'm new in Ubuntu and I don't know much... ```uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN54WW:bd06/13/2017:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadY700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80NV dmi.product.sku: LENOVO
[Kernel-packages] [Bug 1690085]
I've also found https://www.reddit.com/r/Amd/comments/8yzvxz/ryzen_c6_state_sleep_power_supply_common_current/e33lc6s/ which seems to be promising. It is, however, appalling to see this kind of response from AMD and I'm quite sure this is my last AMD system. I'm currently testing my system with "Deep sleep" enabled and will report if its stable. The "Typical current idle" fix certainly didn't fix things for me, and in any case, the best I can say about that "fix" is that its an ugly hack and not really a fix from AMD. I'm bewildered to see so many reports on this thread and no word from AMD. I'm also convinced they are aware of this issue and are doing nothing but propose cheap hacks. AMD has also approved my RMA request and I'll send this processor back if the "deep sleep" "fix" doesn't fix things from me. If the RMA'd processor doesn't work, I'm going to sell. -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used",
[Kernel-packages] [Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
I left the machine on a while, and the internal monitor came on while I was gone for about an hour. ??? -- 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/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: Confirmed Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+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 1882422] Re: xorg fails to load nvidia driver on switching to greeter / black screen blinking cursor with lightdm light-locker
** Package changed: ubuntu => nvidia-graphics-drivers-435 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1882422 Title: xorg fails to load nvidia driver on switching to greeter / black screen blinking cursor with lightdm light-locker Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: System: - Xubuntu 18.04.4, signle seat, single monitor - NVidia 1050ti driver 435.21 - lightdm 1.26.0 - slick-greeter Scenario 1: No xorg.conf. I use 'light-locker-command --lock' or 'dm- tool --lock' or 'dm-tool switch-to-greeter', screen goes black with blinking cursor at top left corner. No keyboard response, only power reset helps. Scenario 2: xorg.conf generated with nvidia tool. After attempting to lock screen same blinking cursor appears, but now if I press Alt-F7 it stops blinking, then Ctrl-Alt-F1, login, sudo systemctl restart lightdm and it's alive and loginable again. In the lightdm.log I see repeating sequence (approx 5 times a second): [+61.67s] DEBUG: Seat seat0: Creating greeter session [+61.67s] DEBUG: Seat seat0: Creating display server of type x [+61.67s] DEBUG: Using VT 8 [+61.67s] DEBUG: Seat seat0: Starting local X display on VT 8 [+61.67s] DEBUG: XServer 1: Logging to /var/log/lightdm/x-1.log [+61.67s] DEBUG: XServer 1: Writing X server authority to /var/run/lightdm/root/:1 [+61.67s] DEBUG: XServer 1: Launching X Server [+61.67s] DEBUG: Launching process 3301: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch [+61.67s] DEBUG: XServer 1: Waiting for ready signal from X server :1 [+61.96s] DEBUG: Process 3301 terminated with signal 6 [+61.96s] DEBUG: XServer 1: X server stopped [+61.96s] DEBUG: Releasing VT 8 [+61.96s] DEBUG: XServer 1: Removing X server authority /var/run/lightdm/root/:1 [+61.96s] DEBUG: Seat seat0: Display server stopped [+61.96s] DEBUG: Seat seat0: Stopping session [+61.96s] DEBUG: Seat seat0: Session stopped [+61.96s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+61.96s] DEBUG: Seat seat0: Active display server stopped, starting greeter x-1.log says: X.Org X Server 1.19.6 Release Date: 2017-12-20 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu Current Operating System: Linux dmitry-desktop 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=7f607ead-1d84-40ec-a3b6-3b78b946bb03 ro noquiet nosplash Build Date: 03 June 2019 08:10:35AM xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Fri Jun 5 15:46:42 2020 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" vesa: Ignoring device with a bound kernel driver (EE) Fatal server error: (EE) no screens found(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. Xorg.1.log says: ... [ 129.447] (II) LoadModule: "nvidia" [ 129.447] (WW) Warning, couldn't open module nvidia [ 129.447] (II) UnloadModule: "nvidia" [ 129.447] (II) Unloading nvidia [ 129.447] (EE) Failed to load module "nvidia" (module does not exist, 0) [ 129.447] (==) Matched nouveau as autoconfigured driver 0 [ 129.447] (==) Matched modesetting as autoconfigured driver 1 [ 129.447] (==) Matched fbdev as autoconfigured driver 2 [ 129.447] (==) Matched vesa as autoconfigured driver 3 [ 129.447] (==) Assigned the driver to the xf86ConfigLayout [ 129.447] (II) LoadModule: "nouveau" ... In my case solution was to add following to xorg.conf to make Xorg load proper nvidia driver: Section "Files" ModulePath "/usr/lib/xorg/modules,/usr/lib/x86_64-linux-gnu/nvidia/xorg/" EndSection I'm not sure which package is responsible for that configuration and how it is done within modern approach, but I think things like this must be done automatically by one of nvidia drivers packages (xserver- xorg-video-nvidia-435 for example). Original discussion: https://github.com/canonical/lightdm/issues/103 Possibly related: https://github.com/the-cavalry/light-locker/iss
[Kernel-packages] [Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
If the external HDMI is plugged in at power-on, a login window will show up on the HDMI, and then I can choose gnome or gnome classic for the session, log in, then right-click on the desktop, set the displays to mirror, and get to the main panels or activities menu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: Confirmed Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+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 1882422] [NEW] xorg fails to load nvidia driver on switching to greeter / black screen blinking cursor with lightdm light-locker
You have been subscribed to a public bug: System: - Xubuntu 18.04.4, signle seat, single monitor - NVidia 1050ti driver 435.21 - lightdm 1.26.0 - slick-greeter Scenario 1: No xorg.conf. I use 'light-locker-command --lock' or 'dm- tool --lock' or 'dm-tool switch-to-greeter', screen goes black with blinking cursor at top left corner. No keyboard response, only power reset helps. Scenario 2: xorg.conf generated with nvidia tool. After attempting to lock screen same blinking cursor appears, but now if I press Alt-F7 it stops blinking, then Ctrl-Alt-F1, login, sudo systemctl restart lightdm and it's alive and loginable again. In the lightdm.log I see repeating sequence (approx 5 times a second): [+61.67s] DEBUG: Seat seat0: Creating greeter session [+61.67s] DEBUG: Seat seat0: Creating display server of type x [+61.67s] DEBUG: Using VT 8 [+61.67s] DEBUG: Seat seat0: Starting local X display on VT 8 [+61.67s] DEBUG: XServer 1: Logging to /var/log/lightdm/x-1.log [+61.67s] DEBUG: XServer 1: Writing X server authority to /var/run/lightdm/root/:1 [+61.67s] DEBUG: XServer 1: Launching X Server [+61.67s] DEBUG: Launching process 3301: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch [+61.67s] DEBUG: XServer 1: Waiting for ready signal from X server :1 [+61.96s] DEBUG: Process 3301 terminated with signal 6 [+61.96s] DEBUG: XServer 1: X server stopped [+61.96s] DEBUG: Releasing VT 8 [+61.96s] DEBUG: XServer 1: Removing X server authority /var/run/lightdm/root/:1 [+61.96s] DEBUG: Seat seat0: Display server stopped [+61.96s] DEBUG: Seat seat0: Stopping session [+61.96s] DEBUG: Seat seat0: Session stopped [+61.96s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+61.96s] DEBUG: Seat seat0: Active display server stopped, starting greeter x-1.log says: X.Org X Server 1.19.6 Release Date: 2017-12-20 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu Current Operating System: Linux dmitry-desktop 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=7f607ead-1d84-40ec-a3b6-3b78b946bb03 ro noquiet nosplash Build Date: 03 June 2019 08:10:35AM xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Fri Jun 5 15:46:42 2020 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" vesa: Ignoring device with a bound kernel driver (EE) Fatal server error: (EE) no screens found(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. Xorg.1.log says: ... [ 129.447] (II) LoadModule: "nvidia" [ 129.447] (WW) Warning, couldn't open module nvidia [ 129.447] (II) UnloadModule: "nvidia" [ 129.447] (II) Unloading nvidia [ 129.447] (EE) Failed to load module "nvidia" (module does not exist, 0) [ 129.447] (==) Matched nouveau as autoconfigured driver 0 [ 129.447] (==) Matched modesetting as autoconfigured driver 1 [ 129.447] (==) Matched fbdev as autoconfigured driver 2 [ 129.447] (==) Matched vesa as autoconfigured driver 3 [ 129.447] (==) Assigned the driver to the xf86ConfigLayout [ 129.447] (II) LoadModule: "nouveau" ... In my case solution was to add following to xorg.conf to make Xorg load proper nvidia driver: Section "Files" ModulePath "/usr/lib/xorg/modules,/usr/lib/x86_64-linux-gnu/nvidia/xorg/" EndSection I'm not sure which package is responsible for that configuration and how it is done within modern approach, but I think things like this must be done automatically by one of nvidia drivers packages (xserver-xorg- video-nvidia-435 for example). Original discussion: https://github.com/canonical/lightdm/issues/103 Possibly related: https://github.com/the-cavalry/light-locker/issues/77 https://github.com/the-cavalry/light-locker/issues/114 ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment dm-tool lightdm nvidia xorg -- xorg fails to load nvidia driver on switching to greeter / black screen blinking cursor with lightdm light-locker https://bugs.launchpad.net/bugs/1882422 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-pack
[Kernel-packages] [Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
If I shutdown and unplug the external HDMI monitor, then power on, the internal display only shows the initial UEFI message, the screen appears grey, then it goes dark. If I then plug in the HDMI (not changing the power state) I can get a tty with ctrl-alt-f1, login, and run startx. MATE then appears, but only the non-panel part of the display. Also the monitor arrangement is flipped, but I think that is a minor MATE problem I noticed in 18.04 after a cli startx. -- 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/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: Confirmed Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
Oh cool. Is there a page I can check to see when that happens so I can test it? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808418 Title: Thinkpad T430u won't boot without noapic workaround Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 - 4.20.0-rc7 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. This bug seems very similar to what's described here for the Thinkpad E485/E585: https://evilazrael.de/node/401 I'll attach screenshots of various times I've encountered this bug over the last year. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy linux-image-4.15.0-42-generic linux-image-4.15.0-42-generic: Installed: 4.15.0-42.45 Candidate: 4.15.0-42.45 Version table: *** 4.15.0-42.45 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880119] Re: System hangs on shut down Kernel 5.3.0-53
*** This bug is a duplicate of bug 1880041 *** https://bugs.launchpad.net/bugs/1880041 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 Status in linux package in Ubuntu: Confirmed Bug description: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toni 1676 F pulseaudio /dev/snd/controlC1: toni 1676 F pulseaudio /dev/snd/controlC0: toni 1676 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 InstallationDate: Installed on 2019-07-25 (301 days ago) InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 IwConfig: enp8s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.173.18 RfKill: Tags: tricia Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+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 1882442] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: Confirmed Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+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 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
I also went in the dconf editor and changed some settings for laptop lid behavior to 'nothing", since the display settings show the internal monitor as a laptop monitor. No effect. -- 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/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: New Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+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 1882442] [NEW] Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
Public bug reported: output of lsb_release -rd: Description:Ubuntu 20.04 LTS Release:20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: New Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not the external monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date:
[Kernel-packages] [Bug 1882195] Re: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI
We found that the system is booting into emergency mode due to unable to mount EFI partition. I suspect this is points to 18.04 bug. There is no issue with 20.04 Jun 07 17:08:32 test-Alienware-Aurora-R9 kernel: Initramfs unpacking failed: Decoding failed Jun 07 17:08:32 test-Alienware-Aurora-R9 kernel: Freeing initrd memory: 48284K Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Found device PM981a NVMe SAMSUNG 2048GB ESP. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Mounting /boot/efi... Jun 07 17:08:34 test-Alienware-Aurora-R9 mount[669]: mount: /boot/efi: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Started Emergency Shell. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Reached target Emergency Mode. ** Description changed: - Issue:- Getting blank screen after the initial install grub prompt. + Issue:- Booting into recovery mode, after post installation - Tried acpi=off, nomodeset parameters added in grub still no luck + Tried nomodeset parameters added in grub, able to install and post + installation of NVIDIA-440 , machine booting in recovery mode. Note:- Ubuntu 20.04 LTS worked without any issues. Env:- - - - + Dell Alienware Aurora R9 + Ubuntu 18.04.4 LTS + 5.3.0-28-generic + dosfstools 4.1-1 UEFI - Dual boot, secure boot disabled, SATA to AHCI - Bios vers - 1.0.7 - $find /sys/devices -name "edid" - - /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid - - /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid - $lspci | grep VGA - - 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX - 2080 SUPER] (rev a1) - - 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX - 2080 SUPER] (rev a1) +01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) + 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === - nomodeset:- defined to instructs the kernel to not load video drivers - and use BIOS modes instead until X is loaded. + Below is the journal logs, for the failure of machine boots into + emergency mode. For some reasons, while unpacking the initramfs, it's + unable to mount the EFI partition and dropping into emergency mode. And + it's points bad superblock + + Might-be this is a bug in the 18.04. At the same time 20.04 worked + without any issues. + + ~~~ + Jun 07 17:08:32 test-Alienware-Aurora-R9 kernel: Initramfs unpacking failed: Decoding failed + Jun 07 17:08:32 test-Alienware-Aurora-R9 kernel: Freeing initrd memory: 48284K + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Found device PM981a NVMe SAMSUNG 2048GB ESP. + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Starting File System Check on /dev/disk/by-uuid/CCF3-E7D6... + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Started File System Check Daemon to report status. + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Found device ST2000DM008-2FR102 4. + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Activating swap /dev/disk/by-uuid/5cfe5c2d-6dd7-46b3-9fce-0e08b35b26cb... + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Activated swap /dev/disk/by-uuid/5cfe5c2d-6dd7-46b3-9fce-0e08b35b26cb. + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Reached target Swap. + Jun 07 17:08:33 test-Alienware-Aurora-R9 kernel: Adding 62499836k swap on /dev/sda4. Priority:-2 extents:1 across:62499836k FS + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd-fsck[623]: fsck.fat 4.1 (2017-01-24) + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd-fsck[623]: /dev/nvme0n1p1: 389 files, 36496/74752 clusters + Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Started File System Check on /dev/disk/by-uuid/CCF3-E7D6. + Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Mounting /boot/efi... + Jun 07 17:08:34 test-Alienware-Aurora-R9 mount[669]: mount: /boot/efi: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. + Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: boot-efi.mount: Mount process exited, code=exited status=32 + Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: boot-efi.mount: Failed with result 'exit-code'. + Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Failed to mount /boot/efi. + Jun 07 17:08:34 test-Alienware-Aurora-R9 kernel: FAT-fs (nvme0n1p1): IO charset iso8859-1 not found + Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Dependency failed for Local File Systems. + Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Dependency failed for Clean up any mess left by 0dns-up. + Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: dns-clean.service: Job dns-clean.service/start failed with result 'dependency'. + Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: local-
[Kernel-packages] [Bug 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04
Is there a way I can simply not start Radeon? I do not need it. I have attempted to blacklist Radeon in a couple of ways but have not been successful in getting the laptop to boot without booting in recovery mode. -- 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/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 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 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+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 1882195] Re: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI
** Description changed: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. - Surprisingly this desktop comes with single HDMI slot. And there is no - any DP port. We need to rely on this one. Apart from the - nomodeset/acpi=off, is there any grub parameter can I try here? Please - suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: - linux-restricted-modules-5.4.0-33-generic N/A - linux-backports-modules-5.4.0-33-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-33-generic N/A + linux-backports-modules-5.4.0-33-generic N/A + linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 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.3.0-28-generic N/A - linux-backports-modules-5.3.0-28-generic N/A - linux-firmware1.173.14 + linux-restricted-modules-5.3.0-28-generic
[Kernel-packages] [Bug 1882195] Re: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI
Hello, Latest apport info fetched info from 18.04 maintaiance mode. Current status:- Able to install 18.04 with passing "nomodeset" after upgrading BIOS to 1.0.8. Post reboot failed, even after installed the NVIDIA driver - 440 Only boot, by passing nomodeset in grub. Please investigate the logs and provide us the fix. how to safely boot along with NVIDIA graphics driver $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1e81 (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation Device 1e81 (rev a1) -- 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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
[Kernel-packages] [Bug 1882195] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381216/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not runnin
[Kernel-packages] [Bug 1882195] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381212/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or no
[Kernel-packages] [Bug 1882195] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381215/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as sess
[Kernel-packages] [Bug 1882195] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381214/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as sess
[Kernel-packages] [Bug 1882195] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381205/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not ru
[Kernel-packages] [Bug 1882195] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381206/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as
[Kernel-packages] [Bug 1882195] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381210/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon runnin
[Kernel-packages] [Bug 1882195] Re: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI
apport information ** Description changed: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-06-07 (0 days ago) + InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) + MachineType: Alienware Alienware Aurora R9 + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset + ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 + 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.3.0-28-generic N/A + linux-backports-modules-5.3.0-28-generic N/A + linux-firmware1.173.14 + Tags: bionic + Uname: Linux 5.3.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _Mar
[Kernel-packages] [Bug 1882195] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381213/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not runn
[Kernel-packages] [Bug 1882195] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381204/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session
[Kernel-packages] [Bug 1882195] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381211/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not runn
[Kernel-packages] [Bug 1882195] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381209/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not runn
[Kernel-packages] [Bug 1882195] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381208/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as sessio
[Kernel-packages] [Bug 1882195] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1882195/+attachment/5381207/+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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Confirmed Bug description: Issue:- Getting blank screen after the initial install grub prompt. Tried acpi=off, nomodeset parameters added in grub still no luck Note:- Ubuntu 20.04 LTS worked without any issues. Env:- UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $find /sys/devices -name "edid" /sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === nomodeset:- defined to instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded. Surprisingly this desktop comes with single HDMI slot. And there is no any DP port. We need to rely on this one. Apart from the nomodeset/acpi=off, is there any grub parameter can I try here? Please suggest. Please note:- we need to rely on 18.04 LTS due to application compatibility. Please suggest Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R9 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.7 dmi.board.name: 0T76PD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.7:bd12/23/2019:svnAlienware:pnAlienwareAuroraR9:pvr1.0.7:rvnAlienware:rn0T76PD:rvrA01:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R9 dmi.product.sku: 0961 dmi.product.version: 1.0.7 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC1', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Alienware Alienware Aurora R9 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=6f3dec95-0e04-4bcb-992c-ee9a185fbb34 ro nomodeset ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as sessio
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
Sorry, I don't upload my stuff here. Using a self build kernel is at your own risk especially there are no security-updates etc. You need to take care yourself if you are willing to do so. Unfortunately there are a lot of outdated instructions around how to build a kernel. I used this (in German) first https://wiki.ubuntuusers.de/Kernel/Kompilierung/ but it failed building the package. I found better instructions here: https://debian-handbook.info/browse/stable/sect.kernel-compilation.html and with make deb-pkg I was able to build and install the debian package. -- 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/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-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: E7CN24WW 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 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
Possibly upload his modified kernel* -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-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: E7CN24WW 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 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1881462] Re: Brightness settings don't work on Lenovo Ideapad 5 15ARE05
My installation with mainline 5.7.0 uses /sys/class/backlight/amdgpu_bl0/brightness and it works partly, but not perfect. Screen reacts for values from 123 to 255... Have you executed "update-grub" and running the correct kernel (check with uname -r)? -- 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/1881462 Title: Brightness settings don't work on Lenovo Ideapad 5 15ARE05 Status in linux package in Ubuntu: Confirmed Bug description: After installation, the notebook brighness buttons change brightness settings, but settings are not applied on the screen. In the log files I can see something like this: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address Failed to get backlight or LED device 'backlight:acpi_video0': No such device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sun May 31 10:43:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev ce) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=94ab3768-11c5-4582-9374-578128353e38 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW 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 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881462/+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 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
@sulliwane: What @Simon did was to change the "eKTH I2C touchscreen" to be built as a module when compiling the kernel. I tried this and it didn't seem to make a difference for me but I'm not as experienced with Linux and may have done something wrong hence why I was asking if he could possibly at his modified kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-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: E7CN24WW 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 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1521173] Re: AER: Corrected error received: id=00e0
@piscvau, the original report is not about a crash, so your issue is unrelated. Please create a separate report for the crash Ubuntu 20.04. (Also mention there, if it is a system crash/hang? Does the numlock key still work? Can you switch to a virtual console with Ctrl + Alt + F4? Can you still ping the system in the network?) Good luck! -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
My Lenovo T440p (with optimus - i915, nouveau) running 20.04 (Kernel 5.4.0-33) is also affected. If I connect an external monitor (Dell U2515H) to it via Displayport it freezes at boot. As workaround I switched from GDM to LightDM. With LightDM it boots straight to the login screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
Thanks @Simon! For information, I installed 5.7 from mainline (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7/) but Touchpad still not working. -- 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/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-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: E7CN24WW 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 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1881462] Re: Brightness settings don't work on Lenovo Ideapad 5 15ARE05
Hey @Simon, I also installed 5.7 from mainline (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7/) but Brightness still not working for me. I notice that adjusting the brightness using the keys or the mouse will change the number from 1 to 21 in this file: cat /sys/class/backlight/ideapad/brightness (but without any real impact on the screen brightness) -- 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/1881462 Title: Brightness settings don't work on Lenovo Ideapad 5 15ARE05 Status in linux package in Ubuntu: Confirmed Bug description: After installation, the notebook brighness buttons change brightness settings, but settings are not applied on the screen. In the log files I can see something like this: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address Failed to get backlight or LED device 'backlight:acpi_video0': No such device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sun May 31 10:43:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev ce) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=94ab3768-11c5-4582-9374-578128353e38 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW 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 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881462/+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 1842462] Re: [IOMMU] xsaves support for pasid
524bb73bc15c56f5587e33c817e103a259b019d2 5274e6c172c47241534e970df26a522497086624 55e00fb66fd5048f4a3ee357018fd26fc527abca 5d6b6a6f9b5ce7ac42273efd75d61ec63b463c18 71581eefd7a0a81b1af7d7c93641925a01d70a9a 8ab22804efefea9ecf3c68aa00f1fa69c70fcfad 98265c17efa9f2279c59262cd27679aca12e0bb8 b860eb8dce5906b14e3a7f3c771e0b3d6ef61b94 c95473e175dd1234b7440daa6eb2670ebf529653 eeedf1533687b8e81865fdbde79eddf7c4b76c9a ** Changed in: intel Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842462 Title: [IOMMU] xsaves support for pasid Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description context switch support for pasid using xsaves method. Target Release: 20.10 Target Kernel: 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842462/+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 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
@sulliwane: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881462 -- 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/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-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: E7CN24WW 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 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Apologies for spamming, guys. I tried another fix for this bug, as suggested here: https://gitlab.freedesktop.org/drm/amd/-/issues/695#note_313722 and it seems to be working. I rebuilt the xserver-xorg-video-amdgpu-hwe-18.04_19.0.1 package with https://github.com/freedesktop/xorg-xf86-video- amdgpu/commit/a2b32e72fdaff3007a79b84929997d8176c2d512 reverted and my machine is able to resume from suspend/hibernate just fine while keeping both DRI3 and KWin's OpenGL compositing enabled. Here's the deb for you to test: https://drive.google.com/file/d/1AK- nKuSkYqGKT09I7juddfIiJNViO86T/view?usp=sharing Note that this is for 18.04 and you have to have the HWE stack enabled first: apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #695 https://gitlab.freedesktop.org/drm/amd/-/issues/695 -- 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/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
Also, did anyone opened an issue related to the brightness controls? Impossible to adjust the brightness -- 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/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-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: E7CN24WW 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 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1882419] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882419 Title: syslog flooded with "wlan0: Failed check-sdata-in-driver check, flags: 0x4" Status in linux package in Ubuntu: Confirmed Bug description: This issue can be found since 4.15.0-99-generic Not sure how to reproduce this yet. But when this happens syslog will be flooded with the following error message, the wifi led will be off, the disk I/O LED will keep blinking (I guess it's writing those log) and the system will be very slow. May 1 22:53:47 allen-laptop kernel: [ 1380.068692] [ cut here ] May 1 22:53:47 allen-laptop kernel: [ 1380.068693] wlan0: Failed check-sdata-in-driver check, flags: 0x4 May 1 22:53:47 allen-laptop kernel: [ 1380.068717] WARNING: CPU: 0 PID: 3 at /build/linux-OORAka/linux-4.15.0/net/mac80211/driver-ops.h:18 drv_sta_state+0x13d/0x3b0 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068718] Modules linked in: rfcomm ccm bnep toshiba_acpi sparse_keymap industrialio toshiba_haps hp_accel lis3lv02d hdaps input_polldev binfmt_misc btusb btrtl btbcm btintel bluetooth coretemp ecdh_generic kvm irqbypass joydev input_leds serio_raw pcmcia snd_hda_codec_analog snd_hda_codec_generic wmi_bmof r852 sm_common nand nand_ecc nand_bch bch yenta_socket mtd pcmcia_rsrc r592 pcmcia_core memstick lpc_ich arc4 iwl3945 thinkpad_acpi iwlegacy nvram mac80211 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hda_intel snd_hda_codec snd_hda_core cfg80211 snd_hwdep snd_pcm snd_seq snd_seq_device shpchp snd_timer snd soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 psmouse i2c_algo_bit ahci libahci sdhci_pci firewire_ohci drm_kms_helper e1000e firewire_core May 1 22:53:47 allen-laptop kernel: [ 1380.068741] pata_acpi sdhci syscopyarea crc_itu_t sysfillrect sysimgblt fb_sys_fops ptp drm pps_core wmi video May 1 22:53:47 allen-laptop kernel: [ 1380.068747] CPU: 0 PID: 3 Comm: kworker/0:0 Tainted: GW4.15.0-99-generic #100-Ubuntu May 1 22:53:47 allen-laptop kernel: [ 1380.068749] Hardware name: LENOVO 7733BW8/7733BW8, BIOS 7LETC4WW (2.24 ) 08/15/2008 May 1 22:53:47 allen-laptop kernel: [ 1380.068766] Workqueue: events_freezable ieee80211_restart_work [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068782] EIP: drv_sta_state+0x13d/0x3b0 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068784] EFLAGS: 00010292 CPU: 0 May 1 22:53:47 allen-laptop kernel: [ 1380.068785] EAX: 0036 EBX: f48f8000 ECX: f4dcd670 EDX: 0007 May 1 22:53:47 allen-laptop kernel: [ 1380.068786] ESI: 0003 EDI: f48f8580 EBP: ed539bac ESP: ed539b88 May 1 22:53:47 allen-laptop kernel: [ 1380.068787] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 May 1 22:53:47 allen-laptop kernel: [ 1380.068788] CR0: 80050033 CR2: b6263160 CR3: 283c CR4: 06f0 May 1 22:53:47 allen-laptop kernel: [ 1380.068789] Call Trace: May 1 22:53:47 allen-laptop kernel: [ 1380.068807] sta_info_move_state+0x275/0x360 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068825] __sta_info_destroy_part2+0x35/0x180 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068842] __sta_info_flush+0x115/0x190 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068864] ieee80211_set_disassoc+0xb7/0x3f0 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068886] ieee80211_mgd_deauth+0x279/0x450 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068889] ? check_preempt_curr+0x27/0x80 May 1 22:53:47 allen-laptop kernel: [ 1380.068909] ? ieee80211_disassoc+0x20/0x20 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068929] ieee80211_deauth+0x16/0x20 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068948] cfg80211_mlme_deauth+0x99/0x190 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068967] cfg80211_mlme_down+0x52/0x70 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068987] cfg80211_disconnect+0x114/0x1e0 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069002] __cfg80211_leave+0x135/0x180 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069018] cfg80211_leave+0x22/0x30 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069034] ? cfg80211_leave+0x30/0x30 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069049] cfg80211_netdev_notifier_call+0x2fd/0x700 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069052] ? sched_slice.isra.57+0x55/0xb0 May 1 22:53:47 allen-laptop kernel: [ 1380.069056] ? __update_load_avg_se.isra.29+0x2b3/0x2c0 May 1 22:53:47 allen-laptop kernel: [ 1380.069059] ? update_load_avg+0x64f/0x830 May 1 22:53:47 allen-laptop kernel: [ 1380.069062] ? update_load_avg+0x6
[Kernel-packages] [Bug 1882419] [NEW] syslog flooded with "wlan0: Failed check-sdata-in-driver check, flags: 0x4"
Public bug reported: This issue can be found since 4.15.0-99-generic Not sure how to reproduce this yet. But when this happens syslog will be flooded with the following error message, the wifi led will be off, the disk I/O LED will keep blinking (I guess it's writing those log) and the system will be very slow. May 1 22:53:47 allen-laptop kernel: [ 1380.068692] [ cut here ] May 1 22:53:47 allen-laptop kernel: [ 1380.068693] wlan0: Failed check-sdata-in-driver check, flags: 0x4 May 1 22:53:47 allen-laptop kernel: [ 1380.068717] WARNING: CPU: 0 PID: 3 at /build/linux-OORAka/linux-4.15.0/net/mac80211/driver-ops.h:18 drv_sta_state+0x13d/0x3b0 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068718] Modules linked in: rfcomm ccm bnep toshiba_acpi sparse_keymap industrialio toshiba_haps hp_accel lis3lv02d hdaps input_polldev binfmt_misc btusb btrtl btbcm btintel bluetooth coretemp ecdh_generic kvm irqbypass joydev input_leds serio_raw pcmcia snd_hda_codec_analog snd_hda_codec_generic wmi_bmof r852 sm_common nand nand_ecc nand_bch bch yenta_socket mtd pcmcia_rsrc r592 pcmcia_core memstick lpc_ich arc4 iwl3945 thinkpad_acpi iwlegacy nvram mac80211 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hda_intel snd_hda_codec snd_hda_core cfg80211 snd_hwdep snd_pcm snd_seq snd_seq_device shpchp snd_timer snd soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 psmouse i2c_algo_bit ahci libahci sdhci_pci firewire_ohci drm_kms_helper e1000e firewire_core May 1 22:53:47 allen-laptop kernel: [ 1380.068741] pata_acpi sdhci syscopyarea crc_itu_t sysfillrect sysimgblt fb_sys_fops ptp drm pps_core wmi video May 1 22:53:47 allen-laptop kernel: [ 1380.068747] CPU: 0 PID: 3 Comm: kworker/0:0 Tainted: GW4.15.0-99-generic #100-Ubuntu May 1 22:53:47 allen-laptop kernel: [ 1380.068749] Hardware name: LENOVO 7733BW8/7733BW8, BIOS 7LETC4WW (2.24 ) 08/15/2008 May 1 22:53:47 allen-laptop kernel: [ 1380.068766] Workqueue: events_freezable ieee80211_restart_work [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068782] EIP: drv_sta_state+0x13d/0x3b0 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068784] EFLAGS: 00010292 CPU: 0 May 1 22:53:47 allen-laptop kernel: [ 1380.068785] EAX: 0036 EBX: f48f8000 ECX: f4dcd670 EDX: 0007 May 1 22:53:47 allen-laptop kernel: [ 1380.068786] ESI: 0003 EDI: f48f8580 EBP: ed539bac ESP: ed539b88 May 1 22:53:47 allen-laptop kernel: [ 1380.068787] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 May 1 22:53:47 allen-laptop kernel: [ 1380.068788] CR0: 80050033 CR2: b6263160 CR3: 283c CR4: 06f0 May 1 22:53:47 allen-laptop kernel: [ 1380.068789] Call Trace: May 1 22:53:47 allen-laptop kernel: [ 1380.068807] sta_info_move_state+0x275/0x360 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068825] __sta_info_destroy_part2+0x35/0x180 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068842] __sta_info_flush+0x115/0x190 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068864] ieee80211_set_disassoc+0xb7/0x3f0 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068886] ieee80211_mgd_deauth+0x279/0x450 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068889] ? check_preempt_curr+0x27/0x80 May 1 22:53:47 allen-laptop kernel: [ 1380.068909] ? ieee80211_disassoc+0x20/0x20 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068929] ieee80211_deauth+0x16/0x20 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068948] cfg80211_mlme_deauth+0x99/0x190 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068967] cfg80211_mlme_down+0x52/0x70 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068987] cfg80211_disconnect+0x114/0x1e0 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069002] __cfg80211_leave+0x135/0x180 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069018] cfg80211_leave+0x22/0x30 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069034] ? cfg80211_leave+0x30/0x30 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069049] cfg80211_netdev_notifier_call+0x2fd/0x700 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069052] ? sched_slice.isra.57+0x55/0xb0 May 1 22:53:47 allen-laptop kernel: [ 1380.069056] ? __update_load_avg_se.isra.29+0x2b3/0x2c0 May 1 22:53:47 allen-laptop kernel: [ 1380.069059] ? update_load_avg+0x64f/0x830 May 1 22:53:47 allen-laptop kernel: [ 1380.069062] ? update_load_avg+0x64f/0x830 May 1 22:53:47 allen-laptop kernel: [ 1380.069065] ? inetdev_event+0x2b/0x560 May 1 22:53:47 allen-laptop kernel: [ 1380.069068] ? skb_dequeue+0x5b/0x70 May 1 22:53:47 allen-laptop kernel: [ 1380.069070] ? wireless_nlevent_flush+0x4c/0x90 May 1 22:53:47 allen-laptop kernel: [ 1380.069086] ? cfg80211_leave+0x30/0x30 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069089] notifier_call_chain+0x51/0x80 May 1 22:53:47 allen-laptop kernel:
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
I also have a Lenovo IdeaPad 5 15ARE05 with Ubuntu 20.04 installed on it. No touchpad working. cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor= Product= Version= N: Name="Elan Touchscreen" P: Phys= S: Sysfs=/devices/platform/AMDI0010:01/i2c-1/i2c-ELAN0001:00/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=6618103 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:05/LNXVIDEO:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=093a Product=2510 Version=0111 N: Name="PixArt USB Optical Mouse" P: Phys=usb-:03:00.4-1/input0 S: Sysfs=/devices/pci:00/:00:08.1/:03:00.4/usb3/3-1/3-1:1.0/0003:093A:2510.0001/input/input6 U: Uniq= H: Handlers=mouse1 event6 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:14.3/PNP0C09:00/VPC2004:00/input/input7 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=174f Product=244c Version=0013 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:03:00.3-3/button S: Sysfs=/devices/pci:00/:00:08.1/:03:00.3/usb1/1-3/1-3:1.0/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:03:00.1/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:03:00.1/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:03:00.6/sound/card1/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:08.1/:03:00.6/sound/card1/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=4 And xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PixArt USB Optical Mouse id=10 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9[slave keyboard (3)] ↳ Ideapad extra buttons id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] -- 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/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Ar
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
Seems to be related: https://bbs.archlinux.org/viewtopic.php?id=256002 (Lenovo Ideapad 5 touchpad not working / untraceable) -- 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/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-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: E7CN24WW 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 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Good news. I was able to work-around this problem by disabling DRI 3: #nano /usr/share/X11/xorg.conf.d/10-amdgpu.conf Option "DRI" "2" I also added: Option "TearFree" "true" to mitigate any screen tearing, although that was for purely cosmetic reasons. See if this works for you and report back, please. -- 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/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388] do_syscall_64+0x57/0x190 Oct 21 10:57:26 pc kernel: [ 9475.309392] entry_SYSCALL_64_after_hwframe+0x
