[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
With the current setup, I didn't manage to reproduce the problem yet today. Here's the debug log that you asked that includes booting with the thunderbolt connected, then disconnecting and reconnecting - all completing successfully. ** Attachment added: "okconnect.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856161/+attachment/5317699/+files/okconnect.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor:
[Kernel-packages] [Bug 1858089] Re: Touchpad stopped working
I booted with the previous version of the kernel (see image) but it still doesn't work ** Attachment added: "kernel options in grub menu (ubuntu advanced options)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858089/+attachment/5317708/+files/WhatsApp%20Image%202020-01-05%20at%2012.27.08.jpeg -- 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/1858089 Title: Touchpad stopped working Status in linux package in Ubuntu: Confirmed Bug description: Suddenly my touchpad stopped working, previously it did but now it doesn't appear on /proc/bus/input/devices. Before this my laptop used to enter in airplane mode when coming back from suspension and I couldn't get it out from airplane mode unless I rebooted it because the hardware button didn't work. Funny thing is now the airplane button does work and my touchpad doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguelonlin 1285 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 11:41:31 2020 InstallationDate: Installed on 2019-12-28 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15s-fq1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=7f3239f4-69f1-48c8-bf53-81a609164416 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2019 dmi.bios.vendor: AMI dmi.bios.version: F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86C9 dmi.board.vendor: HP dmi.board.version: 56.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.06:bd09/10/2019:svnHP:pnHPLaptop15s-fq1xxx:pvr:rvnHP:rn86C9:rvr56.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-fq1xxx dmi.product.sku: 8PU49EA#ABE dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858089/+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 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
** Changed in: linux (Ubuntu Eoan) 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/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in HWE Next: Confirmed Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Confirmed Bug description: [Impact] With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT is set to Y, then it will make the legacy intel soc driver fail, and moreover the current sof driver can't support broadwell well, as a result, many broadwell computers with I2S codec can't support sound anymore. [Fix] Intel submitted a patch, it will make those two kconfig options exclusive, and the legacy soc's option has higher priority, if both of them are enabled, sof's option will be disabled. [Test Case] Build the kernel and check the debian/build/$buidling_dir/.config, the SND_SOC_SOF_BROADWELL_SUPPORT is disabled. [Regression Risk] Low, so far, the sof driver can't support broadwell machine well, so there is no machine use this driver yet. Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwel
[Kernel-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
I'm sorry, I changed the status of the report unconsciously to "Fix Released". It is possible to restore previous status? -- 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/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in HWE Next: Confirmed Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Confirmed Bug description: [Impact] With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT is set to Y, then it will make the legacy intel soc driver fail, and moreover the current sof driver can't support broadwell well, as a result, many broadwell computers with I2S codec can't support sound anymore. [Fix] Intel submitted a patch, it will make those two kconfig options exclusive, and the legacy soc's option has higher priority, if both of them are enabled, sof's option will be disabled. [Test Case] Build the kernel and check the debian/build/$buidling_dir/.config, the SND_SOC_SOF_BROADWELL_SUPPORT is disabled. [Regression Risk] Low, so far, the sof driver can't support broadwell machine well, so there is no machine use this driver yet. Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System
[Kernel-packages] [Bug 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station
Tested, still the same results: no usb available after the undock on laptop (I had a pendrive attached to test) uname -a Linux 5.3.0-27-generic #29~lp1857385 SMP Fri Jan 3 21:30:32 CST 2020 x86_64 x86_64 x86_64 GNU/Linux dmesg when I undock the laptop: [ 129.399949] usb 2-1: USB disconnect, device number 2 [ 129.417254] [drm] DM_MST: stopping TM on aconnector: 76d67240 [id: 77] [ 129.417557] [drm] DM_MST: Disabling connector: 242d96de [id: 81] [master: 76d67240] [ 129.418358] [drm] DM_MST: Disabling connector: 3436afd3 [id: 86] [master: 76d67240] [ 129.418543] [drm] DM_MST: Disabling connector: 1b62a1c6 [id: 91] [master: 76d67240] [ 129.431465] usb 3-4: USB disconnect, device number 2 [ 129.431478] usb 3-4.2: USB disconnect, device number 3 [ 129.467388] r8169 :03:00.0 enp3s0f0: Link is Down [ 129.581266] usb 2-4: USB disconnect, device number 3 [ 129.581280] usb 2-4.2: USB disconnect, device number 4 [ 129.581288] usb 2-4.2.4: USB disconnect, device number 6 [ 131.262762] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 131.262932] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of lines (the same) [ 134.530663] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 135.983562] [drm] Fence fallback timer expired on ring sdma0 [ 135.987559] [drm] Fence fallback timer expired on ring gfx [ 136.495422] [drm] Fence fallback timer expired on ring sdma0 [ 137.007323] [drm] Fence fallback timer expired on ring sdma0 [ 137.519202] [drm] Fence fallback timer expired on ring sdma0 [ 138.031056] [drm] Fence fallback timer expired on ring sdma0 [ 142.290091] iwlwifi :01:00.0: Error sending STATISTICS_CMD: time out after 2000ms. [ 142.290101] iwlwifi :01:00.0: Current CMD queue read_ptr 176 write_ptr 177 [ 142.292482] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 142.292486] iwlwifi :01:00.0: Status: 0x0080, count: 6 [ 142.292491] iwlwifi :01:00.0: Loaded firmware version: 46.6bf1df06.0 [ 142.292495] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 142.292499] iwlwifi :01:00.0: 0x26F4 | trm_hw_status0 [ 142.292502] iwlwifi :01:00.0: 0x | trm_hw_status1 [ 142.292506] iwlwifi :01:00.0: 0x0048853E | branchlink2 [ 142.292509] iwlwifi :01:00.0: 0x00192402 | interruptlink1 [ 142.292512] iwlwifi :01:00.0: 0x00479392 | interruptlink2 [ 142.292515] iwlwifi :01:00.0: 0x0001ACA2 | data1 [ 142.292518] iwlwifi :01:00.0: 0xFF001000 | data2 [ 142.292521] iwlwifi :01:00.0: 0xF000 | data3 [ 142.292524] iwlwifi :01:00.0: 0x4780C555 | beacon time [ 142.292527] iwlwifi :01:00.0: 0x059DFF69 | tsf low [ 142.292529] iwlwifi :01:00.0: 0x0163 | tsf hi [ 142.292532] iwlwifi :01:00.0: 0x | time gp1 [ 142.292535] iwlwifi :01:00.0: 0x08362F53 | time gp2 [ 142.292538] iwlwifi :01:00.0: 0x0001 | uCode revision type [ 142.292541] iwlwifi :01:00.0: 0x002E | uCode version major [ 142.292543] iwlwifi :01:00.0: 0x6BF1DF06 | uCode version minor [ 142.292546] iwlwifi :01:00.0: 0x0321 | hw version [ 142.292549] iwlwifi :01:00.0: 0x00C89004 | board version [ 142.292551] iwlwifi :01:00.0: 0x001C | hcmd [ 142.292554] iwlwifi :01:00.0: 0x80022002 | isr0 [ 142.292557] iwlwifi :01:00.0: 0x | isr1 [ 142.292559] iwlwifi :01:00.0: 0x08101002 | isr2 [ 142.292562] iwlwifi :01:00.0: 0x404000C6 | isr3 [ 142.292565] iwlwifi :01:00.0: 0x | isr4 [ 142.292567] iwlwifi :01:00.0: 0x0B48001C | last cmd Id [ 142.292570] iwlwifi :01:00.0: 0x0001ACA2 | wait_event [ 142.292573] iwlwifi :01:00.0: 0x | l2p_control [ 142.292576] iwlwifi :01:00.0: 0x2020 | l2p_duration [ 142.292578] iwlwifi :01:00.0: 0x | l2p_mhvalid [ 142.292581] iwlwifi :01:00.0: 0x | l2p_addr_match [ 142.292584] iwlwifi :01:00.0: 0x000D | lmpm_pmg_sel [ 142.292586] iwlwifi :01:00.0: 0x08081424 | timestamp [ 142.292589] iwlwifi :01:00.0: 0x38EC | flow_handler [ 142.292698] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 142.292701] iwlwifi :01:00.0: Status: 0x0080, count: 7 [ 142.292704] iwlwifi :01:00.0: 0x2066 | NMI_INTERRUPT_HOST [ 142.292707] iwlwifi :01:00.0: 0x | umac branchlink1 [ 142.292709] iwlwifi :01:00.0: 0xC00E | umac branchlink2 [ 142.292712] iwlwifi :01:00.0: 0x | umac interruptlink1 [ 142.292715] iwlwifi :01:00.0: 0x8044FE76 | umac interruptlink2 [ 142.292718] iwlwifi :01:00.0: 0x0100 | umac data1 [ 142.292720] iwlwifi :01:00.0: 0x8044FE76 | umac data2 [ 142.292723] iwlwifi :01:00.0: 0xDEADBEEF | umac data3 [ 142.292726] iwlwifi :01:00.0: 0x002E | umac major [ 142.292728] iwlwifi :01:00.0: 0x6BF1DF06 | umac minor [ 142.292731] iwlwifi :01:00.0: 0x08362EE9 | frame pointer [ 142.292733] iwlwifi :0
[Kernel-packages] [Bug 1854895] Re: touchpad stopped working after the update
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Touchpad 'Synaptics TM2956-002' on Lenovo 710-11isk completely unresponsive after kernel update to 4-15.0-072. Reverting to kernel 4.15.0-66 fixed it for me. -- 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/1854895 Title: touchpad stopped working after the update Status in Linux: New Status in XOrg-Driver-Synaptics: New Status in linux package in Ubuntu: Confirmed Bug description: After the automatic software update the touchpad stopped working in my laptop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anil 1722 F pulseaudio /dev/snd/controlC0: anil 1722 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 21:44:48 2019 InstallationDate: Installed on 2018-12-21 (346 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 3542 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=a85be26b-aca7-48bd-b03b-6a99e1587772 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 09V1VC dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn09V1VC:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1854895/+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 1832144] Re: Ubuntu 19.04 suspend freeze on Dell inspiron 7373
@emilio96 I think it's not a hardware problem, I just installed a xenial based distribution and suspend worked just fine in the clean installation before installing any updates, so the issue has being introduced in some update. It doesn't seem to be the kernel, because after the update I have started with the initial kernel and the problem remains. It's maybe related with xorg or video controllers. I will make a clean install again and start updating only some packages to find which one introduced the issue. -- 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/1832144 Title: Ubuntu 19.04 suspend freeze on Dell inspiron 7373 Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 19.04 in my Dell Inspiron 7373 and I am getting issues with suspend. When I lock the case or write the "systemctl suspend" command, the screen turn off, the system freeze and the laptop keeps turned on. I need to force the laptop turn off and on again. There are some cases when it suspends without issues, but most of the time it freezes. There are some workarounds for issues like this one but they are mostly for laptops using nvidia graphics. I am not sure how to provide debug information about this issue, but I can give it if someone tells me how to do it. "lsb_release -rd" output: Description:Ubuntu 19.04 Release:19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144/+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 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
I have a Lenovo Yoga S730 (marketed as Lenovo ideapad 730s in the US, mine is European) with the 9260 card and I can confirm that the same issue affects me. The wifi works fine in Windows 10. The only way I've managed to resolve the issue is by adding 11n_disable=1, but this caps my speed to 54mb which is too much of a compromise. -- 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/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 Kernel 5.3.0-18-generic Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card. Expected: Wifi connects, uploads/downloads as normal Symptom: Wifi connects, as soon as an upload/download (any heavy traffic) start, the system comes to a crawl, becomes barely usable, and I end up opening a prompt to reboot. The system is unusable. This happens even with the Live USB version. The only solution I found was to download a different (newer) firmware. Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz I then manually copy the contained firmware to /lib/firmware, remove all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode that the kernel expects to load. This completely resolves the issue. This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh installs): Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending SCAN_CFG_CMD: time out after 2000ms. Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue read_ptr 64 write_ptr 65 Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting before reading Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: 609870115 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | trm_hw_status0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | trm_hw_status1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | interruptlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | interruptlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode revision type Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode version major Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode version minor Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x190AF41B | l2p_addr_match Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7FF297FF | lmpm_pmg_sel Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5248C715 | timestamp Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xBBB939AF | flow_handler Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51
[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Nilesh's fix worked for me thanks ... Ubuntu 16.04 Dell Inspiron 15 3000 series kernel 4.15.0-72-generic -- 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/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0
[Kernel-packages] [Bug 1858375] [NEW] Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION
Public bug reported: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected eoan ** Tags added: apport-collected eoan ** Description changed: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set - I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and - it is because a kernel configuration option is not set. The kernel - configuration for the default kernel in 19.10 does not have this set so - I am assuming this is why I am getting this error message. I think this - should be enabled on kernels from now on to resolve the issue for other - devices that require it. + I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: test875 F pulseaudio + /dev/snd/controlC0: test875 F pulseaudio + /dev/snd/pcmC0D0c: test875 F...m pulseaudio + /dev/snd/pcmC0D0p: test875 F...m pulseaudio + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2020-01-05 (0 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: Dell Inc. Venue 10 Pro 5056 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-24-generic N/A + linux-backports-modules-5.3.0-24-generic N/A + linux-firmware1.183.3 + Tags: eoan + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/03/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.12.0 + dmi.board.name: 0PK97J + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 8 + dmi.chassis
[Kernel-packages] [Bug 1858375] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317803/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317812/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317804/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317813/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317806/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317810/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317809/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317811/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317805/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317807/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317815/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317814/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317808/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858375] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1858375/+attachment/5317816/+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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1826549] Re: Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with Linux kernel 5.0 (but kernel 4.18 works)
Thanks. If a fix exists in any release then we mark the bug as Fix Released. Note also that 19.04 reaches end of life within a few weeks from now (https://wiki.ubuntu.com/Releases). ** 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/1826549 Title: Mouse wheel scroll does not work after upgrade to Ubuntu 19.04 with Linux kernel 5.0 (but kernel 4.18 works) Status in linux package in Ubuntu: Fix Released Bug description: I've just upgraded to Ubuntu 19.04 and found that scrolling with mouse wheel does not work any more. My mouse is Microsoft Wireless Optical Mouse 2000. The mouse is connected to USB port via wireless receiver (Microsoft Wireless Mouse Receiver v1.0). I've found that problem is related to new Linux kernel 5.0. When I boot with previous kernel 4.18 all works good. The problem is reproducible with xorg and with wayland. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:23:34 2019 DistUpgraded: 2019-04-26 14:07:47,232 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2017-09-12 (591 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012 Bus 001 Device 002: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=249a1929-c0a6-4e3c-98dd-3a16b38e6c07 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-26 (0 days ago) dmi.bios.date: 07/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: Z270 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd07/20/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ270Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/1826549/+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 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
Sounds like it's maybe connected to a hardware multiplexer ("mux"). I
don't have experience with such systems, but you might find it useful to
look at these:
https://wiki.archlinux.org/index.php/Hybrid_graphics
\https://01.org/linuxgraphics/gfx-docs/drm/gpu/vga-switcheroo.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1846090
Title:
Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad
and screen - all in one)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57
CDT 2019
GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Oct 1 00:53:26 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
nvidia, 435.21, 5.0.0-29-generic, x86_64: installed
virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:1021]
Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile]
[1043:180e]
InstallationDate: Installed on 2019-09-27 (3 days ago)
InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 13d3:5755 IMC Networks
Bus 001 Device 004: ID 8087:0aaa Intel Corp.
Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic
root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX550GDX.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX550GDX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook Pro
dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+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 1856370] Re: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend
OK, thanks. If there are no more comments for 60 days then the bug will close automatically. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1856370 Title: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-435 package in Ubuntu: Incomplete Bug description: Every time I suspend my laptop, after I resume it, a black screen shows with the error message - GPU has fallen off the bus It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590 with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5 Description: Ubuntu 19.10 Release: 19.10 nvidia driver 435 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 16:31:58 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905] Subsystem: Dell Device [1028:0905] InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856370/+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 1858181] [NEW] System freeze with bluetooth mouse plugin, 19.10
You have been subscribed to a public bug: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze ubuntu -- System freeze with bluetooth mouse plugin, 19.10 https://bugs.launchpad.net/bugs/1858181 You received this bug notification because you are a member of Ker
[Kernel-packages] [Bug 1858181] Re: System freeze with bluetooth mouse plugin, 19.10
** Summary changed: - Xorg freeze with bluetooth mouse plugin, 19.10 + System freeze with bluetooth mouse plugin, 19.10 ** Package changed: xorg (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/1858181 Title: System freeze with bluetooth mouse plugin, 19.10 Status in linux package in Ubuntu: Confirmed Bug description: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-
[Kernel-packages] [Bug 1858375] 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/1858375 Title: Dell Venue 10 Pro 5056 needs CONFIG_PMIC_OPREGION Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.10 on this machine and I am getting messages in dmesg like this: [drm:mipi_exec_pmic [i915]] *ERROR* Your hardware requires CONFIG_PMIC_OPREGION and it is not set I traced the message to drivers/gpu/drm/i915/display/intel_dsi_vbt.c and it is because a kernel configuration option is not set. The kernel configuration for the default kernel in 19.10 does not have this set so I am assuming this is why I am getting this error message. I think this should be enabled on kernels from now on to resolve the issue for other devices that require it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test875 F pulseaudio /dev/snd/controlC0: test875 F pulseaudio /dev/snd/pcmC0D0c: test875 F...m pulseaudio /dev/snd/pcmC0D0p: test875 F...m pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Venue 10 Pro 5056 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=23c45bdc-e371-41b0-8ed3-be8532f4f53c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0PK97J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd12/03/2019:svnDellInc.:pnVenue10Pro5056:pvr:rvnDellInc.:rn0PK97J:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.family: Venue dmi.product.name: Venue 10 Pro 5056 dmi.product.sku: 06E7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858375/+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 1858181] 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/1858181 Title: System freeze with bluetooth mouse plugin, 19.10 Status in linux package in Ubuntu: Confirmed Bug description: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xser
[Kernel-packages] [Bug 1858338] [NEW] Keyboard unresponsive after suspend and resume (19.10)
You have been subscribed to a public bug: Since two to three weeks, my keyboard sometimes becomes unresponsive after wake up from resume. Often it is associated with an @ sign on black background, when the machine is resumed. After that I am back in the desktop. Trackpad and everything works, but the keyboard doesn't. This is on a 2009 macbook pro running uptodate 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 16:30:10 2020 DistUpgraded: 2019-10-06 16:30:12,792 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-24-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00b9] InstallationDate: Installed on 2019-01-12 (358 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Apple Inc. MacBookPro5,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=595c74ec-799d-4c25-bc8d-f06155d59f97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-06 (91 days ago) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP55.88Z.00AC.B03.0906151708 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F2268AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8: dmi.product.family: MacBook dmi.product.name: MacBookPro5,5 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu wayland-session -- Keyboard unresponsive after suspend and resume (19.10) https://bugs.launchpad.net/bugs/1858338 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 1858338] Re: Keyboard unresponsive after suspend and resume (19.10)
When you say the trackpad still works, can you also click on things and get them to respond? If you get a response to the trackpad then this is probably a keyboard bug to be assigned to the kernel. If you get no response from the trackpad and can only move the cursor then this is probably a gnome- shell crash under Xorg. Since you seem to have the 'wayland-session' tag here already I will assume the former... ** Package changed: xorg (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/1858338 Title: Keyboard unresponsive after suspend and resume (19.10) Status in linux package in Ubuntu: New Bug description: Since two to three weeks, my keyboard sometimes becomes unresponsive after wake up from resume. Often it is associated with an @ sign on black background, when the machine is resumed. After that I am back in the desktop. Trackpad and everything works, but the keyboard doesn't. This is on a 2009 macbook pro running uptodate 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 16:30:10 2020 DistUpgraded: 2019-10-06 16:30:12,792 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-24-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00b9] InstallationDate: Installed on 2019-01-12 (358 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Apple Inc. MacBookPro5,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=595c74ec-799d-4c25-bc8d-f06155d59f97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-06 (91 days ago) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP55.88Z.00AC.B03.0906151708 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F2268AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8: dmi.product.family: MacBook dmi.product.name: MacBookPro5,5 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858338/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu Bionic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu Bionic) Importance: Undecided => High ** Changed in: bluez (Ubuntu Bionic) Status: New => Triaged ** No longer affects: gnome-control-center (Ubuntu Bionic) ** No longer affects: pulseaudio (Ubuntu Bionic) ** No longer affects: pulseaudio -- 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/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Triaged Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1858338] 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/1858338 Title: Keyboard unresponsive after suspend and resume (19.10) Status in linux package in Ubuntu: Confirmed Bug description: Since two to three weeks, my keyboard sometimes becomes unresponsive after wake up from resume. Often it is associated with an @ sign on black background, when the machine is resumed. After that I am back in the desktop. Trackpad and everything works, but the keyboard doesn't. This is on a 2009 macbook pro running uptodate 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 16:30:10 2020 DistUpgraded: 2019-10-06 16:30:12,792 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-23-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-24-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00b9] InstallationDate: Installed on 2019-01-12 (358 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Apple Inc. MacBookPro5,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=595c74ec-799d-4c25-bc8d-f06155d59f97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-06 (91 days ago) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP55.88Z.00AC.B03.0906151708 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F2268AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8: dmi.product.family: MacBook dmi.product.name: MacBookPro5,5 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858338/+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 1858089] Re: Touchpad stopped working
Then it doesn't sound like a kernel issue. -- 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/1858089 Title: Touchpad stopped working Status in linux package in Ubuntu: Confirmed Bug description: Suddenly my touchpad stopped working, previously it did but now it doesn't appear on /proc/bus/input/devices. Before this my laptop used to enter in airplane mode when coming back from suspension and I couldn't get it out from airplane mode unless I rebooted it because the hardware button didn't work. Funny thing is now the airplane button does work and my touchpad doesn't. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguelonlin 1285 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 11:41:31 2020 InstallationDate: Installed on 2019-12-28 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15s-fq1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=7f3239f4-69f1-48c8-bf53-81a609164416 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2019 dmi.bios.vendor: AMI dmi.bios.version: F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86C9 dmi.board.vendor: HP dmi.board.version: 56.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.06:bd09/10/2019:svnHP:pnHPLaptop15s-fq1xxx:pvr:rvnHP:rn86C9:rvr56.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-fq1xxx dmi.product.sku: 8PU49EA#ABE dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858089/+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 1858181] Re: System freeze with bluetooth mouse plugin, 19.10
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc4 -- 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/1858181 Title: System freeze with bluetooth mouse plugin, 19.10 Status in linux package in Ubuntu: Confirmed Bug description: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserve
[Kernel-packages] [Bug 1730331] Re: ath10k_pci: firmware crashed!
I'm having the same problem with my LENOVO Z51-70 running openSUSE Tumbleweed, Kernel: 5.3.12. Here are the complete logs: Gopal's Pastebin English This document will expire in 6 days. [ 587.566084] PM: hibernation entry [ 587.647937] Filesystems sync: 0.081 seconds [ 587.647940] Freezing user space processes ... (elapsed 0.003 seconds) done. [ 587.650977] OOM killer disabled. [ 587.651339] PM: Marking nosave pages: [mem 0x-0x0fff] [ 587.651342] PM: Marking nosave pages: [mem 0x00058000-0x00058fff] [ 587.651344] PM: Marking nosave pages: [mem 0x00086000-0x000f] [ 587.651351] PM: Marking nosave pages: [mem 0x84fc8000-0x84fc8fff] [ 587.651354] PM: Marking nosave pages: [mem 0x84fd8000-0x84fd8fff] [ 587.651356] PM: Marking nosave pages: [mem 0x8683e000-0x8713dfff] [ 587.651463] PM: Marking nosave pages: [mem 0x9c353000-0x9cffefff] [ 587.651611] PM: Marking nosave pages: [mem 0x9d00-0x] [ 587.655153] PM: Basic memory bitmaps created [ 587.655207] PM: Preallocating image memory... done (allocated 865192 pages) [ 588.041670] PM: Allocated 3460768 kbytes in 0.38 seconds (9107.28 MB/s) [ 588.041671] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 588.043383] printk: Suspending console(s) (use no_console_suspend to debug) [ 588.043419] wlp3s0: deauthenticating from 68:c4:4d:66:09:27 by local choice (Reason: 3=DEAUTH_LEAVING) [ 588.049359] ath10k_pci :03:00.0: firmware crashed! (guid 3dc14778-dc3b-49dc-92a7-44c0473b6882) [ 588.049363] ath10k_pci :03:00.0: qca6164 hw2.1 target 0x0501 chip_id 0x003405ff sub 17aa:3545 [ 588.049364] ath10k_pci :03:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [ 588.049758] ath10k_pci :03:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08 [ 588.049966] ath10k_pci :03:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a [ 588.049967] ath10k_pci :03:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 588.050088] ath10k_pci :03:00.0: firmware register dump: [ 588.050090] ath10k_pci :03:00.0: [00]: 0x0501 0x 0x0092E4DC 0x25D4684B [ 588.050091] ath10k_pci :03:00.0: [04]: 0x0092E4DC 0x00060130 0x0018 0x0041A760 [ 588.050093] ath10k_pci :03:00.0: [08]: 0x25D46837 0x0040 0x 0x000A5C88 [ 588.050094] ath10k_pci :03:00.0: [12]: 0x0009 0x 0x0096C09C 0x0096C0A7 [ 588.050095] ath10k_pci :03:00.0: [16]: 0x0096BDBC 0x009286B6 0x 0x009287BD [ 588.050096] ath10k_pci :03:00.0: [20]: 0x4092E4DC 0x0041A710 0x 0x0F00 [ 588.050097] ath10k_pci :03:00.0: [24]: 0x809432A7 0x0041A770 0x0040D400 0xC092E4DC [ 588.050098] ath10k_pci :03:00.0: [28]: 0x80942BC4 0x0041A790 0x25D46837 0x0040 [ 588.050099] ath10k_pci :03:00.0: [32]: 0x80947BA7 0x0041A7B0 0x004050A8 0x0040E074 [ 588.050100] ath10k_pci :03:00.0: [36]: 0x809BDECC 0x0041A7D0 0x004050A8 0x0040E074 [ 588.050101] ath10k_pci :03:00.0: [40]: 0x8099638C 0x0041A7F0 0x004050A8 0x [ 588.050102] ath10k_pci :03:00.0: [44]: 0x80992076 0x0041A810 0x0044FD68 0x0046FFE8 [ 588.050103] ath10k_pci :03:00.0: [48]: 0x80996BD3 0x0041A830 0x0044FD68 0x [ 588.050104] ath10k_pci :03:00.0: [52]: 0x800B4405 0x0041A850 0x00422318 0x5002 [ 588.050105] ath10k_pci :03:00.0: [56]: 0x809A6C34 0x0041A8E0 0x0042932C 0x0042CA44 [ 588.050106] ath10k_pci :03:00.0: Copy Engine register dump: [ 588.050114] ath10k_pci :03:00.0: [00]: 0x00034400 1 1 3 3 [ 588.050121] ath10k_pci :03:00.0: [01]: 0x00034800 7 7 234 235 [ 588.050128] ath10k_pci :03:00.0: [02]: 0x00034c00 12 12 11 12 [ 588.050135] ath10k_pci :03:00.0: [03]: 0x00035000 13 13 14 13 [ 588.050142] ath10k_pci :03:00.0: [04]: 0x00035400 339 339 235 171 [ 588.050148] ath10k_pci :03:00.0: [05]: 0x00035800 0 0 0 0 [ 588.050155] ath10k_pci :03:00.0: [06]: 0x00035c00 21 21 21 21 [ 588.050162] ath10k_pci :03:00.0: [07]: 0x00036000 1 1 1 1 [ 588.050231] ath10k_pci :03:00.0: failed to delete WMI vdev 1: -108 [ 588.050255] ath10k_pci :03:00.0: could not suspend target (-108) [ 588.130469] ath10k_pci :03:00.0: cannot restart a device that hasn't been started [ 589.522573] ACPI: EC: interrupt blocked [ 589.525025] ACPI: Preparing to enter system sleep state S4 [ 589.525696] ACPI: EC: event blocked [ 589.525697] ACPI: EC: EC stopped [ 589.525698] PM: Saving platform NVS memory [ 589.525723] Disabling non-boot CPUs ... [ 589.526184] IRQ 47: no longer affine to CPU1 [ 589.527198] smpboot: CPU 1 is now offline [ 589.529097] IRQ 52: no longer affine to CPU2 [ 589.530733] smpboot: CPU 2 is now offline [ 589.532462] IRQ 18: no longer affine to CPU3 [ 589.532468] IRQ 44: no longer affine to CPU3 [ 589.532472] IRQ 46: no longer affine to CPU3 [ 589.533487] smpboot: CPU 3 is
[Kernel-packages] [Bug 1853984] Re: [hns-1126]net: hns3: fix port setting handle for fibre port
** Description changed: [Impact] For hardware doesn't support use specified speed and duplex to negotiate, it's unnecessary to check and modify the port speed and duplex for fibre port when autoneg is on. [Test Case] + `sudo ethtool -s eno1 autoneg off speed 10 duplex full` + `sudo ethtool -s eno1 autoneg on` + commands shall return 0 [Fix] 24283ece5a0f net: hns3: fix port setting handle for fibre port [Regression Risk] Patch restricted to hns3 driver. - "[Bug Description] For hardware doesn't support use specified speed and duplex to negotiate, it's unnecessary to check and modify the port speed and duplex for fibre port when autoneg is on. [Steps to Reproduce] 1.ethtool -s eth* autoneg off speed 10 duplex full 2.ethtool -s eth* autoneg on [Actual Results] set autoneg on fail [Expected Results] set autoneg on ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] Not check and modify the port speed and duplex for fibre port when autoneg on." net: hns3: fix port setting handle for fibre port -- 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/1853984 Title: [hns-1126]net: hns3: fix port setting handle for fibre port Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: Invalid Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: In Progress Status in kunpeng920 ubuntu-19.10 series: In Progress Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: Fix Released Bug description: [Impact] For hardware doesn't support use specified speed and duplex to negotiate, it's unnecessary to check and modify the port speed and duplex for fibre port when autoneg is on. [Test Case] `sudo ethtool -s eno1 autoneg off speed 10 duplex full` `sudo ethtool -s eno1 autoneg on` commands shall return 0 [Fix] 24283ece5a0f net: hns3: fix port setting handle for fibre port [Regression Risk] Patch restricted to hns3 driver. "[Bug Description] For hardware doesn't support use specified speed and duplex to negotiate, it's unnecessary to check and modify the port speed and duplex for fibre port when autoneg is on. [Steps to Reproduce] 1.ethtool -s eth* autoneg off speed 10 duplex full 2.ethtool -s eth* autoneg on [Actual Results] set autoneg on fail [Expected Results] set autoneg on ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] Not check and modify the port speed and duplex for fibre port when autoneg on." net: hns3: fix port setting handle for fibre port To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853984/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
** No longer affects: gnome-control-center (Ubuntu) ** Also affects: pulseaudio (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu Eoan) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu Eoan) Importance: Undecided => High ** Changed in: bluez (Ubuntu Eoan) Status: New => Triaged ** Also affects: pulseaudio (Ubuntu Focal) Importance: High Status: Invalid ** Also affects: bluez (Ubuntu Focal) Importance: High Status: Fix Released ** No longer affects: pulseaudio (Ubuntu Eoan) ** No longer affects: pulseaudio (Ubuntu Focal) ** Summary changed: - Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected + Bluetooth headphones default to low quality headset mode and fails to switch to A2DP when selected ** Summary changed: - Bluetooth headphones default to low quality headset mode and fails to switch to A2DP when selected + Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Triaged Status in bluez source package in Eoan: Triaged Status in bluez source package in Focal: Fix Released Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1853983] Re: [hns-1126]net: hns3: revert to old channel when setting new channel num fail
** Description changed: [Impact] With specific ethtool commands, ethernet does not work [Test Case] + run VF on VM with 3G memory and load VF driver + ethtool -G eth0 tx 3 rx 3 + ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 + ethtool -G eth0 tx 32760 rx 32760 + ethtool -L eth0 combined 32 [Fix] 3a5a5f06d4d2 net: hns3: revert to old channel when setting new channel num fail [Regression Risk] Patch restricted to hns3 driver. - "[Bug Description] After setting new channel num, it needs free old ring memory and allocate new ring memory. If there is no enough memory and allocate new ring memory fail, the ring may initialize fail. To make sure the network interface can work normally, driver should revert the channel to the old configuration. [Steps to Reproduce] 1.run VF on VM with 3G memory 2.load VF driver 3.ethtool -G eth0 tx 3 rx 3 4.ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 5.ethtool -G eth0 tx 32760 rx 32760 6.ethtool -L eth0 combined 32 7.ping [Actual Results] netdevice can not work [Expected Results] ping ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] Revert the channel to the old configuration when allocate new ring memory fail." ** Description changed: [Impact] With specific ethtool commands, ethernet does not work [Test Case] run VF on VM with 3G memory and load VF driver ethtool -G eth0 tx 3 rx 3 ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 ethtool -G eth0 tx 32760 rx 32760 ethtool -L eth0 combined 32 + ethernet shall still be functional after these commands [Fix] 3a5a5f06d4d2 net: hns3: revert to old channel when setting new channel num fail [Regression Risk] Patch restricted to hns3 driver. "[Bug Description] After setting new channel num, it needs free old ring memory and allocate new ring memory. If there is no enough memory and allocate new ring memory fail, the ring may initialize fail. To make sure the network interface can work normally, driver should revert the channel to the old configuration. [Steps to Reproduce] 1.run VF on VM with 3G memory 2.load VF driver 3.ethtool -G eth0 tx 3 rx 3 4.ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 5.ethtool -G eth0 tx 32760 rx 32760 6.ethtool -L eth0 combined 32 7.ping [Actual Results] netdevice can not work [Expected Results] ping ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] Revert the channel to the old configuration when allocate new ring memory fail." -- 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/1853983 Title: [hns-1126]net: hns3: revert to old channel when setting new channel num fail Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: In Progress Status in kunpeng920 ubuntu-19.10 series: In Progress Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: Fix Released Bug description: [Impact] With specific ethtool commands, ethernet does not work [Test Case] run VF on VM with 3G memory and load VF driver ethtool -G eth0 tx 3 rx 3 ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 ethtool -G eth0 tx 32760 rx 32760 ethtool -L eth0 combined 32 ethernet shall still be functional after these commands [Fix] 3a5a5f06d4d2 net: hns3: revert to old channel when setting new channel num fail [Regression Risk] Patch restricted to hns3 driver. "[Bug Description] After setting new channel num, it needs free old ring memory and allocate new ring memory. If there is no enough memory and allocate new ring memory fail, the ring may initialize fail. To make sure the network interface can work normally, driver should revert the channel to the old configuration. [Steps to Reproduce] 1.run VF on VM with 3G memory 2.load VF driver 3.ethtool -G eth0 tx 3 rx 3 4.ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 5.ethtool -G eth0 tx 32760 rx 32760 6.ethtool -L eth0 combined 32 7.ping [Actual Results] netdevice can not work [Expected Results] ping ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] Revert the channel to the old configuration when allocate new ring memory fail." To manage
[Kernel-packages] [Bug 1853948] Re: [hns-1126]net: hns3: fix flow control configure issue for fibre port
** Description changed: [Impact] Flow control parameters of fibre port can not be set after enable flow control autoneg, as flow control autoneg is unsupported for fibre port [Test Case] + Turning on/off tx pause and ethtool shall report status accordingly. [Fix] fb89629f2ecf net: hns3: fix flow control configure issue for fibre port [Regression Risk] Patch restricted to hns3 driver. - "[Bug Description] Flow control parameters of fibre port can not be set after enable flow control autoneg, as flow control autoneg is unsupported for fibre port. [Steps to Reproduce] 1.link up fibre port and enable flow control autoneg 2.check status of tx pause and rx pause 3.turn off tx pause 4.checkout status of tx pause [Actual Results] tx pause is on [Expected Results] tx pause is off [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] This patch return -EOPNOTSUPP when user tries to enable flow control autoneg." net: hns3: fix flow control configure issue for fibre port -- 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/1853948 Title: [hns-1126]net: hns3: fix flow control configure issue for fibre port Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: In Progress Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Flow control parameters of fibre port can not be set after enable flow control autoneg, as flow control autoneg is unsupported for fibre port [Test Case] Turning on/off tx pause and ethtool shall report status accordingly. [Fix] fb89629f2ecf net: hns3: fix flow control configure issue for fibre port [Regression Risk] Patch restricted to hns3 driver. "[Bug Description] Flow control parameters of fibre port can not be set after enable flow control autoneg, as flow control autoneg is unsupported for fibre port. [Steps to Reproduce] 1.link up fibre port and enable flow control autoneg 2.check status of tx pause and rx pause 3.turn off tx pause 4.checkout status of tx pause [Actual Results] tx pause is on [Expected Results] tx pause is off [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] This patch return -EOPNOTSUPP when user tries to enable flow control autoneg." net: hns3: fix flow control configure issue for fibre port To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853948/+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 1853937] Re: [hns-1126] net: hns: add support for vlan TSO
** Description changed: [Impact] hns hardware supports vlan TSO but driver does not set the flag. [Test Case] - + Performance run through vlan TSO shall reach limitation. [Fix] 0d581ba311a2 net: hns: add support for vlan TSO [Regression Risk] Patch restricted to hns3 driver. - """[Bug Description] When add vlan to the net ports, the performance is almost 50% lower than no vlan. [Steps to Reproduce] 1.add vlan to net port(10G fibre); 2.add ip to this vlan; 3.run iperf to test the performance; [Actual Results] iperf result is about 5~6Gbp/s [Expected Results] iperf result is about 9.4Gbp/s [Reproducibility] Conditionally Recur [Additional information] Hardware: D05 Firmware: NA Kernel: NA [Resolution] The hip07 chip support vlan TSO, adds NETIF_F_TSO and NETIF_F_TSO6 flags to vlan_features.""" net: hns: add support for vlan TSO -- 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/1853937 Title: [hns-1126] net: hns: add support for vlan TSO Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: In Progress Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] hns hardware supports vlan TSO but driver does not set the flag. [Test Case] Performance run through vlan TSO shall reach limitation. [Fix] 0d581ba311a2 net: hns: add support for vlan TSO [Regression Risk] Patch restricted to hns3 driver. """[Bug Description] When add vlan to the net ports, the performance is almost 50% lower than no vlan. [Steps to Reproduce] 1.add vlan to net port(10G fibre); 2.add ip to this vlan; 3.run iperf to test the performance; [Actual Results] iperf result is about 5~6Gbp/s [Expected Results] iperf result is about 9.4Gbp/s [Reproducibility] Conditionally Recur [Additional information] Hardware: D05 Firmware: NA Kernel: NA [Resolution] The hip07 chip support vlan TSO, adds NETIF_F_TSO and NETIF_F_TSO6 flags to vlan_features.""" net: hns: add support for vlan TSO To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853937/+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 1843873] Re: Sound distored on Hades Canyon NUC
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc5 -- 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/1843873 Title: Sound distored on Hades Canyon NUC Status in linux package in Ubuntu: Confirmed Bug description: On a fresh install of vanilla Ubuntu 19.04 sound over HDMI is distorted (unusable). Problem does not occur with a fresh install of Ubuntu 18.10 Full Specs for the device can be found here : https://www.intel.co.uk/content/www/uk/en/products/boards-kits/nuc/kits/nuc8i7hvk.html --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sparky 1447 F pulseaudio /dev/snd/controlC1: sparky 1447 F pulseaudio /dev/snd/pcmC1D10p: sparky 1447 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-09-25 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Intel(R) Client Systems NUC8i7HVK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=0e229a17-3e98-4f4f-8e41-20b99ff848db ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: HNKBLi70.86A.0058.2019.0705.1646 dmi.board.name: NUC8i7HVB dmi.board.vendor: Intel Corporation dmi.board.version: J68196-504 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0058.2019.0705.1646:bd07/05/2019:svnIntel(R)ClientSystems:pnNUC8i7HVK:pvrJ71485-504:rvnIntelCorporation:rnNUC8i7HVB:rvrJ68196-504:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i7HVK dmi.product.version: J71485-504 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843873/+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 1851216] Re: System hangs at early boot
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1851216 Title: System hangs at early boot Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [SRU Justification] [Impact] Some recent platform seem to have an unstable HPET, which is used to calibrate TSC but turns out to mark an actual stable TSC clocksource as unstable, and then fallback to that unstable HPET as main clocksource. A previous fix was proposed in bug 1840239, which is then observed to hang platforms with modern chipsets including Skylake and ApolloLake at early boot stage when HPET is disabled. [Fix] Commit c8c4076723da "x86/timer: Skip PIT initialization on modern chipsets" included in v5.3-rc1 to be backported. [Test Case] Boot with kernel built with this change, and see if it will hang right after grub loaded initramfs image. [Regression Risk] Low. This change detects the hardware that requires explicit PIT initialization skip and skip it. For those unaffected systems, they remain unaffected. == original description = After upgrading kernel to linux-image-4.15.0-1061 (proposed), system hangs at very beginning of booting, leaving Grub messages "loading..." on the console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1060-oem 4.15.0-1060.69 ProcVersionSignature: Ubuntu 4.15.0-1060.69-oem 4.15.18 Uname: Linux 4.15.0-1060-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: u 1977 F...m pulseaudio /dev/snd/pcmC1D0p: u 1977 F...m pulseaudio /dev/snd/controlC0: u 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 4 17:15:56 2019 InstallationDate: Installed on 2019-11-04 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Precision 5530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1060-oem root=UUID=baa02b0a-d18f-41d2-9e2b-2d057742013c ro mem_sleep_default=deep nvidia-drm.modeset=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-1060-oem N/A linux-backports-modules-4.15.0-1060-oem N/A linux-firmware 1.173.9 SourcePackage: linux-oem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0184M4 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0184M4:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851216/+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 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
Patch for Ubuntu 19.10 ** Patch added: "bluez_5.50-0ubuntu5.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845046/+attachment/5317845/+files/bluez_5.50-0ubuntu5.debdiff ** Changed in: bluez (Ubuntu Eoan) Status: Triaged => Fix Committed -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Triaged Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1857459] Re: audio doesn't work
$ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good v5.4-rc2 $ git bisect bad v5.4-rc3 $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. -- 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/1857459 Title: audio doesn't work Status in linux package in Ubuntu: Incomplete Bug description: Kernel: Linux version 5.4.6-050406-generic (kernel@kathleen) (gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1)) #201912211140 SMP Sat Dec 21 11:43:01 UTC 2019 In 5.3.18 audio was ok. Now in the setting there is written "Dummy output" and alsamixer doesn't show any devices. Hardware: sudo lspci -vnvn (see the log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857459/+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 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
Hi Anthony, As you may have found, this commit was landed in bug 1851216 for a possible system hang due to bug 1840239, and since it is a solution backported from v5.3-rc1, and you also stated this can be reproduced in v5.5-rc1, then you may probably want to either 1) try a slightly newer v5.5-rc5 mainline kernel[1], or 2) file a upstream bug in kernel bugzilla[2]. [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ [2]: https://bugzilla.kernel.org/ -- 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 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
** Description changed: - Whenever I turn on my headphones theyll connect to my computer but im + [Impact] + + Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: pulseaudio 1:11.1-1ubuntu7.2 - ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 - Uname: Linux 5.0.0-29-generic x86_64 - NonfreeKernelModules: nvidia_modeset nvidia - ApportVersion: 2.20.9-0ubuntu7.7 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: litleck1398 F pulseaudio - /dev/snd/controlC0: litleck1398 F pulseaudio - CurrentDesktop: ubuntu:GNOME - Date: Mon Sep 23 17:07:59 2019 - InstallationDate: Installed on 2019-09-22 (0 days ago) - InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: pulseaudio - Symptom: audio - Symptom_Card: WH-1000XM3 - Symptom_Type: High background noise, or volume is too low - Title: [WH-1000XM3, playback] Background noise or low volume - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 02/12/2019 - dmi.bios.vendor: Alienware - dmi.bios.version: 1.0.19 - dmi.board.name: 01NYPT - dmi.board.vendor: Alienware - dmi.board.version: A00 - dmi.chassis.type: 3 - dmi.chassis.vendor: Alienware - dmi.chassis.version: Not Specified - dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: - dmi.product.family: Alienware - dmi.product.name: Alienware Aurora R5 - dmi.product.sku: 0729 - dmi.product.version: 1.0.19 - dmi.sys.vendor: Alienware + [Test Case] + + 0. Set up your Bluetooth headphones with Ubuntu. + 1. Turn off the headphones. + 2. Turn on the headphones. + 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). + + [Regression Potential] + + Low. Only the headset code path is affected and the fix has already been + released for some time in BlueZ 5.51 onward. -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Triaged Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1858077] Re: Intel(R) Wireless-AC 9260 160MHz, REV=0x324 crash, lock and restart, Error sending STATISTICS_CMD: time out after 2000ms
Seem related to bug 1848921 as well for they share similar error dumps: [ 4866.195416] iwlwifi :01:00.0: Error sending STATISTICS_CMD: time out after 2000ms. ** Summary changed: - iwlwifi crash, lock and restart + Intel(R) Wireless-AC 9260 160MHz, REV=0x324 crash, lock and restart, Error sending STATISTICS_CMD: time out after 2000ms ** Summary changed: - Intel(R) Wireless-AC 9260 160MHz, REV=0x324 crash, lock and restart, Error sending STATISTICS_CMD: time out after 2000ms + Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [8086:2526] subsystemid [8086:0014] crash, lock and restart, Error sending STATISTICS_CMD: time out after 2000ms -- 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/1858077 Title: Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [8086:2526] subsystemid [8086:0014] crash, lock and restart, Error sending STATISTICS_CMD: time out after 2000ms Status in linux package in Ubuntu: Confirmed Bug description: My whole system was frozen for a few seconds, then it got back to normal. In dmesg I found iwlwifi module crash, please see the attached log. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.24.28 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piontec2965 F pulseaudio /dev/snd/controlC1: piontec2965 F pulseaudio /dev/snd/controlC0: piontec2965 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 09:55:20 2020 InstallationDate: Installed on 2019-12-07 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20NJ0010PB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-rootfs ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NJ0010PB dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NJ0010PB:pvrThinkPadT495:rvnLENOVO:rn20NJ0010PB:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NJ0010PB dmi.product.sku: LENOVO_MT_20NJ_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858077/+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 1728651] Re: Intel(R) Dual Band Wireless AC 8260, REV=0x208 [8086:24f3] subsystemid [8086:0010]: System hangs after iwlwifi firmware crash
** Summary changed: - System hangs after iwlwifi firmware crash + Intel(R) Dual Band Wireless AC 8260, REV=0x208 [8086:24f3] subsystemid [8086:0010]: System hangs after iwlwifi firmware crash -- 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/1728651 Title: Intel(R) Dual Band Wireless AC 8260, REV=0x208 [8086:24f3] subsystemid [8086:0010]: System hangs after iwlwifi firmware crash Status in linux-firmware package in Ubuntu: Confirmed Bug description: Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at unpredictable times. I have experienced probably 20 hangs. Once the system is hung no mouse movement, NumLock toggle, VT switch, Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any audio playing is stuck looping in the hardware buffer. The system is really stuck. Only the keyboard backlight is still responsive. The only correlation I have noticed is that the system only hangs if WiFi is enabled. This morning I experienced two hangs in ten minutes necessitating reboots. Having disabled WiFi the system has been stable since ~1100 (~5 hours). Often, I see a iwlwifi hardware reset in the logs before the system dies: /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x8200. (apport has hopefully uploaded the full log, please lmk if not). Sometimes the message doesn't make it into the logs, and ext4 truncates the file at the next mount. There seems to be no correlation with any messages immediately before the wifi chip dies. It doesn't seem to matter whether I'm at home or at work. I have wired ethernet at work simultaneously with wifi, but the wifi provides IPv6 so I would imagine most traffic uses wifi, so it's hard to say whether there's any effect of the traffic load on the probability of failure. Here is a sample of the firmware load: /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi :02:00.0: enabling device ( -> 0002) /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error -2 /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi :02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error -2 /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi :02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) Any help appreciated. Thanks, Bruce ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: KDE Date: Mon Oct 30 16:15:43 2017 DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: kubuntu GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c] InstallationDate: Installed on 2016-09-09 (416 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP EliteBook 820 G3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.13 dmi.board.name: 807C dmi.board.vendor: HP dmi.board.version: KBC Version 85.74 dmi.chassis.asset.tag: 5CG6354JW5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To
[Kernel-packages] [Bug 1858299] Re: This laptop contains a touchpadwhich is not recognized.
Please test this kernel: https://people.canonical.com/~khfeng/lp1858299/ -- 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/1858299 Title: This laptop contains a touchpadwhich is not recognized. Status in linux package in Ubuntu: Confirmed Bug description: This laptop contains a touchpad which is not recognized. The laptop is the Trekstore Surfbook E11B. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deathmetal 1119 F pulseaudio CurrentDesktop: LXQt Date: Sat Jan 4 23:09:34 2020 InstallationDate: Installed on 2020-01-04 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TREKSTOR SURFBOOK E11B ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=c3bcb5e6-3626-422a-b348-dbdb31c269d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BIOS_V1.1.5 dmi.board.asset.tag: Default string dmi.board.name: Gemini_Lake_Celeron_V01 dmi.board.vendor: TS_EMDOOR dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBIOS_V1.1.5:bd08/30/2018:svnTREKSTOR:pnSURFBOOKE11B:pvrDefaultstring:rvnTS_EMDOOR:rnGemini_Lake_Celeron_V01:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Surfbook dmi.product.name: SURFBOOK E11B dmi.product.sku: NFCN4SW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858299/+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 1858206] Re: WiFi adapter does not work: Linksys WUSB6400M [13b1:0043]
** Summary changed: - WiFi adapter does not work: Linksys WUSB6400M + WiFi adapter does not work: Linksys WUSB6400M [13b1:0043] -- 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/1858206 Title: WiFi adapter does not work: Linksys WUSB6400M [13b1:0043] Status in linux package in Ubuntu: Confirmed Bug description: WiFi adapter does not work: Linksys WUSB6400M. Attach image. --- Others: With https://askubuntu.com/questions/1178802/proper-way-of-installing-wifi-drivers-rtl8822bu and kernel 5.4.7 work fine! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1903 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 10:46:26 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (396 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2018-12-02 (396 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858206/+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 1858231] Re: QCA6174 Wifi adapter not functional
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1858231 Title: QCA6174 Wifi adapter not functional Status in linux package in Ubuntu: Confirmed Bug description: The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from the live cd and an install. It is functional in a 18.04 install. At boot, the kernel log contains the following messages in 19.10: [ 15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity mapping [ 15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12 [ 15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 0: -12 [ 15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: -12 [ 15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12 [ 15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 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: ed 1932 F pulseaudio /dev/snd/controlC0: ed 1932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 14:31:15 2020 InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. Precision 7540 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0499T7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd07/24/2019:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858231/+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 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed
** Changed in: linux (Ubuntu) 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/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in linux source package in Disco: Fix Released Bug description: == SRU Justification == fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs has received more than one expected event: <<>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24) fanotify06.c:220: FAIL: group 3 got event fanotify06.c:220: FAIL: group 4 got event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:220: FAIL: group 6 got event fanotify06.c:220: FAIL: group 7 got event fanotify06.c:220: FAIL: group 8 got event Summary: passed 9 failed 9 skipped 0 warnings 0 This duplicated event was generated with operations on files with "fake" path. == Fix == * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path) This patch can be cherry-picked into Disco. Older kernels are not affected by this issue (without commit d1d04ef8) == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/ Verified on a KVM node, the fanotify06 test will pass with this patched disco kernel: fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30 fanotify06.c:230: PASS: group 3 got no event fanotify06.c:230: PASS: group 4 got no event fanotify06.c:230: PASS: group 5 got no event fanotify06.c:230: PASS: group 6 got no event fanotify06.c:230: PASS: group 7 got no event fanotify06.c:230: PASS: group 8 got no event == Regression Potential == Low, fix limited to the overlayfs and just corrects the flag behaviour with "fake" path. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 17 04:37 seq crw-rw 1 root audio 116, 33 Jun 17 04:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 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: CurrentDmesg: Date: Mon Jun 17 04:40:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/
[Kernel-packages] [Bug 1854213] Re: RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] subsystem [17aa:38a8]: No Wifi Adapter found - Lenevo Ideapad 330 series
** Summary changed: - No Wifi Adapter found - Lenevo Ideapad 330 series + RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] subsystem [17aa:38a8]: No Wifi Adapter found - Lenevo Ideapad 330 series -- 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/1854213 Title: RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] subsystem [17aa:38a8]: No Wifi Adapter found - Lenevo Ideapad 330 series Status in linux package in Ubuntu: Confirmed Status in rtl8821ce package in Ubuntu: New Bug description: Commands executed 1. ubuntu-bug linux 2. cat /proc/version_signature Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7 3. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error 4. lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 5. apt-cache policy pkgname N: Unable to locate package pkgname What you expected to happen? Connect to the Internet after installing the update What happened instead? No Wifi Adapter found message displayed instead ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.2 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 28 00:44:57 2019 InstallationDate: Installed on 2019-06-05 (175 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: athena 1573 F pulseaudio /dev/snd/controlC0: athena 1573 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-05 (212 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp3s0f3u3 no wireless extensions. enp2s0no wireless extensions. lono wireless extensions. MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.173.13 Tags: bionic Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN46WW 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 330-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854213/+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 1830678] Re: netns_sysfs from containers test suite in LTP failed with KVM kernel
This should be fixed from the test case side. ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-kvm (Ubuntu Disco) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1830678 Title: netns_sysfs from containers test suite in LTP failed with KVM kernel Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Invalid Bug description: <<>> tag=netns_sysfs stime=1559024934 cmdline="netns_sysfs.sh" contacts="" analysis=exit <<>> incrementing stop RTNETLINK answers: Operation not supported netns_sysfs 1 TBROK: failed to add a new (host) dummy device <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=1 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1035-kvm 4.15.0-1035.35 ProcVersionSignature: User Name 4.15.0-1035.35-kvm 4.15.18 Uname: Linux 4.15.0-1035-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 28 06:22:51 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830678/+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 1748395] Re: btrfs related tests in ubuntu_ecryptfs failed on Precise amd64 / i386
Precise ESM ends April 2019. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Triaged => Won't Fix -- 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/1748395 Title: btrfs related tests in ubuntu_ecryptfs failed on Precise amd64 / i386 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: This issue can be reproduced in 3.13.0-142 in proposed and 3.13.0-141. So it should not be considered as a regression. We didn't have this issue before, until I'm testing 3.13 Precise LTS kernel on the systems (201307-13930 - i386 and 201308-14073 - amd64) in Cert lab instead of using our regular regression-testing test pool from kernel team this cycle. All btrfs related tests in ubuntu_ecryptfs failed. miscdev-bad-count.sh.btrfs extend-file-random.sh.btrfs trunc-file.sh.btrfs directory-concurrent.sh.btrfs file-concurrent.sh.btrfs lp-994247.sh.btrfs llseek.sh.btrfs lp-469664.sh.btrfs lp-524919.sh.btrfs lp-509180.sh.btrfs lp-613873.sh.btrfs lp-745836.sh.btrfs lp-870326.sh.btrfs lp-885744.sh.btrfs lp-926292.sh.btrfs inotify.sh.btrfs mmap-bmap.sh.btrfs mmap-close.sh.btrfs mmap-dir.sh.btrfs read-dir.sh.btrfs setattr-flush-dirty.sh.btrfs inode-race-stat.sh.btrfs lp-911507.sh.btrfs lp-561129.sh.btrfs mknod.sh.btrfs link.sh.btrfs xattr.sh.btrfs namelen.sh.btrfs The output is not really helpful, it's just saying that the return value is 1, like: 03:37:47 DEBUG| Running 'tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs' 03:37:59 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/ubuntu_ecryptfs.py", line 45, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs Exit status: 1 Duration: 12.1887788773 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748395/+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
