[Kernel-packages] [Bug 1868733] Re: Battery charge state frozen/incorrect
Latest Ubuntu-base package update corrected this error for me. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868733 Title: Battery charge state frozen/incorrect Status in linux package in Ubuntu: Fix Released Bug description: This may be a copy of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886 However with the bug's age I did not want to take a chance and reported separately and commented/subscribed there as well. Running Kubuntu 19.10. After running 45 minutes, unplugged, on old computer, with brightness 100% and streaming video: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_ACAD native-path: ACAD power supply: yes updated: Tue 24 Mar 2020 08:48:42 AM CDT (2763 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: Tue 24 Mar 2020 09:34:43 AM CDT (2 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: Tue 24 Mar 2020 08:26:14 AM CDT (4111 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 _ $ acpi Battery 0: Not charging, 100% _ $ cat /sys/class/power_supply/BAT1/charge* 65535000 65535000 65535000 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sperger1086 F pulseaudio /dev/snd/controlC0: sperger1086 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-03-11 (12 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 003: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite C55-B Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.3.0-42-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/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:
[Kernel-packages] [Bug 1868538] Re: Focal update: v5.4.27 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Paolo Pisati (p-pisati) -- 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/1868538 Title: Focal update: v5.4.27 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: 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: v5.4.27 upstream stable release from git://git.kernel.org/ Linux 5.4.27 ipv4: ensure rcu_read_lock() in cipso_v4_error() ARM: 8961/2: Fix Kbuild issue caused by per-task stack protector GCC plugin HID: add ALWAYS_POLL quirk to lenovo pixart mouse HID: google: add moonball USB id mm: slub: add missing TID bump in kmem_cache_alloc_bulk() ARM: 8958/1: rename missed uaccess .fixup section ARM: 8957/1: VDSO: Match ARMv8 timer in cntvct_functional() net: qrtr: fix len of skb_put_padto in qrtr_node_enqueue blk-mq: insert flush request to the front of dispatch queue jbd2: fix data races at struct journal_head sfc: fix timestamp reconstruction at 16-bit rollover points net: rmnet: fix packet forwarding in rmnet bridge mode net: rmnet: fix bridge mode bugs net: rmnet: use upper/lower device infrastructure net: rmnet: do not allow to change mux id if mux id is duplicated net: rmnet: remove rcu_read_lock in rmnet_force_unassociate_device() net: rmnet: fix suspicious RCU usage net: rmnet: fix NULL pointer dereference in rmnet_changelink() net: rmnet: fix NULL pointer dereference in rmnet_newlink() hinic: fix a bug of rss configuration hinic: fix a bug of setting hw_ioctxt hinic: fix a irq affinity bug net: phy: mscc: fix firmware paths slip: not call free_netdev before rtnl_unlock in slip_open signal: avoid double atomic counter increments for user accounting kbuild: add dt_binding_check to PHONY in a correct place kbuild: add dtbs_check to PHONY drm/amdgpu: fix memory leak during TDR test(v2) blk-mq: insert passthrough request into hctx->dispatch directly net: ll_temac: Handle DMA halt condition caused by buffer underrun net: ll_temac: Fix RX buffer descriptor handling on GFP_ATOMIC pressure net: ll_temac: Add more error handling of dma_map_single() calls net: ll_temac: Fix race condition causing TX hang mac80211: rx: avoid RCU list traversal under mutex net: ks8851-ml: Fix IRQ handling and locking net: usb: qmi_wwan: restore mtu min/max values after raw_ip switch scsi: libfc: free response frame from GPN_ID cfg80211: check reg_rule for NULL in handle_channel_custom() tracing: Fix number printing bug in print_synth_event() selftests/rseq: Fix out-of-tree compilation HID: hid-bigbenff: fix race condition for scheduled work during removal HID: hid-bigbenff: call hid_hw_stop() in case of error HID: hid-bigbenff: fix general protection fault caused by double kfree HID: i2c-hid: add Trekstor Surfbook E11B to descriptor override ACPI: watchdog: Set default timeout in probe HID: apple: Add support for recent firmware on Magic Keyboards ACPI: watchdog: Allow disabling WDAT at boot drm/amdgpu: Fix TLB invalidation request when using semaphore netfilter: xt_hashlimit: unregister proc file before releasing mutex netfilter: hashlimit: do not use indirect calls during gc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1868898] Missing required logs.
Ran apport-collect 1868898 -Steve On 2020-03-25 8:30 a.m., Ubuntu Kernel Bot wrote: > apport-collect 1868898 -- 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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868727] Re: drm/i915: Enable Tiger Lake
** Changed in: linux-oem-5.4 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1868727
Title:
drm/i915: Enable Tiger Lake
Status in linux-oem-5.4 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
We need to apply a set of patches on oem-5.6 in order to enable Tiger Lake
(TGL) graphics. These are all from drm-intel-next-queued that will end up in
v5.7.
drm/i915/dp/tgl+: Update combo phy vswing tables
drm/i915/tgl: Add Wa_1409825376 to tgl
drm/i915/tgl: Re-enable RPS
drm/i915: Disable tesselation clock gating on tgl A0
drm/i915/tgl: Update cdclk voltage level settings
drm/i915: HDCP support on above PORT_E
drm/i915/tgl: Add Wa_1808121037 to tgl.
drm/i915: Implement Wa_1607090982
drm/i915: Use engine wa list for Wa_1607090982
drm/i915/tgl: Program MBUS_ABOX{1,2}_CTL during display init
drm/i915/tgl: Allow DC5/DC6 entry while PG2 is active
drm/i915/tgl: Add Wa_1606054188:tgl
drm/i915: Set up PIPE_MISC truncate bit on tgl+
drm/i915/ggtt: do not set bits 1-11 in gen12 ptes
drm/i915: Nuke pre-production GLK HDMI w/a 1139
drm/i915: Limit display Wa_1405510057 to gen11
drm/i915/tgl: Implement Wa_1409804808
drm/i915/tgl: Implement Wa_1806527549
drm/i915/tgl: Add Wa_1409085225, Wa_14010229206
drm/i915/tgl: Extend Wa_1606931601 for all steppings
drm/i915/tgl: Add note to Wa_1607297627
drm/i915/tgl: Add note about Wa_1607063988
drm/i915/tgl: Fix the Wa number of a fix
drm/i915/tgl: Add note about Wa_1409142259
drm/i915/tgl: Add Wa number to
WaAllowPMDepthAndInvocationCountAccessFromUMD
drm/i915/huc: update TGL HuC to v7.0.12
drm/i915/dmc: Use firmware v2.06 for TGL
drm/i915/tgl: Move and restrict Wa_1408615072
drm/i915/tgl: WaDisableGPGPUMidThreadPreemption
drm/i915/tgl: Make Wa_1606700617 permanent
drm/i915/tgl: Don't treat unslice registers as masked
drm/i915: Add missing HDMI audio pixel clocks for gen12
drm/i915/gen12: Disable preemption timeout
Revert "drm/i915/tgl: Add extra hdc flush workaround"
drm/i915: Handle all MCR ranges
drm/i915/tgl: Remove require_force_probe protection
drm/i915/tgl: Add new PCI IDs to TGL
[Test case]
Boot a TGL system, verify that it's using the native graphics driver.
[Regression potential]
Shouldn't be any, this is a new platform.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.4/+bug/1868727/+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 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Hi all, I have the same laptop HP ZBook 15 G6 and my mike is not recognised too. I'm using ubuntu 18.04 kernel version 5.3.0-28-generic, and with the newer kernels my whole sound card is not recognised. If you look at this documentation http://h20195.www2.hp.com/v2/getpdf.aspx/4AA7-6280ENW.pdf page 12 , they say: "11 Audio output via speakers function. Audio input via built-in microphone is currently not functional due to a missing driver. Please check with your distro vendor for the availability of the snd-sof-pci driver in ALSA." -- 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/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1869061] Re: Focal update: v5.4.28 upstream stable release
** Description changed: + SRU Justification - 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: - 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: + v5.4.28 upstream stable release + from git://git.kernel.org/ -v5.4.28 upstream stable release -from git://git.kernel.org/ + perf/x86/amd: Add support for Large Increment per Cycle Events + EDAC/amd64: Add family ops for Family 19h Models 00h-0Fh + x86/MCE/AMD, EDAC/mce_amd: Add new Load Store unit McaType + EDAC/mce_amd: Always load on SMCA systems + x86/amd_nb: Add Family 19h PCI IDs + EDAC/amd64: Drop some family checks for newer systems + locks: fix a potential use-after-free problem when wakeup a waiter + locks: reinstate locks_delete_block optimization + spi: spi-omap2-mcspi: Support probe deferral for DMA channels + drm/mediatek: Find the cursor plane instead of hard coding it + phy: ti: gmii-sel: fix set of copy-paste errors + phy: ti: gmii-sel: do not fail in case of gmii + ARM: dts: dra7-l4: mark timer13-16 as pwm capable + spi: qup: call spi_qup_pm_resume_runtime before suspending + powerpc: Include .BTF section + cifs: fix potential mismatch of UNC paths + cifs: add missing mount option to /proc/mounts + ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes + spi: pxa2xx: Add CS control clock quirk + spi/zynqmp: remove entry that causes a cs glitch + drm/exynos: dsi: propagate error value and silence meaningless warning + drm/exynos: dsi: fix workaround for the legacy clock name + drm/exynos: hdmi: don't leak enable HDMI_EN regulator if probe fails + drivers/perf: fsl_imx8_ddr: Correct the CLEAR bit definition + drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer + altera-stapl: altera_get_note: prevent write beyond end of 'key' + dm bio record: save/restore bi_end_io and bi_integrity + dm integrity: use dm_bio_record and dm_bio_restore + riscv: avoid the PIC offset of static percpu data in module beyond 2G limits + ASoC: stm32: sai: manage rebind issue + spi: spi_register_controller(): free bus id on error paths + riscv: Force flat memory model with no-mmu + riscv: Fix range looking for kernel image memblock + drm/amdgpu: clean wptr on wb when gpu recovery + drm/amd/display: Clear link settings on MST disable connector + drm/amd/display: fix dcc swath size calculations on dcn1 + xenbus: req->body should be updated before req->state + xenbus: req->err should be updated before req->state + block, bfq: fix overwrite of bfq_group pointer in bfq_find_set_group() + parse-maintainers: Mark as executable + binderfs: use refcount for binder control devices too + Revert "drm/fbdev: Fallback to non tiled mode if all tiles not present" + usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters + USB: serial: option: add ME910G1 ECM composition 0x110b + usb: host: xhci-plat: add a shutdown + USB: serial: pl2303: add device-id for HP LD381 + usb: xhci: apply XHCI_SUSPEND_DELAY to AMD XHCI controller 1022:145c + usb: typec: ucsi: displayport: Fix NULL pointer dereference + usb: typec: ucsi: displayport: Fix a potential race during registration + USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL + USB: cdc-acm: fix rounding error in TIOCSSERIAL + ALSA: line6: Fix endless MIDI read loop + ALSA: hda/realtek - Enable headset mic of Acer X2660G with ALC662 + ALSA: hda/realtek - Enable the headset of Acer N50-600 with ALC662 + ALSA: seq: virmidi: Fix running status after receiving sysex + ALSA: seq: oss: Fix running status after receiving sysex + ALSA: pcm: oss: Avoid plugin buffer overflow + ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks + tty: fix compat TIOCGSERIAL leaking uninitialized memory + tty: fix compat TIOCGSERIAL checking wrong function ptr + iio: chemical: sps30: fix missing triggered buffer dependency + iio: st_sensors: remap SMO8840 to LIS2DH12 + iio: trigger: stm32-timer: disable master mode when stopping + iio: accel: adxl372: Set iio_chan BE + iio: magnetometer: ak8974: Fix negative raw values in sysfs + iio: adc: stm32-dfsdm: fix sleep in atomic context + iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode + iio: light: vcnl4000: update
[Kernel-packages] [Bug 1869062] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1869062 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869062 Title: Acer Aspire 7715 microphone not detected Status in linux package in Ubuntu: Incomplete Bug description: System:Host: jdole-Aspire-7715Z Kernel: 4.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Acer product: Aspire 7715Z v: V3.04 serial: Mobo: Acer model: Aspire 7715Z v: V3.04 serial: BIOS: Acer v: 3.04 date: 12/16/2009 CPU: Topology: Dual Core model: Pentium T4400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8778 Speed: 2195 MHz min/max: 1200/2200 MHz Core speeds (MHz): 1: 2195 2: 2195 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 19.2.8 direct render: Yes Audio: Device-1: Intel 82801I HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e Sound Server: ALSA v: k4.15.0-91-generic Network: Device-1: Qualcomm Atheros AR928X Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel port: 5000 bus ID: 04:00.0 chip ID: 168c:002a IF: wlp4s0 state: up mac: Device-2: Qualcomm Atheros AR8132 Fast Ethernet vendor: Acer Incorporated ALI driver: atl1c v: 1.0.1.1-NAPI port: 1000 bus ID: 05:00.0 chip ID: 1969:1062 IF: enp5s0 state: down mac: Drives:Local Storage: total: 465.76 GiB used: 33.06 GiB (7.1%) ID-1: /dev/sda vendor: Western Digital model: WD5000BEVT-22A0RT0 size: 465.76 GiB speed: 3.0 Gb/s serial: Partition: ID-1: / size: 211.37 GiB used: 33.06 GiB (15.6%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 54.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mint.remi.lu tricia main upstream import backport 2: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic main restricted universe multiverse 3: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse 6: deb http: //archive.canonical.com/ubuntu/ bionic partner Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 1: deb [arch=amd64] https: //repo.skype.com/deb stable main Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 1: deb http: //linux.teamviewer.com/deb stable main Info: Processes: 214 Uptime: 8h 09m Memory: 3.78 GiB used: 2.69 GiB (71.0%) Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Client: Unknown python3.6 client inxi: 3.0.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869062/+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 1824886] Re: Battery level stuck at 100% and Estimating...
I dont want to close this bug report as fix released, but after my update of ubuntu-base yesterday the issue is gone. If the original bug reported agrees, then the bug report can be closed. -- 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/1824886 Title: Battery level stuck at 100% and Estimating... Status in linux package in Ubuntu: Confirmed Bug description: Battery applet does not display battery charge. Always shows 100%. ASUS 1215T-RED008S. Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-control-center: Установлен: 1:3.28.2-0ubuntu0.18.04.2 Кандидат: 1:3.28.2-0ubuntu0.18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 00:48:18 2019 InstallationDate: Installed on 2019-04-10 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886/+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 1869062] [NEW] Acer Aspire 7715 microphone not detected
Public bug reported: System:Host: jdole-Aspire-7715Z Kernel: 4.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Acer product: Aspire 7715Z v: V3.04 serial: Mobo: Acer model: Aspire 7715Z v: V3.04 serial: BIOS: Acer v: 3.04 date: 12/16/2009 CPU: Topology: Dual Core model: Pentium T4400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8778 Speed: 2195 MHz min/max: 1200/2200 MHz Core speeds (MHz): 1: 2195 2: 2195 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 19.2.8 direct render: Yes Audio: Device-1: Intel 82801I HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e Sound Server: ALSA v: k4.15.0-91-generic Network: Device-1: Qualcomm Atheros AR928X Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel port: 5000 bus ID: 04:00.0 chip ID: 168c:002a IF: wlp4s0 state: up mac: Device-2: Qualcomm Atheros AR8132 Fast Ethernet vendor: Acer Incorporated ALI driver: atl1c v: 1.0.1.1-NAPI port: 1000 bus ID: 05:00.0 chip ID: 1969:1062 IF: enp5s0 state: down mac: Drives:Local Storage: total: 465.76 GiB used: 33.06 GiB (7.1%) ID-1: /dev/sda vendor: Western Digital model: WD5000BEVT-22A0RT0 size: 465.76 GiB speed: 3.0 Gb/s serial: Partition: ID-1: / size: 211.37 GiB used: 33.06 GiB (15.6%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 54.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mint.remi.lu tricia main upstream import backport 2: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic main restricted universe multiverse 3: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse 6: deb http: //archive.canonical.com/ubuntu/ bionic partner Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 1: deb [arch=amd64] https: //repo.skype.com/deb stable main Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 1: deb http: //linux.teamviewer.com/deb stable main Info: Processes: 214 Uptime: 8h 09m Memory: 3.78 GiB used: 2.69 GiB (71.0%) Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Client: Unknown python3.6 client inxi: 3.0.32 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869062 Title: Acer Aspire 7715 microphone not detected Status in linux package in Ubuntu: Incomplete Bug description: System:Host: jdole-Aspire-7715Z Kernel: 4.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Acer product: Aspire 7715Z v: V3.04 serial: Mobo: Acer model: Aspire 7715Z v: V3.04 serial: BIOS: Acer v: 3.04 date: 12/16/2009 CPU: Topology: Dual Core model: Pentium T4400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8778 Speed: 2195 MHz min/max: 1200/2200 MHz Core speeds (MHz): 1: 2195 2: 2195 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express
[Kernel-packages] [Bug 1869061] Re: Focal update: v5.4.28 upstream stable release
** Changed in: linux (Ubuntu Focal) 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/1869061 Title: Focal update: v5.4.28 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: 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: v5.4.28 upstream stable release from git://git.kernel.org/ locks: fix a potential use-after-free problem when wakeup a waiter locks: reinstate locks_delete_block optimization spi: spi-omap2-mcspi: Support probe deferral for DMA channels drm/mediatek: Find the cursor plane instead of hard coding it phy: ti: gmii-sel: fix set of copy-paste errors phy: ti: gmii-sel: do not fail in case of gmii ARM: dts: dra7-l4: mark timer13-16 as pwm capable spi: qup: call spi_qup_pm_resume_runtime before suspending powerpc: Include .BTF section cifs: fix potential mismatch of UNC paths cifs: add missing mount option to /proc/mounts ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes spi: pxa2xx: Add CS control clock quirk spi/zynqmp: remove entry that causes a cs glitch drm/exynos: dsi: propagate error value and silence meaningless warning drm/exynos: dsi: fix workaround for the legacy clock name drm/exynos: hdmi: don't leak enable HDMI_EN regulator if probe fails drivers/perf: fsl_imx8_ddr: Correct the CLEAR bit definition drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer altera-stapl: altera_get_note: prevent write beyond end of 'key' dm bio record: save/restore bi_end_io and bi_integrity dm integrity: use dm_bio_record and dm_bio_restore riscv: avoid the PIC offset of static percpu data in module beyond 2G limits ASoC: stm32: sai: manage rebind issue spi: spi_register_controller(): free bus id on error paths riscv: Force flat memory model with no-mmu riscv: Fix range looking for kernel image memblock drm/amdgpu: clean wptr on wb when gpu recovery drm/amd/display: Clear link settings on MST disable connector drm/amd/display: fix dcc swath size calculations on dcn1 xenbus: req->body should be updated before req->state xenbus: req->err should be updated before req->state block, bfq: fix overwrite of bfq_group pointer in bfq_find_set_group() parse-maintainers: Mark as executable binderfs: use refcount for binder control devices too Revert "drm/fbdev: Fallback to non tiled mode if all tiles not present" usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters USB: serial: option: add ME910G1 ECM composition 0x110b usb: host: xhci-plat: add a shutdown USB: serial: pl2303: add device-id for HP LD381 usb: xhci: apply XHCI_SUSPEND_DELAY to AMD XHCI controller 1022:145c usb: typec: ucsi: displayport: Fix NULL pointer dereference usb: typec: ucsi: displayport: Fix a potential race during registration USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL USB: cdc-acm: fix rounding error in TIOCSSERIAL ALSA: line6: Fix endless MIDI read loop ALSA: hda/realtek - Enable headset mic of Acer X2660G with ALC662 ALSA: hda/realtek - Enable the headset of Acer N50-600 with ALC662 ALSA: seq: virmidi: Fix running status after receiving sysex ALSA: seq: oss: Fix running status after receiving sysex ALSA: pcm: oss: Avoid plugin buffer overflow ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks tty: fix compat TIOCGSERIAL leaking uninitialized memory tty: fix compat TIOCGSERIAL checking wrong function ptr iio: chemical: sps30: fix missing triggered buffer dependency iio: st_sensors: remap SMO8840 to LIS2DH12 iio: trigger: stm32-timer: disable master mode when stopping iio: accel: adxl372: Set iio_chan BE iio: magnetometer: ak8974: Fix negative raw values in sysfs iio: adc: stm32-dfsdm: fix sleep in atomic context iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode iio: light: vcnl4000: update sampling periods for vcnl4200 iio: light: vcnl4000: update sampling periods for vcnl4040 mmc: rtsx_pci: Fix support for speed-modes that relies on tuning mmc: sdhci-of-at91: fix cd-gpios for SAMA5D2 mmc: sdhci-cadence: set SDHCI_QUIRK2_PRESET_VALUE_BROKEN for UniPhier CIFS: fiemap: do not return EINVAL if get nothing kbuild: Disable -Wpointer-to-enum-cast staging: rtl8188eu: Add device id for MERCUSYS MW150US v2 staging: greybus: loopback_test:
[Kernel-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
It seems that one of the updates that just happened via apt might have fixed the issue? attached is dmesg log... does it look like expected behavior? My fans are properly turning off, and when I open my laptop lid, I'm not getting the delayed sleep mode. BIOS update I'm not sure exactly which package solved it. I've attached the most recent list of packages upgraded by apt, as well. I'm curious if it's the rfkill update that solved 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/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019
[Kernel-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
** Attachment added: "apt.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1865170/+attachment/5341642/+files/apt.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/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1868169] [NEW] Cannot build nvidia driver via dkms because compiler doesn't match kernel
You have been subscribed to a public bug: The same as this issue https://bugs.launchpad.net/ubuntu/+source/gcc- defaults/+bug/1608753 but on 18.04 relevant output from /var/lib/dkms/nvidia/440.33.01/build/make.log: Compiler version check failed: The major and minor number of the compiler used to compile the kernel: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) does not match the compiler used here: cc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. It is recommended to set the CC environment variable to the compiler that was used to compile the kernel. The compiler version check can be disabled by setting the IGNORE_CC_MISMATCH environment variable to "1". However, mixing compiler versions between the kernel and kernel modules can result in subtle bugs that are difficult to diagnose. *** Failed CC version check. Bailing out! *** ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: rls-bb-incoming -- Cannot build nvidia driver via dkms because compiler doesn't match kernel https://bugs.launchpad.net/bugs/1868169 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
the dmesg with only the chrome attempt ** Attachment added: "dmesg-202003251809.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5341612/+files/dmesg-202003251809.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I just installed the latest package from your PPA: it actually makes the looping issue worse. now the issue occurs as soon as I create a meeting in meets.google.com with chromium. I tried right after to create a meeting in firefox and couldnt' get the headset to work at all. After restarting the headset, in firefox the headset behaved as I would expect and I didn't have the error anymore. I attached the whole boot's dmesg to this comment. ** Attachment added: "dmesg-202003251813.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5341611/+files/dmesg-202003251813.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1835660] Re: initramfs unpacking failed
I've been experiencing this issue the last couple of days on Ubuntu 20.04 Focal Fossa too. Issuing $ sudo update-initramfs -u does nothing for me. Adding COMPRESS=gzip to /etc/initramfs-tools/initramfs.conf didn't work either. -- 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/1835660 Title: initramfs unpacking failed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+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 1865170] Re: lid close simply turns off laptop screen
Nevermind, I just saw the rfkill changelog. Since I'm no longer able to reproduce the bug, should it be closed? -- 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/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
[Kernel-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1865170/+attachment/5341643/+files/dmesg.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/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1868169] Re: Cannot build nvidia driver via dkms because compiler doesn't match kernel
cnewcome@wintermute:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" cnewcome@wintermute:~$ cat /proc/version Linux version 5.3.0-42-generic (buildd@lcy01-amd64-019) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 cnewcome@wintermute:~$ gcc --version gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- 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/1868169 Title: Cannot build nvidia driver via dkms because compiler doesn't match kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The same as this issue https://bugs.launchpad.net/ubuntu/+source/gcc- defaults/+bug/1608753 but on 18.04 relevant output from /var/lib/dkms/nvidia/440.33.01/build/make.log: Compiler version check failed: The major and minor number of the compiler used to compile the kernel: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) does not match the compiler used here: cc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. It is recommended to set the CC environment variable to the compiler that was used to compile the kernel. The compiler version check can be disabled by setting the IGNORE_CC_MISMATCH environment variable to "1". However, mixing compiler versions between the kernel and kernel modules can result in subtle bugs that are difficult to diagnose. *** Failed CC version check. Bailing out! *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868169/+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 1868169] Re: Cannot build nvidia driver via dkms because compiler doesn't match kernel
gcc package upgraded in 18.04 and new kernel compiled with that version hasn't been released yet. ** Package changed: gcc-defaults (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868169 Title: Cannot build nvidia driver via dkms because compiler doesn't match kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: The same as this issue https://bugs.launchpad.net/ubuntu/+source/gcc- defaults/+bug/1608753 but on 18.04 relevant output from /var/lib/dkms/nvidia/440.33.01/build/make.log: Compiler version check failed: The major and minor number of the compiler used to compile the kernel: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) does not match the compiler used here: cc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. It is recommended to set the CC environment variable to the compiler that was used to compile the kernel. The compiler version check can be disabled by setting the IGNORE_CC_MISMATCH environment variable to "1". However, mixing compiler versions between the kernel and kernel modules can result in subtle bugs that are difficult to diagnose. *** Failed CC version check. Bailing out! *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868169/+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 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
Customer notified to test new kernels and verify the driver updates. -- 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/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. [FIXES] These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement All are clean cherry picks into the 5.4 branch and can be pulled from my branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1864484-smartpqi-to-1.2.10-025 [TESTING] modinfo for smartpqi should show: version:1.2.10-025 description:Driver for Microsemi Smart Family Controller version 1.2.10-025 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+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 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Thanks for the explanations. I'll keep working with pulseaudio+ucm for now so as to be able to test your fixes. If it becomes too unbearable I'll revert to dmic_detect=0 >About the issue on google meet, it is a problem, do you also meet the similar issue on other audio apps? Regarding the microphone issue, it seems to be chromium specific, possibly related to the fact that chromium is a snap and is therefore sandboxed. here is the corresponding dmesg trace : [24350.178216] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [24350.270480] sof-audio-pci :00:1f.3: firmware boot complete [24354.651222] input: 2C:41:A1:47:C5:93 as /devices/virtual/input/input24 [24354.693912] audit: type=1107 audit(1585155460.615:229): pid=1284 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.8" mask="receive" pid=8453 label="snap.spotify.spotify" peer_pid=1291 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [24354.930070] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24354.940107] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24354.940110] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24354.940110] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24364.030170] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24364.030176] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24364.030177] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.009964] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.009968] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.019991] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.019995] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.019996] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.094089] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.094093] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.094095] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.244985] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.244988] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.244989] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.254999] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.255003] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.255004] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.467006] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.467011] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.467012] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.467014] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.477005] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.522114] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.522117] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.748003] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.748012] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.748013] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.758019] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.758025] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.842064] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.842067] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24366.023968] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.023972] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.034004] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.034008] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.034010] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.295004] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.295009] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.304979] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.304982] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.304983] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.338045] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24366.338048] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24366.338049] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24366.426008] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.426014] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.426015] Bluetooth: hci0: SCO packet for unknown connection
[Kernel-packages] [Bug 1869061] [NEW] Focal update: v5.4.28 upstream stable release
Public bug reported: 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: v5.4.28 upstream stable release from git://git.kernel.org/ locks: fix a potential use-after-free problem when wakeup a waiter locks: reinstate locks_delete_block optimization spi: spi-omap2-mcspi: Support probe deferral for DMA channels drm/mediatek: Find the cursor plane instead of hard coding it phy: ti: gmii-sel: fix set of copy-paste errors phy: ti: gmii-sel: do not fail in case of gmii ARM: dts: dra7-l4: mark timer13-16 as pwm capable spi: qup: call spi_qup_pm_resume_runtime before suspending powerpc: Include .BTF section cifs: fix potential mismatch of UNC paths cifs: add missing mount option to /proc/mounts ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes spi: pxa2xx: Add CS control clock quirk spi/zynqmp: remove entry that causes a cs glitch drm/exynos: dsi: propagate error value and silence meaningless warning drm/exynos: dsi: fix workaround for the legacy clock name drm/exynos: hdmi: don't leak enable HDMI_EN regulator if probe fails drivers/perf: fsl_imx8_ddr: Correct the CLEAR bit definition drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer altera-stapl: altera_get_note: prevent write beyond end of 'key' dm bio record: save/restore bi_end_io and bi_integrity dm integrity: use dm_bio_record and dm_bio_restore riscv: avoid the PIC offset of static percpu data in module beyond 2G limits ASoC: stm32: sai: manage rebind issue spi: spi_register_controller(): free bus id on error paths riscv: Force flat memory model with no-mmu riscv: Fix range looking for kernel image memblock drm/amdgpu: clean wptr on wb when gpu recovery drm/amd/display: Clear link settings on MST disable connector drm/amd/display: fix dcc swath size calculations on dcn1 xenbus: req->body should be updated before req->state xenbus: req->err should be updated before req->state block, bfq: fix overwrite of bfq_group pointer in bfq_find_set_group() parse-maintainers: Mark as executable binderfs: use refcount for binder control devices too Revert "drm/fbdev: Fallback to non tiled mode if all tiles not present" usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters USB: serial: option: add ME910G1 ECM composition 0x110b usb: host: xhci-plat: add a shutdown USB: serial: pl2303: add device-id for HP LD381 usb: xhci: apply XHCI_SUSPEND_DELAY to AMD XHCI controller 1022:145c usb: typec: ucsi: displayport: Fix NULL pointer dereference usb: typec: ucsi: displayport: Fix a potential race during registration USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL USB: cdc-acm: fix rounding error in TIOCSSERIAL ALSA: line6: Fix endless MIDI read loop ALSA: hda/realtek - Enable headset mic of Acer X2660G with ALC662 ALSA: hda/realtek - Enable the headset of Acer N50-600 with ALC662 ALSA: seq: virmidi: Fix running status after receiving sysex ALSA: seq: oss: Fix running status after receiving sysex ALSA: pcm: oss: Avoid plugin buffer overflow ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks tty: fix compat TIOCGSERIAL leaking uninitialized memory tty: fix compat TIOCGSERIAL checking wrong function ptr iio: chemical: sps30: fix missing triggered buffer dependency iio: st_sensors: remap SMO8840 to LIS2DH12 iio: trigger: stm32-timer: disable master mode when stopping iio: accel: adxl372: Set iio_chan BE iio: magnetometer: ak8974: Fix negative raw values in sysfs iio: adc: stm32-dfsdm: fix sleep in atomic context iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode iio: light: vcnl4000: update sampling periods for vcnl4200 iio: light: vcnl4000: update sampling periods for vcnl4040 mmc: rtsx_pci: Fix support for speed-modes that relies on tuning mmc: sdhci-of-at91: fix cd-gpios for SAMA5D2 mmc: sdhci-cadence: set SDHCI_QUIRK2_PRESET_VALUE_BROKEN for UniPhier CIFS: fiemap: do not return EINVAL if get nothing kbuild: Disable -Wpointer-to-enum-cast staging: rtl8188eu: Add device id for MERCUSYS MW150US v2 staging: greybus: loopback_test: fix poll-mask build breakage staging/speakup: fix get_word non-space look-ahead intel_th: msu: Fix the unexpected state warning intel_th: Fix user-visible error codes intel_th: pci: Add Elkhart Lake CPU support modpost: move the namespace field in Module.symvers last rtc: max8907: add missing select REGMAP_IRQ arm64: compat: Fix syscall number of compat_clock_getres xhci: Do not open code __print_symbolic() in xhci trace events btrfs: fix log context list corruption after rename whiteout error drm/amd/amdgpu: Fix GPR read from debugfs (v2) drm/lease: fix
[Kernel-packages] [Bug 1863574] Re: Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04
** Also affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Michael Reed (mreed8855) Status: In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- 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/1863574 Title: Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] This is a feature request to update the mpt3sas driver in focal to latest version 33.100.00.00 in Ubuntu 20.04. This will allow users to use fixes and enhancements that landed upstream in 5.6. For this reason, Broadcom and Dell have requested that we pull these patches to update the mpt3sas driver to the current upstream version. [FIXES] The following commit ID's from Broadcom that whould be cherry-picked form mainline commit c53cf10ef6d9faeee9baa1fab824139c6f10a134 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c53cf10ef6d9faeee9baa1fab824139c6f10a134 commit c50ed99cd56ee725d9e14dffec8e8f1641b8ca30 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c50ed99cd56ee725d9e14dffec8e8f1641b8ca30 commit c6bdb6a10892d1130638a5e28d1523a813e45d5e https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c6bdb6a10892d1130638a5e28d1523a813e45d5e commit 5b061980e362820894d7d884370b37005bed23ec https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5b061980e362820894d7d884370b37005bed23ec commit c59777189433621392f6f5c82ecfc62f00a1232d https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c59777189433621392f6f5c82ecfc62f00a1232d commit fce0aa08792b3ae725395fa25d44507dee0b603b https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=fce0aa08792b3ae725395fa25d44507dee0b603b commit e8c2307e6a690db9aaff84153b2857c5c4dfd969 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=e8c2307e6a690db9aaff84153b2857c5c4dfd969 commit 36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0 commit d3f623ae8e0323ca434ee9029100312a8be37773 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d3f623ae8e0323ca434ee9029100312a8be37773 commit 1ade26b616cc2da0b7277a97e3799c99bae0655b https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=1ade26b616cc2da0b7277a97e3799c99bae0655b commit ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb commit 5bb2f743cdaa6da618e77a6aab5c38b46072365b https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5bb2f743cdaa6da618e77a6aab5c38b46072365b commit 3524a38e594dd5f090cbc3226e5f47cb4067fac7 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=3524a38e594dd5f090cbc3226e5f47cb4067fac7 commit d8b2625f4699a36b1753d87e96b0c50a4531c065 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d8b2625f4699a36b1753d87e96b0c50a4531c065 commit 9e64fd1e65f72d229f96fcf390576e772770a01c https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=9e64fd1e65f72d229f96fcf390576e772770a01c commit 77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9 commit b06ff10249036eec74fa8565503ac40d0ee92213 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=b06ff10249036eec74fa8565503ac40d0ee92213 commit 29f571f8b4cc652cae9244630f714a610549d301 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=29f571f8b4cc652cae9244630f714a610549d301 commit a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d commit a066f4c31359d07b1a2c5144b4b9a29901365fd0 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a066f4c31359d07b1a2c5144b4b9a29901365fd0 commit dd180e4eedfd85b80020a6fd566601f4765a9d69 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=dd180e4eedfd85b80020a6fd566601f4765a9d69 commit 08e7378ee331a803cfdd91c512a3dea040f1da79 https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=08e7378ee331a803cfdd91c512a3dea040f1da79 commit
[Kernel-packages] [Bug 1863581] Re: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1
** Also affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Michael Reed (mreed8855) Status: In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- 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/1863581 Title: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] This is a feature request to update megaraid_sas driver in Ubuntu 20.04 release to latest Linux upstream tip. The current latest upstream megaraid_sas driver version is- 07.713.01.00-rc1. The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver version- 07.710.50.00-rc1. [FIXES] Below set of upstream commit ids will lift driver version to 07.713.01.00-rc1 from 07.710.50.00-rc1: 92b4f9d15059 scsi: megaraid_sas: fixup MSIx interrupt setup during resume 824b72db5086 scsi: megaraid_sas: Update driver version to 07.713.01.00-rc1 4d1634b8d12e scsi: megaraid_sas: Use Block layer API to check SCSI device in-flight IO requests 56ee0c585602 scsi: megaraid_sas: Limit the number of retries for the IOCTLs causing firmware fault 6d7537270e32 scsi: megaraid_sas: Do not initiate OCR if controller is not in ready state 201a810cc188 scsi: megaraid_sas: Re-Define enum DCMD_RETURN_STATUS eeb63c23ffe1 scsi: megaraid_sas: Do not set HBA Operational if FW is not in operational state 9330a0fd827a scsi: megaraid_sas: Do not kill HBA if JBOD Seqence map or RAID map is disabled eb974f34bb9d scsi: megaraid_sas: Do not kill host bus adapter, if adapter is already dead 6e73550670ed scsi: megaraid_sas: Update optimal queue depth for SAS and NVMe devices a7faf81d7858 scsi: megaraid_sas: Set no_write_same only for Virtual Disk 499e7246d6da scsi: megaraid_sas: Reset adapter if FW is not in READY state after device resume 73374b39b01e scsi: megaraid_sas: Make poll_aen_lock static 01b8bca81e18 compat_ioctl: use correct compat_ptr() translation in drivers 8cfb8e40d686 scsi: megaraid_sas: remove unused variables 'debugBlk','fusion' ff7ca7fd03ce scsi: megaraid_sas: Unique names for MSI-X vectors 9ab089d30bcf scsi: megaraid_sas: Introduce module parameter for default queue depth e5460f084b84 scsi: megaraid_sas: Fix a compilation warning 88d5c343949e scsi: megaraid_sas: Make a bunch of functions static e45ab43b1d40 scsi: megaraid_sas: Make some functions static 3b5f307ef3cb scsi: megaraid_sas: fix panic on loading firmware crashdump 359603a3847e scsi: megaraid_sas: fix spelling mistake "megarid_sas" -> "megaraid_sas" 07d9aa143464 scsi: megaraid_sas: set an unlimited max_segment_size Here is the link to latest Linux upstream megaraid_sas driver source: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid Please let me know if any further information is required. Thanks, Sumit All are clean cherry picks into the 5.4 branch and can be pulled from the following branch: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp1863581_megaraid_sas [TESTING] Modinfo should show that the megaraid_sas driver has been updated to 07.713.01.00 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863581/+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 1867684] Re: Wifi fails to work with newer kernels
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867684 Title: Wifi fails to work with newer kernels Status in linux package in Ubuntu: Fix Released Bug description: When I boot Ubuntu normally with the most recent kernel image WiFi will not work, I will get this message, Network activation error,so I boot up Ubuntu to other generic kernels, 5.4.0-18 and 5.4.0-18-generic and I still receive the same message, finally I boot to kernel 5.2.0-15-generic and the WiFi works perfectly fine! see also bug #1867797 for info of when i booted into the 5.4.0 kernels Description: Ubuntu Focal Fossa (development branch) Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 1740 F pulseaudio /dev/snd/controlC0: administrator 1740 F pulseaudio DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-06-05 (285 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook 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.2.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 RelatedPackageVersions: linux-restricted-modules-5.2.0-15-generic N/A linux-backports-modules-5.2.0-15-generic N/A linux-firmware1.186 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.2.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867684/+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 1861359] Re: swap storms kills interactive use
BTW, this is still happening in: Linux millbarge 5.4.0-20-generic #24-Ubuntu SMP Mon Mar 23 20:55:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I've seen it both with firefox in trello, firefox in launchpad (typing this comment) and doing two sequential wgets of http://releases.ubuntu.com/18.04/ubuntu-18.04.4-desktop-amd64.iso (a 1.8 GB file). 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/1861359 Title: swap storms kills interactive use Status in linux package in Ubuntu: Confirmed Bug description: Hello, several times since upgrading to focal from 19.04 I've found my computer entirely unresponsive for periods of twenty or thirty seconds. No mouse movement, no keyboard input, the screen output does not change. My computer was using swap space and despite very slow writeout speeds well below what the NVME drive can handle, the computer was unusable. I've captured some vmstat 1 output and top output that I started collecting during the event. (Normally one very long painful period is followed by several shorter periods of uselessness.) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Wed Jan 29 23:44:05 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET69W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW 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:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1
[Kernel-packages] [Bug 1869083] 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/1869083 Title: pipe state doesn't match! [i915] Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 7390 with Dell WD15 with 2 external screens (on HDMI and DP) Ubuntu 5.3.0-42.34-generic 5.3.18 Description: Ubuntu 19.10 Release: 19.10 Kernel crash while idling unattended: Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216046] [ cut here ] Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216046] pipe state doesn't match! Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216094] WARNING: CPU: 6 PID: 3714 at drivers/gpu/drm/i915/display/intel_display.c:13006 verify_crtc_state+0x2ad/0x300 [i915] Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216094] Modules linked in: rfcomm binfmt_misc veth nft_masq nft_chain_nat bridge stp llc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filte r ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter nf_tables nfnetlink ccm typec_displayport cmac bnep nls_is o8859_1 sof_pci_dev snd_sof_intel_hda_common snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus snd_pcm_dmaengine joydev snd_hda_intel mei_hdcp snd_intel_nhlt snd_hda_codec snd_hda_core intel_rapl_msr snd_usb_audio snd_usbmidi_lib snd_hwdep snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216108] coretemp snd_seq_midi mac80211 snd_seq_midi_event kvm_intel libarc4 dell_laptop ledtrig_audio snd_rawmidi kvm snd_seq irqbypass dell_wmi intel_cstate dell_smbios intel_rapl_perf dcdbas uvcvideo iwlwifi snd_seq_device input_leds dell_wmi_descriptor snd_timer videobuf2_vmalloc cdc_ether serio_raw videobuf2_memops usbnet intel_wmi_thunderbolt videobuf2_v4l2 btusb r8152 btrtl videobuf2_common mii btbcm btintel snd videodev wmi_bmof bluetooth rtsx_pci_ms mc soundcore cfg80211 memstick mei_me ecdh_generic hid_multitouch mei ecc idma64 virt_dma processor_thermal_device intel_rapl_common intel_soc_dts_iosf ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone mac_hid intel_hid acpi_tad int3400_thermal acpi_pad acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt hid_generic uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rtsx_pci_sdmmc i915 aesni_intel aes_x86_64 crypto_simd cryptd glue_helper Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216123] i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt fb_sys_fops i2c_i801 thunderbolt nvme_core drm rtsx_pci intel_lpss_pci intel_lpss i2c_hid wmi hid pinctrl_cannonlake video pinctrl_intel Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216129] CPU: 6 PID: 3714 Comm: gnome-shell Tainted: PW O 5.3.0-42-generic #34-Ubuntu Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216129] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.4.0 11/25/2019 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216144] RIP: 0010:verify_crtc_state+0x2ad/0x300 [i915] Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216145] Code: b6 45 bf e9 8d fe ff ff 80 3d 55 0d 10 00 00 0f b6 f0 48 c7 c7 f0 93 92 c0 75 32 e8 9d d7 9d ff e9 1e fe ff ff e8 7e cf 04 e6 <0f> 0b e9 1b ff ff ff e8 72 cf 04 e6 0f 0b e9 85 fe ff ff e8 66 cf Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216145] RSP: 0018:af5cc5fa3ac8 EFLAGS: 00010282 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216146] RAX: RBX: 914b6b5e02b0 RCX: 0006 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216147] RDX: 0007 RSI: 0086 RDI: 914b7e797440 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216147] RBP: af5cc5fa3b10 R08: d967 R09: 0004 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216147] R10: R11: 0001 R12: 914b7bcd3000 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216148] R13: 914b6b5e02b8 R14: 914b6b5e R15: 914b20336000 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216148] FS: 7f0835d3ecc0() GS:914b7e78() knlGS: Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216149] CS: 0010 DS: ES: CR0: 80050033 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216149] CR2: 3b18df55a000 CR3: 0003ee6f2005 CR4:
[Kernel-packages] [Bug 1869062] Re: Acer Aspire 7715 microphone not detected
NOTE: I am NOT the originator of this bug report, but have a similar(? identical?) problem. My machine is an Acer Aspire E17 E5-722-425Q, and the built-in microphone (and also the mouse pad) has never(?) been detected. (Since I use a USB mouse and a USB headset-with-microphone, neither problem has ever bothered me in the slightest.) Sometimes, the built-in WiFi is not detected (as is the case at the moment), and, usually, the built-in Bluetooth is not detected (also the case at the moment). However, I *have* observed that, at least in the case of the WiFi (the Bluetooth is not-so-clear) it seems to be related to the temperature (especially the external (ambient, i.e., room temperature)). Whilst no measurements have been made, if the ambient temperature is sufficiently cool (cold, actually, PROBABLY less than 10 degrees Celsius (estimated)), the WiFi is frequently detected. When it is warm, it is much more hit-and-miss. (There are some circumstantial reasons to think, for both the WiFi and Bluetooth (both are USB), that if there certain unclear external USB devices are also attached when the system is booted, than one or both is detected. Apologies for being quite vague here, I have never tried to confirm or characterise this incidental observation.) Attached is the RAW report generated by apport-cli(1); I do not know how to automagically append it to a bug which I did not originally create. However, please note that, at the moment, neither the built-in USB WiFi nor the built-in USB Bluetooth is currently detected (and the ambient temperature is currently quite warm). ** Attachment added: "1869062" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869062/+attachment/5341699/+files/1869062 -- 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/1869062 Title: Acer Aspire 7715 microphone not detected Status in linux package in Ubuntu: Incomplete Bug description: System:Host: jdole-Aspire-7715Z Kernel: 4.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Acer product: Aspire 7715Z v: V3.04 serial: Mobo: Acer model: Aspire 7715Z v: V3.04 serial: BIOS: Acer v: 3.04 date: 12/16/2009 CPU: Topology: Dual Core model: Pentium T4400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8778 Speed: 2195 MHz min/max: 1200/2200 MHz Core speeds (MHz): 1: 2195 2: 2195 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 19.2.8 direct render: Yes Audio: Device-1: Intel 82801I HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e Sound Server: ALSA v: k4.15.0-91-generic Network: Device-1: Qualcomm Atheros AR928X Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel port: 5000 bus ID: 04:00.0 chip ID: 168c:002a IF: wlp4s0 state: up mac: Device-2: Qualcomm Atheros AR8132 Fast Ethernet vendor: Acer Incorporated ALI driver: atl1c v: 1.0.1.1-NAPI port: 1000 bus ID: 05:00.0 chip ID: 1969:1062 IF: enp5s0 state: down mac: Drives:Local Storage: total: 465.76 GiB used: 33.06 GiB (7.1%) ID-1: /dev/sda vendor: Western Digital model: WD5000BEVT-22A0RT0 size: 465.76 GiB speed: 3.0 Gb/s serial: Partition: ID-1: / size: 211.37 GiB used: 33.06 GiB (15.6%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 54.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mint.remi.lu tricia main upstream import backport 2: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic main restricted universe multiverse 3: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/
[Kernel-packages] [Bug 1869083] [NEW] pipe state doesn't match! [i915]
Public bug reported: Dell XPS 7390 with Dell WD15 with 2 external screens (on HDMI and DP) Ubuntu 5.3.0-42.34-generic 5.3.18 Description:Ubuntu 19.10 Release:19.10 Kernel crash while idling unattended: Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216046] [ cut here ] Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216046] pipe state doesn't match! Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216094] WARNING: CPU: 6 PID: 3714 at drivers/gpu/drm/i915/display/intel_display.c:13006 verify_crtc_state+0x2ad/0x300 [i915] Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216094] Modules linked in: rfcomm binfmt_misc veth nft_masq nft_chain_nat bridge stp llc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filte r ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter bpfilter nf_tables nfnetlink ccm typec_displayport cmac bnep nls_is o8859_1 sof_pci_dev snd_sof_intel_hda_common snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus snd_pcm_dmaengine joydev snd_hda_intel mei_hdcp snd_intel_nhlt snd_hda_codec snd_hda_core intel_rapl_msr snd_usb_audio snd_usbmidi_lib snd_hwdep snd_pcm x86_pkg_temp_thermal intel_powerclamp iwlmvm Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216108] coretemp snd_seq_midi mac80211 snd_seq_midi_event kvm_intel libarc4 dell_laptop ledtrig_audio snd_rawmidi kvm snd_seq irqbypass dell_wmi intel_cstate dell_smbios intel_rapl_perf dcdbas uvcvideo iwlwifi snd_seq_device input_leds dell_wmi_descriptor snd_timer videobuf2_vmalloc cdc_ether serio_raw videobuf2_memops usbnet intel_wmi_thunderbolt videobuf2_v4l2 btusb r8152 btrtl videobuf2_common mii btbcm btintel snd videodev wmi_bmof bluetooth rtsx_pci_ms mc soundcore cfg80211 memstick mei_me ecdh_generic hid_multitouch mei ecc idma64 virt_dma processor_thermal_device intel_rapl_common intel_soc_dts_iosf ucsi_acpi typec_ucsi typec int3403_thermal int340x_thermal_zone mac_hid intel_hid acpi_tad int3400_thermal acpi_pad acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt hid_generic uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rtsx_pci_sdmmc i915 aesni_intel aes_x86_64 crypto_simd cryptd glue_helper Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216123] i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt fb_sys_fops i2c_i801 thunderbolt nvme_core drm rtsx_pci intel_lpss_pci intel_lpss i2c_hid wmi hid pinctrl_cannonlake video pinctrl_intel Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216129] CPU: 6 PID: 3714 Comm: gnome-shell Tainted: PW O 5.3.0-42-generic #34-Ubuntu Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216129] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.4.0 11/25/2019 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216144] RIP: 0010:verify_crtc_state+0x2ad/0x300 [i915] Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216145] Code: b6 45 bf e9 8d fe ff ff 80 3d 55 0d 10 00 00 0f b6 f0 48 c7 c7 f0 93 92 c0 75 32 e8 9d d7 9d ff e9 1e fe ff ff e8 7e cf 04 e6 <0f> 0b e9 1b ff ff ff e8 72 cf 04 e6 0f 0b e9 85 fe ff ff e8 66 cf Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216145] RSP: 0018:af5cc5fa3ac8 EFLAGS: 00010282 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216146] RAX: RBX: 914b6b5e02b0 RCX: 0006 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216147] RDX: 0007 RSI: 0086 RDI: 914b7e797440 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216147] RBP: af5cc5fa3b10 R08: d967 R09: 0004 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216147] R10: R11: 0001 R12: 914b7bcd3000 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216148] R13: 914b6b5e02b8 R14: 914b6b5e R15: 914b20336000 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216148] FS: 7f0835d3ecc0() GS:914b7e78() knlGS: Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216149] CS: 0010 DS: ES: CR0: 80050033 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216149] CR2: 3b18df55a000 CR3: 0003ee6f2005 CR4: 003606e0 Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216150] Call Trace: Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216167] intel_atomic_commit_tail+0x6db/0x1130 [i915] Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216182] intel_atomic_commit+0x28f/0x2c0 [i915] Mar 25 21:31:30 nikolaj-fauna kernel: [53511.216193] drm_atomic_commit+0x4a/0x50 [drm] Mar 25 21:31:30 nikolaj-fauna kernel:
[Kernel-packages] [Bug 1868189] Re: Low memory situations result in root partition being remounted read-only
** Package changed: ubuntu => linux (Ubuntu) -- 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/1868189 Title: Low memory situations result in root partition being remounted read- only Status in linux package in Ubuntu: New Bug description: Instead of killing something with a high niceness low memory situations seem to hang something super-ultra-so-very vital, writes fail and the root partition is remounted read-only. After that systemd-journald starts stupidly spamming and earlier logs are rendered unusable. I'd post more logs but https://github.com/systemd/systemd/issues/2339 hasn't been fixed in years. This has happened at least four times, across many kernel versions. With Ubuntu 18.10, 19.04 and 19.10. ``` [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 00 10 00 [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871518) [827788.409154] Buffer I/O error on device dm-1, logical block 3871518 [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871519) [827788.409164] Buffer I/O error on device dm-1, logical block 3871519 [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 00 08 00 [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871598) [827788.409180] Buffer I/O error on device dm-1, logical block 3871598 [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 00 38 00 [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0 [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871564) [827788.409195] Buffer I/O error on device dm-1, logical block 3871564 [827788.409196] Buffer I/O error on device dm-1, logical block 3871565 [827788.409198] Buffer I/O error on device dm-1, logical block 3871566 [827788.409199] Buffer I/O error on device dm-1, logical block 3871567 [827788.409201] Buffer I/O error on device dm-1, logical block 3871568 [827788.409202] Buffer I/O error on device dm-1, logical block 3871569 [827788.409203] Buffer I/O error on device dm-1, logical block 3871570 [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 00 08 00 [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871558) [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 00 08 00 [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871562) [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 00 08 00 [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871601) [827818.628273] sd 5:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628276] sd 5:0:0:0: [sdb] tag#31 CDB: Write(10) 2a 00 01 cf 12 38 00 00 30 00 [827818.628279] blk_update_request: I/O error, dev sdb, sector 30347832 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0 [827818.628347] sd 5:0:0:0: [sdb] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628351] sd 5:0:0:0: [sdb] tag#28 CDB: Write(10) 2a 00 01 93 2f b0 00 00
[Kernel-packages] [Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
It seems that I have the same issue with my HP ZBook that Ubuntu doesn't boot since kernel 4.15.0-72-generic release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release Status in linux package in Ubuntu: Confirmed Bug description: After the update to install kernel 4.15.0-72-generic (a bit over a week ago) my computer will not boot. On boot, all I see is the purple screen with: Loading Linux 4.15.0-72-generic ... Loading initial ramdisk ... and nothing happens. Just sits there. I've waited about 5-10 minutes on occasion but to no avail. I've checked a number of logs in /var/log but not found anything. If I go into the advanced options and select kernel 4.15.0-70-generic, the computer boots normally. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 21:53:14 2019 HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1 InstallationDate: Installed on 2018-09-16 (454 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE Sabre 17WV8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off RelatedPackageVersions: linux-restricted-modules-4.15.0-70-generic N/A linux-backports-modules-4.15.0-70-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F05 dmi.board.asset.tag: Tag 12345 dmi.board.name: Sabre 17WV8 dmi.board.vendor: GIGABYTE dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF05:bd05/22/2018:svnGIGABYTE:pnSabre17WV8:pvrNotApplicable:rvnGIGABYTE:rnSabre17WV8:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A: dmi.product.family: Sabre dmi.product.name: Sabre 17WV8 dmi.product.version: Not Applicable dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+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 1868189] [NEW] Low memory situations result in root partition being remounted read-only
You have been subscribed to a public bug: Instead of killing something with a high niceness low memory situations seem to hang something super-ultra-so-very vital, writes fail and the root partition is remounted read-only. After that systemd-journald starts stupidly spamming and earlier logs are rendered unusable. I'd post more logs but https://github.com/systemd/systemd/issues/2339 hasn't been fixed in years. This has happened at least four times, across many kernel versions. With Ubuntu 18.10, 19.04 and 19.10. ``` [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 00 10 00 [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871518) [827788.409154] Buffer I/O error on device dm-1, logical block 3871518 [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871519) [827788.409164] Buffer I/O error on device dm-1, logical block 3871519 [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 00 08 00 [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871598) [827788.409180] Buffer I/O error on device dm-1, logical block 3871598 [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 00 38 00 [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0 [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871564) [827788.409195] Buffer I/O error on device dm-1, logical block 3871564 [827788.409196] Buffer I/O error on device dm-1, logical block 3871565 [827788.409198] Buffer I/O error on device dm-1, logical block 3871566 [827788.409199] Buffer I/O error on device dm-1, logical block 3871567 [827788.409201] Buffer I/O error on device dm-1, logical block 3871568 [827788.409202] Buffer I/O error on device dm-1, logical block 3871569 [827788.409203] Buffer I/O error on device dm-1, logical block 3871570 [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 00 08 00 [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871558) [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 00 08 00 [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871562) [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 00 08 00 [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871601) [827818.628273] sd 5:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628276] sd 5:0:0:0: [sdb] tag#31 CDB: Write(10) 2a 00 01 cf 12 38 00 00 30 00 [827818.628279] blk_update_request: I/O error, dev sdb, sector 30347832 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0 [827818.628347] sd 5:0:0:0: [sdb] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628351] sd 5:0:0:0: [sdb] tag#28 CDB: Write(10) 2a 00 01 93 2f b0 00 00 08 00 [827818.628353] blk_update_request: I/O error, dev sdb, sector 26423216 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827818.628358] Aborting journal on device dm-1-8. [827818.628374] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3236342) [827818.628379] buffer_io_error: 3 callbacks suppressed [827818.628381] Buffer I/O error
[Kernel-packages] [Bug 1868189] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1868189 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868189 Title: Low memory situations result in root partition being remounted read- only Status in linux package in Ubuntu: Incomplete Bug description: Instead of killing something with a high niceness low memory situations seem to hang something super-ultra-so-very vital, writes fail and the root partition is remounted read-only. After that systemd-journald starts stupidly spamming and earlier logs are rendered unusable. I'd post more logs but https://github.com/systemd/systemd/issues/2339 hasn't been fixed in years. This has happened at least four times, across many kernel versions. With Ubuntu 18.10, 19.04 and 19.10. ``` [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 00 10 00 [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871518) [827788.409154] Buffer I/O error on device dm-1, logical block 3871518 [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871519) [827788.409164] Buffer I/O error on device dm-1, logical block 3871519 [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 00 08 00 [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871598) [827788.409180] Buffer I/O error on device dm-1, logical block 3871598 [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 00 38 00 [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0 [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871564) [827788.409195] Buffer I/O error on device dm-1, logical block 3871564 [827788.409196] Buffer I/O error on device dm-1, logical block 3871565 [827788.409198] Buffer I/O error on device dm-1, logical block 3871566 [827788.409199] Buffer I/O error on device dm-1, logical block 3871567 [827788.409201] Buffer I/O error on device dm-1, logical block 3871568 [827788.409202] Buffer I/O error on device dm-1, logical block 3871569 [827788.409203] Buffer I/O error on device dm-1, logical block 3871570 [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 00 08 00 [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871558) [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 00 08 00 [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871562) [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 00 08 00 [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10
[Kernel-packages] [Bug 1869062] Re: Acer Aspire 7715 microphone not detected
Follow-up to #2 (again, please note I am NOT the originator of this report). Searching through some old notes/logs, I found the attached information about _my_ WiFi H/W (excerpted and slightly redacted because I have not checked the complete notes/logs for sensitive information). Abbreviated summary (from `hwinfo --all', see attachment for more details): 13: PCI 300.0: 0282 WLAN controller [...] Model: "Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter" Vendor: pci 0x168c "Qualcomm Atheros" Device: pci 0x0042 "QCA9377 802.11ac Wireless Network Adapter" SubVendor: pci 0x11ad "Lite-On Communications Inc" SubDevice: pci 0x0806 Revision: 0x30 Driver: "ath10k_pci" Driver Modules: "ath10k_pci" Device File: wlp3s0 Features: WLAN Memory Range: 0xf080-0xf09f (rw,non-prefetchable) IRQ: 47 (1789 events) HW Address: [REDACTED] Permanent HW Address: [REDACTED (same)] Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v168Cd0042sv11ADsd0806bc02sc80i00" Driver Info #0: Driver Status: ath10k_pci is active [...] Unfortunately, the (less likely to be detected) builtin USB Bluetooth was not detected. ;-( ** Attachment added: "Assorted WiFi-related excerpts from notes/logs of Jan-2020" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869062/+attachment/5341708/+files/Aspire-E17-WiFi.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/1869062 Title: Acer Aspire 7715 microphone not detected Status in linux package in Ubuntu: Incomplete Bug description: System:Host: jdole-Aspire-7715Z Kernel: 4.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Acer product: Aspire 7715Z v: V3.04 serial: Mobo: Acer model: Aspire 7715Z v: V3.04 serial: BIOS: Acer v: 3.04 date: 12/16/2009 CPU: Topology: Dual Core model: Pentium T4400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8778 Speed: 2195 MHz min/max: 1200/2200 MHz Core speeds (MHz): 1: 2195 2: 2195 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 19.2.8 direct render: Yes Audio: Device-1: Intel 82801I HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e Sound Server: ALSA v: k4.15.0-91-generic Network: Device-1: Qualcomm Atheros AR928X Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel port: 5000 bus ID: 04:00.0 chip ID: 168c:002a IF: wlp4s0 state: up mac: Device-2: Qualcomm Atheros AR8132 Fast Ethernet vendor: Acer Incorporated ALI driver: atl1c v: 1.0.1.1-NAPI port: 1000 bus ID: 05:00.0 chip ID: 1969:1062 IF: enp5s0 state: down mac: Drives:Local Storage: total: 465.76 GiB used: 33.06 GiB (7.1%) ID-1: /dev/sda vendor: Western Digital model: WD5000BEVT-22A0RT0 size: 465.76 GiB speed: 3.0 Gb/s serial: Partition: ID-1: / size: 211.37 GiB used: 33.06 GiB (15.6%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 54.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mint.remi.lu tricia main upstream import backport 2: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic main restricted universe multiverse 3: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-backports main restricted universe multiverse 5: deb
[Kernel-packages] [Bug 1530617] Re: FUSE in wily image with upstart installed causes chaos
** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid ** Changed in: upstart (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1530617 Title: FUSE in wily image with upstart installed causes chaos Status in linux package in Ubuntu: Invalid Status in lxc package in Ubuntu: Invalid Status in upstart package in Ubuntu: Won't Fix Bug description: Host: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.10 DISTRIB_CODENAME=wily DISTRIB_DESCRIPTION="Ubuntu 15.10" lxc version: 1.1.4-0ubuntu1 In a LXC container running Ubuntu 15.10, install upstart-sysv to replace systemd. Using FUSE then causes almost all processes in the container to be killed. The following steps reproduce the problem using sshfs: # create a wily container and attach to it sudo lxc-create -t download -n wily -- -d ubuntu -r wily -a amd64 sudo lxc-start -n wily sudo lxc-attach -n wily # inside the container, install upstart-sysv and reboot apt-get update && apt-get -y install upstart-sysv reboot # on the host, reattach to the container sudo lxc-attach -n wily # back in the container, install ssh and sshfs apt-get -y install openssh-server sshfs # create an ssh key pair in /root/.ssh ssh-keygen # set up passwordless ssh mkdir ~ubuntu/.ssh cat /root/.ssh/id_rsa.pub >> ~ubuntu/.ssh/authorized_keys eval $(ssh-agent) ssh-add /root/.ssh/id_rsa # take a note of the running processes and their PIDs ps axjf # run sshfs mkdir /fuse sshfs ubuntu@localhost:/ /fuse # we are kicked out of the container # run ps again in the container sudo lxc-attach -n wily -- ps axjf # a whole bunch of processes are now gone. the getty processes now have new PIDs, indicating they have been restarted. Other debugging performed: - On a 14.10 host with lxc version 1.1.0~alpha2-0ubuntu3.3, the problem does not occur. FUSE works fine. - On the same 14.10 host with lxc upgraded to 1.1.5-0ubuntu3~ubuntu14.04.1, the problem occurs. - On a 15.10 host, when running a wily container without upstart, the problem does not occur. - On a 15.10 host, when running a trusty container, the problem does not occur. - The problem can't be reproduced outside a container (15.10 host, install upstart-sysv, then use FUSE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530617/+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 1863581] Re: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1
** Description changed: [IMPACT] - This is a feature request to update megaraid_sas driver in Ubuntu 20.04 release to latest Linux upstream tip. + This is a feature request to update megaraid_sas driver in Ubuntu 20.04 release to latest Linux upstream tip. The current latest upstream megaraid_sas driver version is- 07.713.01.00-rc1. - The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver version- 07.710.50.00-rc1. + The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver version- 07.710.50.00-rc1. This will allow users to utilize features of + the PERC 11 device. For this reason, Broadcom and Dell have requested that we pull these patches to update the megaraid_sas driver to the current upstream version. [FIXES] Below set of upstream commit ids will lift driver version to 07.713.01.00-rc1 from 07.710.50.00-rc1: 92b4f9d15059 scsi: megaraid_sas: fixup MSIx interrupt setup during resume 824b72db5086 scsi: megaraid_sas: Update driver version to 07.713.01.00-rc1 4d1634b8d12e scsi: megaraid_sas: Use Block layer API to check SCSI device in-flight IO requests 56ee0c585602 scsi: megaraid_sas: Limit the number of retries for the IOCTLs causing firmware fault 6d7537270e32 scsi: megaraid_sas: Do not initiate OCR if controller is not in ready state 201a810cc188 scsi: megaraid_sas: Re-Define enum DCMD_RETURN_STATUS eeb63c23ffe1 scsi: megaraid_sas: Do not set HBA Operational if FW is not in operational state 9330a0fd827a scsi: megaraid_sas: Do not kill HBA if JBOD Seqence map or RAID map is disabled eb974f34bb9d scsi: megaraid_sas: Do not kill host bus adapter, if adapter is already dead 6e73550670ed scsi: megaraid_sas: Update optimal queue depth for SAS and NVMe devices a7faf81d7858 scsi: megaraid_sas: Set no_write_same only for Virtual Disk 499e7246d6da scsi: megaraid_sas: Reset adapter if FW is not in READY state after device resume 73374b39b01e scsi: megaraid_sas: Make poll_aen_lock static 01b8bca81e18 compat_ioctl: use correct compat_ptr() translation in drivers 8cfb8e40d686 scsi: megaraid_sas: remove unused variables 'debugBlk','fusion' ff7ca7fd03ce scsi: megaraid_sas: Unique names for MSI-X vectors 9ab089d30bcf scsi: megaraid_sas: Introduce module parameter for default queue depth e5460f084b84 scsi: megaraid_sas: Fix a compilation warning 88d5c343949e scsi: megaraid_sas: Make a bunch of functions static e45ab43b1d40 scsi: megaraid_sas: Make some functions static 3b5f307ef3cb scsi: megaraid_sas: fix panic on loading firmware crashdump 359603a3847e scsi: megaraid_sas: fix spelling mistake "megarid_sas" -> "megaraid_sas" 07d9aa143464 scsi: megaraid_sas: set an unlimited max_segment_size Here is the link to latest Linux upstream megaraid_sas driver source: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid Please let me know if any further information is required. Thanks, Sumit All are clean cherry picks into the 5.4 branch and can be pulled from the following branch: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp1863581_megaraid_sas [TESTING] Modinfo should show that the megaraid_sas driver has been updated to 07.713.01.00 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases. -- 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/1863581 Title: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] This is a feature request to update megaraid_sas driver in Ubuntu 20.04 release to latest Linux upstream tip. The current latest upstream megaraid_sas driver version is- 07.713.01.00-rc1. The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver version- 07.710.50.00-rc1. This will allow users to utilize features of the PERC 11 device. For this reason, Broadcom and Dell have requested that we pull these patches to update the megaraid_sas driver to the current upstream version. [FIXES] Below set of upstream commit ids will lift driver version to 07.713.01.00-rc1 from 07.710.50.00-rc1: 92b4f9d15059 scsi: megaraid_sas: fixup MSIx interrupt setup during resume 824b72db5086 scsi: megaraid_sas: Update driver version to 07.713.01.00-rc1 4d1634b8d12e scsi: megaraid_sas: Use Block layer API to check SCSI device in-flight IO requests 56ee0c585602 scsi: megaraid_sas: Limit the number of retries for the IOCTLs causing firmware fault 6d7537270e32 scsi: megaraid_sas: Do not initiate OCR if controller is not in ready state 201a810cc188 scsi: megaraid_sas: Re-Define enum DCMD_RETURN_STATUS eeb63c23ffe1 scsi: megaraid_sas: Do not set HBA Operational if FW is not in
[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use
I'm adding the champagne tag to this bug to bring it to a potential wider audience; I think we may need to take more drastic steps like disabling swap on upgrades, not offering swap in our installers, etc., to try to have a better experience. Thanks ** Tags added: champagne -- 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/1861359 Title: swap storms kills interactive use Status in linux package in Ubuntu: Confirmed Bug description: Hello, several times since upgrading to focal from 19.04 I've found my computer entirely unresponsive for periods of twenty or thirty seconds. No mouse movement, no keyboard input, the screen output does not change. My computer was using swap space and despite very slow writeout speeds well below what the NVME drive can handle, the computer was unusable. I've captured some vmstat 1 output and top output that I started collecting during the event. (Normally one very long painful period is followed by several shorter periods of uselessness.) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Wed Jan 29 23:44:05 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET69W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW 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:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed'
[Kernel-packages] [Bug 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station
This bug might be related to https://bugzilla.kernel.org/show_bug.cgi?id=206901 ** Bug watch added: Linux Kernel Bug Tracker #206901 https://bugzilla.kernel.org/show_bug.cgi?id=206901 -- 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/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added connector: c263592d [id: 105] [master: 8e933bad] [ 344.365899] [drm] DM_MST: added connector: 44df80f6 [id: 116] [master: 8e933bad] Software: Ubuntu 19.10 - Ubuntu 5.3.0-24.26-generic 5.3.10 Linux 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci: (laptop + docking) 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.2 PCI
[Kernel-packages] [Bug 1313279] Re: xHCI host not responding to stop endpoint command
I went to https://bugzilla.kernel.org/show_bug.cgi?id=206901 ** Bug watch added: Linux Kernel Bug Tracker #206901 https://bugzilla.kernel.org/show_bug.cgi?id=206901 -- 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/1313279 Title: xHCI host not responding to stop endpoint command Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 Hardware: Intel NUC D34010WYK (Core i3 4010U) Memory: 4 gigabytes USD device: PCTV 292e DVB-T tuner I have 2 PCTV 292e DVB-T tuners connected to the system. When I start to use either of the tuner, the xHCI host crashes. Since I'm booting from an USB disk. If I only connect 1 of the tuners, the system works ok. It does not matter which one of the tuners I connect. [ 68.990396] xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command. [ 68.990402] xhci_hcd :00:14.0: Assuming host is dying, halting host. Sometimes this also leads to this: [ 638.183002] IP: [] usb_enable_link_state+0x2d/0x2f0 [ 638.183057] PGD 0 [ 638.183077] Oops: [#1] SMP I can also observe the same fault with OpenELEC Linux distribution that runs kernel 3.14 when I run the system from an internal SATA SSD drive (not from an external USB disk). lsusb -v: http://paste.ubuntu.com/7343384/ dmesg: http://sprunge.us/HMXH dmesg (crash type 2): http://sprunge.us/PSiX ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lubuntu-desktop 0.55 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 11:12:22 2014 InstallationDate: Installed on 2014-04-07 (19 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: lubuntu-meta UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1313279/+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 1868474] 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/1868474 Title: Lenovo ThinkPad P73 touchpad does not work *after* installation Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 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-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-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: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868474/+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 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Hey, Mr. Здравко (zdravko-garmev), thanks for the answer. Unfortunately, I have not experienced any changes, the problem continues ... In the last command rm linux-firmware_1.173.17_all.deb, the terminal asked me if I should delete the file, and I said yes, is that correct? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M]
[Kernel-packages] [Bug 1868189] Re: Low memory situations result in root partition being remounted read-only
I can't run this command because permanent logging stops and temporary logging is flooded by systemd. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868189 Title: Low memory situations result in root partition being remounted read- only Status in linux package in Ubuntu: Confirmed Bug description: Instead of killing something with a high niceness low memory situations seem to hang something super-ultra-so-very vital, writes fail and the root partition is remounted read-only. After that systemd-journald starts stupidly spamming and earlier logs are rendered unusable. I'd post more logs but https://github.com/systemd/systemd/issues/2339 hasn't been fixed in years. This has happened at least four times, across many kernel versions. With Ubuntu 18.10, 19.04 and 19.10. ``` [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 00 10 00 [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871518) [827788.409154] Buffer I/O error on device dm-1, logical block 3871518 [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871519) [827788.409164] Buffer I/O error on device dm-1, logical block 3871519 [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 00 08 00 [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871598) [827788.409180] Buffer I/O error on device dm-1, logical block 3871598 [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 00 38 00 [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0 [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871564) [827788.409195] Buffer I/O error on device dm-1, logical block 3871564 [827788.409196] Buffer I/O error on device dm-1, logical block 3871565 [827788.409198] Buffer I/O error on device dm-1, logical block 3871566 [827788.409199] Buffer I/O error on device dm-1, logical block 3871567 [827788.409201] Buffer I/O error on device dm-1, logical block 3871568 [827788.409202] Buffer I/O error on device dm-1, logical block 3871569 [827788.409203] Buffer I/O error on device dm-1, logical block 3871570 [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 00 08 00 [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871558) [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 00 08 00 [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871562) [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 00 08 00 [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871601) [827818.628273] sd 5:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628276] sd 5:0:0:0: [sdb] tag#31 CDB: Write(10) 2a 00 01 cf 12 38 00 00 30 00 [827818.628279] blk_update_request: I/O error, dev sdb, sector 30347832 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0 [827818.628347] sd 5:0:0:0: [sdb] tag#28 FAILED
[Kernel-packages] [Bug 1868438] Re: nvidia-dkms-418 418.74-0ubuntu1: nvidia kernel module failed to build [nv-linux.h:733:21: error: void value not ignored as it ought to be]
** Summary changed: - nvidia-dkms-418 418.74-0ubuntu1: nvidia kernel module failed to build + nvidia-dkms-418 418.74-0ubuntu1: nvidia kernel module failed to build [nv-linux.h:733:21: error: void value not ignored as it ought to be] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1868438 Title: nvidia-dkms-418 418.74-0ubuntu1: nvidia kernel module failed to build [nv-linux.h:733:21: error: void value not ignored as it ought to be] Status in nvidia-graphics-drivers-418 package in Ubuntu: New Bug description: This driver doesn't work properly. Sometimes when I restart my PC, my ubuntu doesn't load. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-418 (not installed) ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 DKMSKernelVersion: 5.3.0-42-generic Date: Thu Mar 19 18:03:03 2020 DuplicateSignature: dkms:nvidia-dkms-418:418.74-0ubuntu1:/var/lib/dkms/nvidia/418.74/build/common/inc/nv-linux.h:733:21: error: void value not ignored as it ought to be InstallationDate: Installed on 2020-03-19 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523) PackageVersion: 418.74-0ubuntu1 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-418 Title: nvidia-dkms-418 418.74-0ubuntu1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1868438/+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 1527374] Re: CVE-2015-8709
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-goldfish in Ubuntu. https://bugs.launchpad.net/bugs/1527374 Title: CVE-2015-8709 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Confirmed Status in linux-flo package in Ubuntu: Confirmed Status in linux-goldfish package in Ubuntu: Confirmed Status in linux-lts-quantal package in Ubuntu: Won't Fix Status in linux-lts-raring package in Ubuntu: Won't Fix Status in linux-lts-saucy package in Ubuntu: Won't Fix Status in linux-lts-utopic package in Ubuntu: Fix Released Status in linux-lts-vivid package in Ubuntu: Fix Released Status in linux-lts-wily package in Ubuntu: Fix Released Status in linux-lts-xenial package in Ubuntu: New Status in linux-mako package in Ubuntu: Confirmed Status in linux-manta package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Confirmed Status in linux source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: ** DISPUTED ** kernel/ptrace.c in the Linux kernel through 4.4.1 mishandles uid and gid mappings, which allows local users to gain privileges by establishing a user namespace, waiting for a root process to enter that namespace with an unsafe uid or gid, and then using the ptrace system call. NOTE: the vendor states "there is no kernel bug here." Break-Fix: - local-2015-8709 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527374/+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 1863222] Re: Sync hwdata 0.333-1 (main) from Debian unstable (main)
** Changed in: hwdata (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to hwdata in Ubuntu.
https://bugs.launchpad.net/bugs/1863222
Title:
Sync hwdata 0.333-1 (main) from Debian unstable (main)
Status in hwdata package in Ubuntu:
New
Status in hwdata package in Debian:
New
Bug description:
Please sync hwdata 0.333-1 (main) from Debian unstable (main)
It has updated packaging and newer IDs useful for the new LTS.
Explanation of the Ubuntu delta and why it can be dropped:
* debian/rules:
- don't install deprecated changelog
The Ubuntu delta can be dropped because it's already in the Debian
package.
Changelog entries since current focal version 0.317-0ubuntu2:
hwdata (0.333-1) unstable; urgency=medium
* New upstream release: (Closes: #947191)
- pnp.ids: update Goldstar to LG Electronics (Closes: #95)
-- Pino Toscano Thu, 12 Mar 2020 06:45:31 +0100
hwdata (0.290-2) unstable; urgency=medium
* Take over the maintainership from Noël Köthe, with his permission.
Thanks for maintaining hwdata so far!
* Add the configuration for the CI on salsa.
* Stop shipping, and installing, a ChangeLog file generated from the
upstream Git repository, as it is not useful.
* Move the installation of pnp.ids to a hwdata.install file, instead of
copying it manually.
* Move the symlinks creation to a hwdata.links file, instead of passing
them as arguments of dh_link.
* Stop patching usb.ids, as we do not ship it anyway.
* Switch source format to "3.0 (quilt)".
* Bump the debhelper compatibility to 12:
- switch the debhelper build dependency to debhelper-compat 12
- remove debian/compat
* Rewrite rules to the dh sequencer, with no specific buildsystem.
* Remove dirs file, as the right directories are automatically created.
* Stop using the ${shlibs:Depends} substvar, as it does not exist in
arch:all binaries.
* Upstream moved to GitHub, so:
- switch Homepage to https://github.com/vcrhonek/hwdata
- switch watch file to GitHub tags
* Add Vcs-* fields.
* Remove README.build, as we do not ship usb.ids.
* Remove trailing whitespaces in changelog.
* Bump Standards-Version to 4.5.0, no changes required.
* Mark hwdata as Multi-Arch: foreign.
* Set Rules-Requires-Root: no.
-- Pino Toscano Fri, 06 Mar 2020 20:47:41 +0100
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1863222/+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 1868474] Re: Lenovo ThinkPad P73 touchpad does not work *after* installation
This looks relevant: [ 6.732] (II) event6 - ETPS/2 Elantech Touchpad: device is a touchpad [ 6.732] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse1) [ 6.732] (II) No input driver specified, ignoring this device. [ 10652.396] (II) config/udev: Adding input device Telink Wireless Receiver Mouse (/dev/input/mouse2) [ 10652.396] (II) No input driver specified, ignoring this device. ** Summary changed: - 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 + Lenovo ThinkPad P73 touchpad does not work *after* installation ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868474 Title: Lenovo ThinkPad P73 touchpad does not work *after* installation Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 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-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-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: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1684481] Re: KVM guest execution start apparmor blocks on /dev/ptmx now (regression?)
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1684481 Title: KVM guest execution start apparmor blocks on /dev/ptmx now (regression?) Status in apparmor package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Invalid Status in lxc package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Bug description: Setup: - Xenial host - lxd guests with Trusty, Xenial, ... - add a LXD profile to allow kvm [3] (inspired by stgraber) - spawn KVM guests in the LXD guests using the different distro release versions - guests are based on the uvtool default template which has a serial console [4] Issue: - guest starting with serial device gets blocked by apparmor and killed on creation - This affects at least ppc64el and x86 (s390x has no serial concept that would match) - This appeared in our usual checks on -proposed releases so maybe we can/should stop something? Last good was "Apr 5, 2017 10:40:50 AM" first bad one "Apr 8, 2017 5:11:22 AM" Background: We use this setup for a while and it was working without a change on our end. Also the fact that it still works in the Trusty LXD makes it somewhat suspicious. Therefore I'd assume an SRUed change in LXD/Kernel/Apparmor might be the reason and open this bug to get your opinion on it. You can look into [1] and search for uvt-kvm create in it. Deny in dmesg: [652759.606218] audit: type=1400 audit(1492671353.134:4520): apparmor="DENIED" operation="open" namespace="root//lxd-testkvm-xenial-from_" profile="libvirt-668e21f1-fa55-4a30-b325-0ed5cfd55e5b" name="/dev/pts/ptmx" pid=27162 comm="qemu-system-ppc" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Qemu-log: 2017-04-20T06:55:53.139450Z qemu-system-ppc64: -chardev pty,id=charserial0: Failed to create PTY: No such file or directory There was a similar issue on qmeu namespacing (which we don't use on any of these releases) [2]. While we surely don't have the "same" issue the debugging on the namespacing might be worth as it could be related. Workaround for now: - drop serial section from guest xml [1]: https://jenkins.ubuntu.com/server/view/Virt/job/virt-migration-cross-release-amd64/78/consoleFull [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1421036 [3]: https://git.launchpad.net/~ubuntu-server/ubuntu/+source/qemu-migration-test/tree/kvm_profile.yaml [4]: https://libvirt.org/formatdomain.html#elementsCharPTY --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: ppc64el DistroRelease: Ubuntu 16.04 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: lxd PackageArchitecture: ppc64el ProcKernelCmdline: root=UUID=902eaad1-2164-4f9a-bec4-7ff3abc15804 ro console=hvc0 ProcLoadAvg: 3.15 3.02 3.83 1/3056 79993 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-72-generic (buildd@bos01-ppc64el-022) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Syslog: Tags: xenial uec-images Uname: Linux 4.4.0-72-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: utah _MarkForUpload: True cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT is off --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: ppc64el DistroRelease: Ubuntu 16.04 NonfreeKernelModules: cfg80211 ebtable_broute ebtable_nat binfmt_misc veth nbd openvswitch vhost_net vhost macvtap macvlan xt_conntrack ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables zfs zunicode zcommon znvpair spl zavl kvm_hv kvm ipmi_powernv ipmi_msghandler uio_pdrv_genirq vmx_crypto powernv_rng ibmpowernv leds_powernv uio ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx4_en vxlan ip6_udp_tunnel udp_tunnel mlx4_core ipr Package: lxd PackageArchitecture: ppc64el ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdline: root=UUID=902eaad1-2164-4f9a-bec4-7ff3abc15804 ro console=hvc0
[Kernel-packages] [Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
** Package changed: linux-5.4 (Ubuntu Focal) => linux (Ubuntu Focal) ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] After Ubuntu-5.4.0-9.12 which introduce DPCD backlight patches, the backlight control on some platforms fail to work. It seems using OUI string to map the panels which support DPCD backlight doesn't work well, it mis-mapped those panel that doesn't support DPCD backlight, and breaks the backlight control. [Fix] The author of the origin DPCD backlight patches recently provides a DP quirks based on EDID identification. [Fix] Verified on the machine with DPCD backlight and also on the machine which has regression with the OUI quirks, both of them work now. [Regression Potential] Low, it introduce a new quirks to list the panels which support DPCD backlight. === After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no longer have the ability to control the backlight brightness on my HP EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen indicator pops up and shows that the brightness setting is being changed but the actual screen brightness is stuck on the lowest setting. This laptop has a built-in privacy screen. If I activate the privacy screen (fn-f2), then the actual screen brightness goes to the maximum setting and then I am able to dim and brighten the backlight as long as the privacy screen functionality is turned on. This is a regression from Eoan's 5.3.0-29.31 kernel where I was able to control the brightness with and without the privacy screen functionality being turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 11:42:16 2020 InstallationDate: Installed on 2019-06-24 (221 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861521/+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 1868898] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341563/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341560/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341562/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341559/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341566/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341569/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341561/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341565/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341567/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341564/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] Re: Ubuntu 20.04 clean install : autostandby feature
apport information ** Tags added: apport-collected staging ** Description changed: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. - Problem seems to be in auto standby feature. I remember this bug in - 18.04 development branch as well. + Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: steve 1606 F pulseaudio + /dev/snd/controlC0: steve 1606 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-03-21 (4 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) + MachineType: Dell Inc. Inspiron 5765 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-18-generic N/A + linux-backports-modules-5.4.0-18-generic N/A + linux-firmware1.187 + StagingDrivers: exfat + Tags: focal staging + Uname: Linux 5.4.0-18-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/17/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.1.1 + dmi.board.name: 0DM01M + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 1.1.1 + dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5765 + dmi.product.sku: 076A + dmi.product.version: 1.1.1 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341558/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1868898] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341568/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] Re: Ubuntu 20.04 clean install : autostandby feature
** Package changed: ubuntu => linux (Ubuntu) -- 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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Hi @dersuuzalachillout, You can just open a terminal window and run inside (line by line, in sequence): wget http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.173.17_all.deb sudo dpkg -i linux-firmware_1.173.17_all.deb rm linux-firmware_1.173.17_all.deb Type your password (when 'sudo' ask you) and when everything gets done reboot your computer. Is there any change? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen
[Kernel-packages] [Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic
The issue with the brightness slider not moving in the gnome panel menu, in response to brightness keys, was fixed after the latest round of updates that installed gnome-shell 3.36. So all is good now on the Dell XPS 9575, thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858844 Title: [Dell XPS 15 9575] Screen brightness stopped working with linux- image-5.4.0-9-generic Status in linux package in Ubuntu: Confirmed Bug description: I upgraded to Focal Fossa 3 days ago and nothing broke. At the time, it was still using linux 5.3 (linux-image-5.3.0-24-generic). Today, it updated to linux 5.4 (linux-image-5.4.0-9-generic) and after rebooting, the screen brightness does not work anymore - neither from keyboard keys nor from the slider in the gnome-shell panel. It works again when rebooting into the previous linux- image-5.3.0-24-generic kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 1892 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 20:23:31 2020 InstallationDate: Installed on 2018-09-13 (481 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-04 (3 days ago) dmi.bios.date: 07/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858844/+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 1814481] Re: Keychron K1 keyboard not working
Keychron K1v3 (firmware V3.7) on Ubuntu 19.10 (upgrad path from 18.04), can confirm that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/comments/19 fixes the issue when connected via Bluetooth. Some additional information: For me when connected via Bluetooth only the function keys would work. The following command as described by Eferox, allowed me to use the keyboard normally: echo 0 | sudo tee /sys/module/hid_apple/parameters/fnmode Note that this means that the `fn` key is now disabled by default, so pressing one of the `F` keys registers as `F1`, `F2`, etc. In order to get the media key functions you have to press `fn` + `F`. Also note that if you also use an Apple keyboard this probably modifies its default behaviour. Explanation of parameters for `/sys/module/hid_apple/parameters/fnmode` https://superuser.com/questions/79822/how-to-swap-the-fn-use-of-function-keys-on-an-apple-keyboard-in-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: Keychron K1 keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: I recently got a nice mechanical bluetooth keyboard to use on my thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only works after calling `sudo evtest /dev/input/eventN`. Xorg.0.log shows it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine:
[Kernel-packages] [Bug 1814481] Re: Keychron K1 keyboard not working
Additionally if you want to change the default `F` key behaviour again, press and hold `fn + X + L` in that order for >3 seconds until the keyboard blinks red twice. -- 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/1814481 Title: Keychron K1 keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: I recently got a nice mechanical bluetooth keyboard to use on my thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only works after calling `sudo evtest /dev/input/eventN`. Xorg.0.log shows it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW 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:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW
Re: [Kernel-packages] [Bug 1868898] Re: Ubuntu 20.04 clean install : autostandby feature
Hi, I am currently leaving my laptop on on idle to replicate the issue then I will run apport collect to the bug. not sure how to change the bug status. -Steve On 2020-03-25 8:25 a.m., Juhani Numminen wrote: > ** Package changed: ubuntu => linux (Ubuntu) > -- 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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1869033] [NEW] Lenovo IdeaPad S145-IWL - touchpad not recognized
Public bug reported: I'm trying to use Ubuntu 20.04 but it's not seeing touchpad - it's not even available in device list. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4248 F pulseaudio CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:44:31 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN21WW 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: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN21WW:bd10/09/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL 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/1869033 Title: Lenovo IdeaPad S145-IWL - touchpad not recognized Status in linux package in Ubuntu: New Bug description: I'm trying to use Ubuntu 20.04 but it's not seeing touchpad - it's not even available in device list. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4248 F pulseaudio CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:44:31 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN21WW 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: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN21WW:bd10/09/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869033/+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 1869032] Re: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8
This is what I saw on this Eoan P8 node modoc on the last cycle: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867155 Which makes it failed to finish the test. -- 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/1869032 Title: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Issue found on P8 node modoc with Eoan (5.3.0-43.36) (Note that this test has passed with P9 node baltar without any traces in syslog) The ubuntu_kernel_selftests hangs: 15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack 15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # Opening 127.0.0.1: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening in6addr_any: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # selftests: net: tls 15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected status (4) == 0 (0) 15:17:26 DEBUG| [stdout] # Alarm clock 15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351 (And test continues) It looks like it's the selftests: net: tls that's causing this issue. If you ssh to the node, the following trace could be found in dmesg: Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Oops: Exception in kernel mode, sig: 4 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: notifier_error_inject] CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu NIP: c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270 REGS: c00fc97837a0 TRAP: 0e40 Not tainted (5.3.0-43-generic) MSR: 9288b033 CR: 28002862 XER: 2000 CFAR: c000dfc4 IRQMASK: 0 GPR00: c0080a4d6a40 c00fc9783a30 c19d9000 GPR04: c00f5afc c00fc97839b8 GPR08: c00f5afc c00ff9a13780 GPR12: 88002462 c00eb380 GPR16: 0ac875961368 0ac875960d38 0ac875960d90 GPR20: 7c6b4ef0 c00e3996dc48 GPR24: c04a9d70 ea60 GPR28: c00c0398c740 cab32e70 c00f7ecebd00 NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] Call Trace: [c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] (unreliable) [c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140 [c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70 [c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50 [c00fc9783b10] [c04a9e8c] pipe_to_sendpage+0x7c/0xf0 [c00fc9783b40] [c04ab3d4] __splice_from_pipe+0x164/0x280 [c00fc9783ba0] [c04ad994] splice_from_pipe+0x74/0xc0 [c00fc9783c20] [c04a9dbc] direct_splice_actor+0x4c/0xa0 [c00fc9783c40] [c04aad14] splice_direct_to_actor+0x2a4/0x3c0 [c00fc9783cc0] [c04aaee4] do_splice_direct+0xb4/0x130 [c00fc9783d30] [c04565c4] do_sendfile+0x234/0x4a0 [c00fc9783dd0] [c0456b70] sys_sendfile64+0x160/0x170 [c00fc9783e20] [c000b388] system_call+0x5c/0x70 Instruction dump: <> ---[ end trace 8961ea39a6f2dd08 ]--- BUG: Kernel NULL pointer dereference at 0x Faulting instruction address: 0xc020bd74 Oops: Kernel access of bad area, sig: 11 [#2] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls
[Kernel-packages] [Bug 1869032] Re: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8
A quick search with keywork "tls" in Eoan tree brought me this:
commit 299dfeeb7a216fe4dcfdd6ad0461ea93db72d389
Author: Jakub Kicinski
Date: Fri Jan 10 04:38:32 2020 -0800
net/tls: fix async operation
BugLink: https://bugs.launchpad.net/bugs/1864710
commit db885e66d268884dc72967279b7e84f522556abc upstream.
Mallesham reports the TLS with async accelerator was broken by
commit d10523d0b3d7 ("net/tls: free the record on encryption error")
because encryption can return -EINPROGRESS in such setups, which
should not be treated as an error.
The error is also present in the BPF path (likely copied from there).
Reported-by: Mallesham Jatharakonda
Fixes: d3b18ad31f93 ("tls: add bpf support to sk_msg handling")
Fixes: d10523d0b3d7 ("net/tls: free the record on encryption error")
Signed-off-by: Jakub Kicinski
Reviewed-by: Simon Horman
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Kamal Mostafa
Signed-off-by: Khalid Elmously
$ git tag --contains 299dfeeb7a216fe4dcfdd6ad0461ea93db72d389
Ubuntu-5.3.0-43.35
Ubuntu-5.3.0-43.36
Need to check if this is the cause.
--
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/1869032
Title:
Kernel oopsed and null pointer dereference while running
ubuntu_kernel_selftests on Eoan Power8
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
Issue found on P8 node modoc with Eoan (5.3.0-43.36)
(Note that this test has passed with P9 node baltar without any traces in
syslog)
The ubuntu_kernel_selftests hangs:
15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack
15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict
15:16:53 DEBUG| [stdout] # Opening 127.0.0.1:
15:16:53 DEBUG| [stdout] # Opening INADDR_ANY:
15:16:53 DEBUG| [stdout] # bind: Address already in use
15:16:53 DEBUG| [stdout] # Opening in6addr_any:
15:16:53 DEBUG| [stdout] # Opening INADDR_ANY:
15:16:53 DEBUG| [stdout] # bind: Address already in use
15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket
15:16:53 DEBUG| [stdout] # bind: Address already in use
15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict
15:16:53 DEBUG| [stdout] # selftests: net: tls
15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected
status (4) == 0 (0)
15:17:26 DEBUG| [stdout] # Alarm clock
15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351
(And test continues)
It looks like it's the selftests: net: tls that's causing this issue.
If you ssh to the node, the following trace could be found in dmesg:
Injecting error (-12) to MEM_GOING_OFFLINE
Injecting error (-12) to MEM_GOING_OFFLINE
Injecting error (-12) to MEM_GOING_OFFLINE
Oops: Exception in kernel mode, sig: 4 [#1]
LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc
scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio
powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel
ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum
tg3 ipr [last unloaded: notifier_error_inject]
CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu
NIP: c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270
REGS: c00fc97837a0 TRAP: 0e40 Not tainted (5.3.0-43-generic)
MSR: 9288b033 CR: 28002862
XER: 2000
CFAR: c000dfc4 IRQMASK: 0
GPR00: c0080a4d6a40 c00fc9783a30 c19d9000
GPR04: c00f5afc c00fc97839b8
GPR08: c00f5afc c00ff9a13780
GPR12: 88002462 c00eb380
GPR16: 0ac875961368 0ac875960d38 0ac875960d90
GPR20: 7c6b4ef0 c00e3996dc48
GPR24: c04a9d70 ea60
GPR28: c00c0398c740 cab32e70 c00f7ecebd00
NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls]
LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls]
Call Trace:
[c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls]
(unreliable)
[c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140
[c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70
[c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50
[c00fc9783b10] [c04a9e8c]
[Kernel-packages] [Bug 1869032] 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/1869032 Title: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Issue found on P8 node modoc with Eoan (5.3.0-43.36) (Note that this test has passed with P9 node baltar without any traces in syslog) The ubuntu_kernel_selftests hangs: 15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack 15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # Opening 127.0.0.1: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening in6addr_any: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # selftests: net: tls 15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected status (4) == 0 (0) 15:17:26 DEBUG| [stdout] # Alarm clock 15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351 (And test continues) It looks like it's the selftests: net: tls that's causing this issue. If you ssh to the node, the following trace could be found in dmesg: Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Oops: Exception in kernel mode, sig: 4 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: notifier_error_inject] CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu NIP: c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270 REGS: c00fc97837a0 TRAP: 0e40 Not tainted (5.3.0-43-generic) MSR: 9288b033 CR: 28002862 XER: 2000 CFAR: c000dfc4 IRQMASK: 0 GPR00: c0080a4d6a40 c00fc9783a30 c19d9000 GPR04: c00f5afc c00fc97839b8 GPR08: c00f5afc c00ff9a13780 GPR12: 88002462 c00eb380 GPR16: 0ac875961368 0ac875960d38 0ac875960d90 GPR20: 7c6b4ef0 c00e3996dc48 GPR24: c04a9d70 ea60 GPR28: c00c0398c740 cab32e70 c00f7ecebd00 NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] Call Trace: [c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] (unreliable) [c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140 [c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70 [c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50 [c00fc9783b10] [c04a9e8c] pipe_to_sendpage+0x7c/0xf0 [c00fc9783b40] [c04ab3d4] __splice_from_pipe+0x164/0x280 [c00fc9783ba0] [c04ad994] splice_from_pipe+0x74/0xc0 [c00fc9783c20] [c04a9dbc] direct_splice_actor+0x4c/0xa0 [c00fc9783c40] [c04aad14] splice_direct_to_actor+0x2a4/0x3c0 [c00fc9783cc0] [c04aaee4] do_splice_direct+0xb4/0x130 [c00fc9783d30] [c04565c4] do_sendfile+0x234/0x4a0 [c00fc9783dd0] [c0456b70] sys_sendfile64+0x160/0x170 [c00fc9783e20] [c000b388] system_call+0x5c/0x70 Instruction dump: <> ---[ end trace 8961ea39a6f2dd08 ]--- BUG: Kernel NULL pointer dereference at 0x Faulting instruction address: 0xc020bd74 Oops: Kernel access of bad area, sig: 11 [#2] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv
[Kernel-packages] [Bug 1868898] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341591/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341585/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341588/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Jean, You mentioned Bluetooth audio, that remind me that the testing alsa-lib in the #66 has some problem, I just fixed it and uploaded a new version to it, please try it. And testing alsa-lib is not SRUed yet, I plan to SRU it with this bug: #1868210. And Because the pulseaudio+ucm works greatly different from pulseaudio+non-ucm, most pulseaudio+ucm machines are headless embedded systems, it can't work as well as pulseauido+non-ucm on desktop system. To support the internal mic, Intel provided this ucm. If you prefer pulseaudio+non-ucm, you could add "options snd-hda-intel dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf. With the ucm, the internal mic and headset-mic belong to different sources, and all output devices and input devices separate to different profiles, that makes the auto-selection/switch among audio devices nearly not work. And if you manually select an output device which is not in the current profile, and two or more input devices are in the new profile, you will see input device is changed when you select output device. This is a pulseaudio bug maybe, if pulseaudio has fix, I will backport it. About the issue on google meet, it is a problem, do you also meet the similar issue on other audio apps? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1867109] Re: [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up
--- Comment From pa...@de.ibm.com 2020-03-25 10:35 EDT--- Verificattion: looks good! ** Tags removed: verification-needed-focal ** Tags added: verification-done-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/1867109 Title: [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: virtio-blk disks can go dissfunctional when swiotlb fills up virtio-blk hw queue gets possibly permanently stopped when swiotlb full For example, with a PV guest choose a small swiotlb (30MB) and create IO load on several virtio-blk disks simultaneously. It actually should not matter what causes the swiotlb pressure (can be virtio-net as well). Fixes posted upstream: https://lkml.org/lkml/2020/2/13/306 We will need backports to support Protected Virtualization. IBM verified that the patches apply cleanly on focal/master-next, upstream commit ids for reference: commit bab7e6f05699a481787f7659c4f766dd87187dae Author: Halil Pasic Date: Thu Feb 13 13:37:27 2020 +0100 virtio-blk: fix hw_queue stopped on arbitrary error commit 24506976aec92052e9fe328146a2e574a1190986 Author: Halil Pasic Date: Thu Feb 13 13:37:28 2020 +0100 virtio-blk: improve virtqueue error to BLK_STS Also applies cleanly on 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1867109/+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 1866882] Re: segfault in libllvm-10 when building kernel bpf selftests on s390
Still seeing this with the current focal-proposed kernel: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/l/linux/20200325_012616_7d5a5@/log.gz ** Changed in: llvm-toolchain-10 (Ubuntu) Status: Incomplete => Confirmed ** Changed in: llvm-toolchain-10 (Ubuntu) Assignee: (unassigned) => Matthias Klose (doko) ** Changed in: llvm-toolchain-10 (Ubuntu) Importance: Undecided => High -- 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/1866882 Title: segfault in libllvm-10 when building kernel bpf selftests on s390 Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-10 package in Ubuntu: Confirmed Bug description: Seeing this in autopkgtest for the 5.4.0-18 kernel. Only happens on s390, other architectures are fine. Stack dump: 0. Program arguments: llc -march=bpf -mcpu=probe -filetype=obj -o /tmp/autopkgtest.92AlD3/build.vya/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/btf__core_reloc_nesting___err_array_container.o #0 0x03ff830ab14a (/lib/s390x-linux-gnu/libLLVM-10.so.1+0x9ab14a) Segmentation fault (core dumped) Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/l/linux/20200310_180956_146bd@/log.gz This did not happen for the 5.4.0-17 upload with llvm-9, with no changes to the bpf program being compiled when the segfault happens between the -17 and -18 uploads. To reproduce, clone the focal kernel tree and build the bpf selftests. $ git clone --single-branch --depth=1 -b master-next git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal $ make -C focal/tools/testing/selftests TARGETS=bpf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866882/+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 1868898] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341590/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1868898] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341589/+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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-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/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
It'll be in Eoan kernel when it's "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/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Triaged Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [ 911.413625] Restarting tasks ... done. [ 911.462021] PM: suspend exit It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865570/+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 1855399] Re: [TGL] graphics kernel support
Thanks! There are a few that are missing from my patchset, I'll add them in the next batch. -- 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/1855399 Title: [TGL] graphics kernel support Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: This feature tracks the updates TGL graphics updates. We will submit the commit id lists since 5.4. 20.04 will use v5.4 as a base, (2109/11/25) first commit lists will be provided in 2020/01, if you need more before that, please let us know. Target Release: 20.10 Target Kernel: v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855399/+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 1868388] Re: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]
Could you please send /var/log/kern.log* ? 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/1868388 Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] Status in linux package in Ubuntu: Confirmed Bug description: Got this after resuming from suspend for a few hours. Also noticed that it was not possible to re-establish wifi connectivity. Had to reboot the machine to get back to a proper working state. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1443 F pulseaudio marcus 1889 F pulseaudio Date: Sat Mar 21 11:43:52 2020 Failure: oops InstallationDate: Installed on 2020-03-18 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8c0be221-e900-480f-b359-5cbd3f16ebd4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868388/+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 1868388] Re: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]
Unfortunately no, the install has been removed for now as it was just a quick test spin of 20.04 on real hardware. -- 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/1868388 Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] Status in linux package in Ubuntu: Confirmed Bug description: Got this after resuming from suspend for a few hours. Also noticed that it was not possible to re-establish wifi connectivity. Had to reboot the machine to get back to a proper working state. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1443 F pulseaudio marcus 1889 F pulseaudio Date: Sat Mar 21 11:43:52 2020 Failure: oops InstallationDate: Installed on 2020-03-18 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8c0be221-e900-480f-b359-5cbd3f16ebd4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868388/+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 1868898] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1868898 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+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 1869033] 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/1869033 Title: Lenovo IdeaPad S145-IWL - touchpad not recognized Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to use Ubuntu 20.04 but it's not seeing touchpad - it's not even available in device list. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4248 F pulseaudio CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:44:31 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN21WW 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: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN21WW:bd10/09/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869033/+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 1869032] [NEW] Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8
Public bug reported: Issue found on P8 node modoc with Eoan (5.3.0-43.36) (Note that this test has passed with P9 node baltar without any traces in syslog) The ubuntu_kernel_selftests hangs: 15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack 15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # Opening 127.0.0.1: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening in6addr_any: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # selftests: net: tls 15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected status (4) == 0 (0) 15:17:26 DEBUG| [stdout] # Alarm clock 15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351 (And test continues) It looks like it's the selftests: net: tls that's causing this issue. If you ssh to the node, the following trace could be found in dmesg: Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Oops: Exception in kernel mode, sig: 4 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: notifier_error_inject] CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu NIP: c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270 REGS: c00fc97837a0 TRAP: 0e40 Not tainted (5.3.0-43-generic) MSR: 9288b033 CR: 28002862 XER: 2000 CFAR: c000dfc4 IRQMASK: 0 GPR00: c0080a4d6a40 c00fc9783a30 c19d9000 GPR04: c00f5afc c00fc97839b8 GPR08: c00f5afc c00ff9a13780 GPR12: 88002462 c00eb380 GPR16: 0ac875961368 0ac875960d38 0ac875960d90 GPR20: 7c6b4ef0 c00e3996dc48 GPR24: c04a9d70 ea60 GPR28: c00c0398c740 cab32e70 c00f7ecebd00 NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] Call Trace: [c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] (unreliable) [c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140 [c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70 [c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50 [c00fc9783b10] [c04a9e8c] pipe_to_sendpage+0x7c/0xf0 [c00fc9783b40] [c04ab3d4] __splice_from_pipe+0x164/0x280 [c00fc9783ba0] [c04ad994] splice_from_pipe+0x74/0xc0 [c00fc9783c20] [c04a9dbc] direct_splice_actor+0x4c/0xa0 [c00fc9783c40] [c04aad14] splice_direct_to_actor+0x2a4/0x3c0 [c00fc9783cc0] [c04aaee4] do_splice_direct+0xb4/0x130 [c00fc9783d30] [c04565c4] do_sendfile+0x234/0x4a0 [c00fc9783dd0] [c0456b70] sys_sendfile64+0x160/0x170 [c00fc9783e20] [c000b388] system_call+0x5c/0x70 Instruction dump: <> ---[ end trace 8961ea39a6f2dd08 ]--- BUG: Kernel NULL pointer dereference at 0x Faulting instruction address: 0xc020bd74 Oops: Kernel access of bad area, sig: 11 [#2] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: notifier_error_inject] CPU: 10 PID: 38095 Comm: modprobe Tainted: G D 5.3.0-43-generic #36-Ubuntu NIP: c020bd74 LR: c07a24f4 CTR: c020bd40
[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
Please ignore #1 and #2. Some users found some problem on them (find the ucm by bios version). I will upload new debdiffs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in HWE Next: New Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Eoan: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: This SRU is not backported from upstream of alsa-lib and this SRU is not going to be submitted to upstream. That is because the latest alsa-lib already supports ucm2, and with ucm2 all machines could share one ucm, so latest alsa-lib does not have this problem. This problem is only specific to the alsa-lib in Bionic and Eoan. [Impact] On some Lenovo notebooks, UCM files are not loaded and mic can't be used. [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] After applying this patch, install the testing alsa-lib on Lenovo X1C7 and Dell vostro 5390, which are all machines with the DMIC connected to PCH. After system bootup, check the /usr/share/alsa/ucm/ for the presence of LENOVO-BIOSID-xxx directories. Lenovo X1C7 should load the N2H/*.conf and verify the audio functionalities. The Dell machine should still load the ucm by cardname, and it should work as good as before. [Regression Potential] low, just add some new UCMs and let Lenovo machine find the UCM by bios_version if it fails by cardlongname. I've already tested the change on Lenovo and Dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1868918] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1868918 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1868918 Title: [ICX] Turbostat update for ICX Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: During turbostat test with Ubuntu 19.10(kernel 5.3), we found some columns are missing on ICX. Checked turbostat code in latest kernel(5.5-rc1), seems update needed to add ICX support: #define INTEL_FAM6_ICELAKE_X 0x6A Commit ids: 23274faf96500700da83c4f0ff12d78ae03d5604 Target Release: 20.04 Target Kernel: 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1868918/+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 1868693] Re: Incorrect advertise flags in bluetooth beacon using BlueZ
OK. I can't tell yet but in case this bug is caused by your Bluetooth driver I'll also include the kernel here. ** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1868693 Title: Incorrect advertise flags in bluetooth beacon using BlueZ Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried the following on bluex version 5.48 and 5.52. I have set ControllerMode to "le" in main.conf. Using bluetootctl, when i turn on the advertisement using command "advertise on" , I get 0x02 advertisement flag. which means "BR/EDR Not Supported" (Bit 2) is not set. Now , if i restart the bluetooth service, and turn on the advertisement again, I get 0x06 advertisement flags. Here is my main.conf [General]# Default adaper name # Defaults to 'BlueZ X.YZ' #Name = BlueZ# Default device class. Only the major and minor device class bits are # considered. Defaults to '0x00'. Class = 0x000100# How long to stay in discoverable mode before going back to non-discoverable # The value is in seconds. Default is 180, i.e. 3 minutes. # 0 = disable timer, i.e. stay discoverable forever DiscoverableTimeout = 0# How long to stay in pairable mode before going back to non-discoverable # The value is in seconds. Default is 0. # 0 = disable timer, i.e. stay pairable forever #PairableTimeout = 0# Automatic connection for bonded devices driven by platform/user events. # If a platform plugin uses this mechanism, automatic connections will be # enabled during the interval defined below. Initially, this feature # intends to be used to establish connections to ATT channels. Default is 60. #AutoConnectTimeout = 60# Use vendor id source (assigner), vendor, product and version information for # DID profile support. The values are separated by ":" and assigner, VID, PID # and version. # Possible vendor id source values: bluetooth, usb (defaults to usb) #DeviceID = bluetooth:1234:5678:abcd# Do reverse service discovery for previously unknown devices that connect to # us. This option is really only needed for qualification since the BITE tester # doesn't like us doing reverse SDP for some test cases (though there could in # theory be other useful purposes for this too). Defaults to 'true'. #ReverseServiceDiscovery = true# Enable name resolving after inquiry. Set it to 'false' if you don't need # remote devices name and want shorter discovery cycle. Defaults to 'true'. #NameResolving = true# Enable runtime persistency of debug link keys. Default is false which # makes debug link keys valid only for the duration of the connection # that they were created for. #DebugKeys = false# Restricts all controllers to the specified transport. Default value # is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW). # Possible values: "dual", "bredr", "le" ControllerMode = le# Enables Multi Profile Specification support. This allows to specify if # system supports only Multiple Profiles Single Device (MPSD) configuration # or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple # Devices (MPMD) configurations. # Possible values: "off", "single", "multiple" #MultiProfile = off# Permanently enables the Fast Connectable setting for adapters that # support it. When enabled other devices can connect faster to us, # however the tradeoff is increased power consumptions. This feature # will fully work only on kernel version 4.1 and newer. Defaults to # 'false'. #FastConnectable = false[Policy]# The ReconnectUUIDs defines the set of remote services that should try # to be reconnected to in case of a link loss (link supervision # timeout). The policy plugin should contain a sane set of values by # default, but this list can be overridden here. By setting the list to # empty the reconnection feature gets disabled. #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb# ReconnectAttempts define the number of attempts to reconnect after a link # lost. Setting the value to 0 disables reconnecting feature. #ReconnectAttempts=7# ReconnectIntervals define the set of intervals in seconds to use in between # attempts. # If the number of attempts defined in ReconnectAttempts is bigger than the # set of intervals the last interval is repeated until the last attempt. #ReconnectIntervals=1, 2, 4, 8, 16, 32, 64# AutoEnable defines option to enable all controllers when they are found. # This includes adapters present on start as well as adapters that are plugged # in later on. Defaults to 'false'. AutoEnable=true And
[Kernel-packages] [Bug 1813136] Re: dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests failed with Power9 on B/C/D
On Bionic P9, this issue still exist on P9. On Eoan P9, it's now: not ok 6 selftests: dscr: dscr_sysfs_test # TIMEOUT ** Tags added: sru-20200316 ** No longer affects: linux (Ubuntu Eoan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813136 Title: dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests failed with Power9 on B/C/D Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue can be found on Power9 with Bionic / Cosmic kernel $ sudo ./dscr_sysfs_test test: dscr_sysfs_test tags: git_version:c186097-dirty !! killing dscr_sysfs_test !! child died by signal 15 failure: dscr_sysfs_test Passed on Power8 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 24 07:22 seq crw-rw 1 root audio 116, 33 Jan 24 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 24 09:29:00 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.26 0.07 0.11 3/1363 35034 ProcLocks: 1: FLOCK ADVISORY WRITE 3482 00:17:520 0 EOF 2: POSIX ADVISORY WRITE 3746 00:17:580 0 EOF 3: POSIX ADVISORY WRITE 1800 00:17:368 0 EOF 4: FLOCK ADVISORY WRITE 3744 00:17:568 0 EOF 5: POSIX ADVISORY WRITE 3831 00:17:588 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-44-generic (buildd@bos02-ppc64el-004) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #47-Ubuntu SMP Mon Jan 14 11:26:40 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 5 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.862 GHz (cpu 3) avg: 2.862 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813136/+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 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
@mapengyu, I've rebuilt e1000e.ko with your patch applied to 5.6.0-rc5 tree, and suspend works normally for me: Linux journex 5.6.0-rc5+ #2 SMP Sun Mar 15 00:09:19 CET 2020 x86_64 x86_64 x86_64 GNU/Linux First suspend: [ 66.578525] PM: suspend entry (s2idle) [ 66.582870] Filesystems sync: 0.004 seconds [ 66.583640] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 66.585841] OOM killer disabled. [ 66.585842] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 66.587085] printk: Suspending console(s) (use no_console_suspend to debug) [ 66.587375] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 66.691969] e1000e: EEE TX LPI TIMER: 0011 [ 69.395364] ACPI: EC: interrupt blocked [ 79.252679] ACPI: EC: interrupt unblocked [ 82.053040] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 82.169363] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 82.234288] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 85.251055] OOM killer enabled. [ 85.251056] Restarting tasks ... done. [ 85.260141] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 85.293929] PM: suspend exit [ 85.391753] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 85.627128] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM ... Second suspend: [ 140.523471] PM: suspend entry (s2idle) [ 140.554018] Filesystems sync: 0.030 seconds [ 140.554655] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 140.556773] OOM killer disabled. [ 140.556773] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 140.558014] printk: Suspending console(s) (use no_console_suspend to debug) [ 140.558275] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 140.659976] e1000e: EEE TX LPI TIMER: 0011 [ 143.380606] ACPI: EC: interrupt blocked [ 158.716081] ACPI: EC: interrupt unblocked [ 161.516454] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 161.866014] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 161.933414] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 164.586442] OOM killer enabled. [ 164.586443] Restarting tasks ... [ 164.592488] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 164.592743] done. [ 164.637623] PM: suspend exit [ 164.735062] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 164.999601] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM ... -- 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/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Triaged Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug
[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
** Attachment added: "dmesg.5.6.0-050600rc5-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868936/+attachment/5341350/+files/dmesg.5.6.0-050600rc5-generic ** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #1296 https://gitlab.freedesktop.org/drm/intel/issues/1296 -- 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/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in linux package in Ubuntu: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868936/+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 1868626] Re: Allow BPF tracing under lockdown
** 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/1868626
Title:
Allow BPF tracing under lockdown
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Bug description:
[Impact]
BPF tracing is allowed on Bionic and on Focal under integrity lockdown, which
is going to be the default before release. Right now, Eoan does not allow
kprobes and BPF reads under lockdown, preventing BPF tracing and kprobe tracing.
[Test case]
sudo bpftrace -e 'kprobe:do_nanosleep { printf("PID %d sleeping...\n", pid);
}'
sudo bpftrace -e 'tracepoint:syscalls:sys_enter_openat { printf("filename:
[%s]; flags: [%d]\n", str(args->filename), args->flags); }'
The last one should show the filename and flags.
[Regression potential]
This would allow privileged users to possibly read some kernel data that was
not possible before. However, this is already possible on systems that are not
under lockdown, which are all non-secure boot systems by default. This also
matches the behavior of signed kernels of Bionic and Focal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868626/+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 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
I've just tested on Eoan with the proposed branch. It didn't resolve my issue. I'll give it some time today to see if the new kernel gets released. This is the kernel I'm running after an apt update/upgrade cycle this morning Linux MiX 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Triaged Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [ 911.413625] Restarting tasks ... done. [ 911.462021] PM: suspend exit It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865570/+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 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
Using the kernel package from -proposed makes suspend work normally as well. Linux journex 5.4.0-20-generic #24-Ubuntu SMP Mon Mar 23 20:55:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Though I guess that 5.4.0-20 uses the "workaround", and it may be better to apply the "proper fix" from comment 21? In any case, I am marking it "verification-done" because it does indeed work. ** Tags removed: verification-needed-focal ** Tags added: verification-done-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/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Triaged Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [ 911.413625] Restarting tasks ... done. [ 911.462021] PM: suspend exit It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865570/+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 1868936] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1868936 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+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 1835531] Re: [20.04 FEAT] Base KVM setup for secure guests - kernel part
--- Comment From cborn...@de.ibm.com 2020-03-25 04:28 EDT--- further testing looks good. ** Tags removed: verification-needed-focal ** Tags added: verification-done-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/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+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 1868936] [NEW] [ICL] TC port in legacy/static mode can't be detected due TCCOLD
Public bug reported: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Tags added: apport-collected bionic ** Description changed: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.12 + Architecture: amd64 + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-03-18 (7 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: bionic + Uname: Linux 5.6.0-050600rc5-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True -- 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/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in linux package in Ubuntu: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868936/+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 1868936] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341349/+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/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in linux package in Ubuntu: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868936/+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 1868693] 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1868693 Title: Incorrect advertise flags in bluetooth beacon using BlueZ Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I tried the following on bluex version 5.48 and 5.52. I have set ControllerMode to "le" in main.conf. Using bluetootctl, when i turn on the advertisement using command "advertise on" , I get 0x02 advertisement flag. which means "BR/EDR Not Supported" (Bit 2) is not set. Now , if i restart the bluetooth service, and turn on the advertisement again, I get 0x06 advertisement flags. Here is my main.conf [General]# Default adaper name # Defaults to 'BlueZ X.YZ' #Name = BlueZ# Default device class. Only the major and minor device class bits are # considered. Defaults to '0x00'. Class = 0x000100# How long to stay in discoverable mode before going back to non-discoverable # The value is in seconds. Default is 180, i.e. 3 minutes. # 0 = disable timer, i.e. stay discoverable forever DiscoverableTimeout = 0# How long to stay in pairable mode before going back to non-discoverable # The value is in seconds. Default is 0. # 0 = disable timer, i.e. stay pairable forever #PairableTimeout = 0# Automatic connection for bonded devices driven by platform/user events. # If a platform plugin uses this mechanism, automatic connections will be # enabled during the interval defined below. Initially, this feature # intends to be used to establish connections to ATT channels. Default is 60. #AutoConnectTimeout = 60# Use vendor id source (assigner), vendor, product and version information for # DID profile support. The values are separated by ":" and assigner, VID, PID # and version. # Possible vendor id source values: bluetooth, usb (defaults to usb) #DeviceID = bluetooth:1234:5678:abcd# Do reverse service discovery for previously unknown devices that connect to # us. This option is really only needed for qualification since the BITE tester # doesn't like us doing reverse SDP for some test cases (though there could in # theory be other useful purposes for this too). Defaults to 'true'. #ReverseServiceDiscovery = true# Enable name resolving after inquiry. Set it to 'false' if you don't need # remote devices name and want shorter discovery cycle. Defaults to 'true'. #NameResolving = true# Enable runtime persistency of debug link keys. Default is false which # makes debug link keys valid only for the duration of the connection # that they were created for. #DebugKeys = false# Restricts all controllers to the specified transport. Default value # is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW). # Possible values: "dual", "bredr", "le" ControllerMode = le# Enables Multi Profile Specification support. This allows to specify if # system supports only Multiple Profiles Single Device (MPSD) configuration # or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple # Devices (MPMD) configurations. # Possible values: "off", "single", "multiple" #MultiProfile = off# Permanently enables the Fast Connectable setting for adapters that # support it. When enabled other devices can connect faster to us, # however the tradeoff is increased power consumptions. This feature # will fully work only on kernel version 4.1 and newer. Defaults to # 'false'. #FastConnectable = false[Policy]# The ReconnectUUIDs defines the set of remote services that should try # to be reconnected to in case of a link loss (link supervision # timeout). The policy plugin should contain a sane set of values by # default, but this list can be overridden here. By setting the list to # empty the reconnection feature gets disabled. #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb# ReconnectAttempts define the number of attempts to reconnect after a link # lost. Setting the value to 0 disables reconnecting feature. #ReconnectAttempts=7# ReconnectIntervals define the set of intervals in seconds to use in between # attempts. # If the number of attempts defined in ReconnectAttempts is bigger than the # set of intervals the last interval is repeated until the last attempt. #ReconnectIntervals=1, 2, 4, 8, 16, 32, 64# AutoEnable defines option to enable all controllers when they are found. # This includes adapters present on start as well as adapters that are plugged # in later on. Defaults to 'false'. AutoEnable=true And bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth[Service] Type=dbus
