[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic
NO response yet, we really want to fix it but need some way to verify it. Sorry to ask once again, but we need to get this unblocked. @Vern - can you use the setup to verify the two planned uploads for Bionic and Cosmic? -- 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/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Fix Released Status in ipxe-qemu-256k-compat package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in ipxe source package in Trusty: Won't Fix Status in ipxe source package in Xenial: Won't Fix Status in ipxe source package in Bionic: Incomplete Status in ipxe source package in Cosmic: Incomplete Status in ipxe source package in Disco: Fix Released Bug description: [Impact] * VLAN 0 is special (for QoS actually, not a real VLAN) * Some components in the stack accidentally strip it, so does ipxe in this case. * Fix by porting a fix that is carried by other distributions as upstream didn't follow the suggestion but it is needed for the use case affected by the bug here (Thanks Andres) [Test Case] * Comment #42 contains a virtual test setup to understand the case but it does NOT trigger the isse. That requires special switch HW that adds VLAN 0 tags for QoS. Therefore Vern (reporter) will test that on a customer site with such hardware being affected by this issue. [Regression Potential] * The only reference to VLAN tags on iPXE boot that we found was on iBFT boot for SCSI, we tested that in comment #34 and it still worked fine. * We didn't see such cases on review, but there might be use cases that made some unexpected use of the headers which are now stripped. But that seems wrong. [Other Info] * n/a --- I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+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 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
Is "dpm_run_callback()" still shown in dmesg? -- 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/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+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 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
According to [1], new firmware can fix the issue.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799988/comments/42
--
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/1807974
Title:
Wireless regularly breaking (ath10k firmware crashed!) after upgrade
to Cosmic
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when
this machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has appeared/become much worse on Cosmic.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-11-generic 4.18.0-11.12
ProcVersionSignature:
[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
I didn't test it with disabled Bluetooth. So cannot provide correct information. However, there is some update on the issue. Recently (4 days ago), I have rolled back to default kernel 4.18 and updated atheros firmware to one from kvalo (QCA-ATH10KwWLAN.RM.4.4.1-00128-QCARMSWPZ). By now, the issue haven't occurred at all. -- 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/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Can confirm that installing kernel 5.0-rc1 using UKUU that sound from the speakers and earphones now work on my Zenbook UX391UA. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Please attach output of `sudo lspci -vvv -s 02:00.0`.
I think I've seen several platforms that requires to tweak PCI ASPM bits.
--
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/1807974
Title:
Wireless regularly breaking (ath10k firmware crashed!) after upgrade
to Cosmic
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when
this machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has appeared/become much worse on Cosmic.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-11-generic 4.18.0-11.12
ProcVersionSignature:
[Kernel-packages] [Bug 1796016] Re: Unable to build sysdig module on Trusty 4.15 Azure kernel
Test disabled on Trusty: https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=d8f563074e01f308a0b43260f45ca0dc1dfc8f15 ** No longer affects: linux-signed-azure (Ubuntu) ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** No longer affects: sysdig (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1796016 Title: Unable to build sysdig module on Trusty 4.15 Azure kernel Status in ubuntu-kernel-tests: Fix Released Bug description: On Trusty + 4.15 Azure kernel, the sysdig cannot be installed: $ cat /var/lib/dkms/sysdig/0.1.87/build/make.log DKMS make.log for sysdig-0.1.87 for kernel 4.15.0-1023-azure (x86_64) Thu Oct 4 03:32:04 UTC 2018 make: Entering directory `/usr/src/linux-headers-4.15.0-1023-azure' Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel" CC [M] /var/lib/dkms/sysdig/0.1.87/build/main.o /var/lib/dkms/sysdig/0.1.87/build/main.c: In function ‘ppm_open’: /var/lib/dkms/sysdig/0.1.87/build/main.c:196:27: error: ‘struct file’ has no member named ‘f_dentry’ int ring_no = iminor(filp->f_dentry->d_inode); ^ /var/lib/dkms/sysdig/0.1.87/build/main.c: In function ‘ppm_release’: /var/lib/dkms/sysdig/0.1.87/build/main.c:291:27: error: ‘struct file’ has no member named ‘f_dentry’ int ring_no = iminor(filp->f_dentry->d_inode); ^ /var/lib/dkms/sysdig/0.1.87/build/main.c: In function ‘ppm_ioctl’: /var/lib/dkms/sysdig/0.1.87/build/main.c:349:28: error: ‘struct file’ has no member named ‘f_dentry’ int ring_no = iminor(filp->f_dentry->d_inode); ^ /var/lib/dkms/sysdig/0.1.87/build/main.c:362:28: error: ‘struct file’ has no member named ‘f_dentry’ int ring_no = iminor(filp->f_dentry->d_inode); ^ /var/lib/dkms/sysdig/0.1.87/build/main.c: In function ‘ppm_mmap’: /var/lib/dkms/sysdig/0.1.87/build/main.c:482:28: error: ‘struct file’ has no member named ‘f_dentry’ int ring_no = iminor(filp->f_dentry->d_inode); ^ /var/lib/dkms/sysdig/0.1.87/build/main.c: At top level: /var/lib/dkms/sysdig/0.1.87/build/main.c:1015:5: error: conflicting types for ‘__access_remote_vm’ int __access_remote_vm(struct task_struct *t, struct mm_struct *mm, unsigned long addr, ^ In file included from ./include/linux/scatterlist.h:8:0, from ./include/linux/dma-mapping.h:11, from ./include/linux/skbuff.h:34, from ./include/linux/if_ether.h:23, from ./include/uapi/linux/ethtool.h:19, from ./include/linux/ethtool.h:18, from ./include/linux/netdevice.h:41, from ./include/net/sock.h:51, from /var/lib/dkms/sysdig/0.1.87/build/main.c:38: ./include/linux/mm.h:1391:12: note: previous declaration of ‘__access_remote_vm’ was here extern int __access_remote_vm(struct task_struct *tsk, struct mm_struct *mm, ^ make[1]: *** [/var/lib/dkms/sysdig/0.1.87/build/main.o] Error 1 make: *** [_module_/var/lib/dkms/sysdig/0.1.87/build] Error 2 make: Leaving directory `/usr/src/linux-headers-4.15.0-1023-azure' ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.15.0-1023-azure 4.15.0-1023.24~14.04.1 ProcVersionSignature: User Name 4.15.0-1023.24~14.04.1-username 4.15.18 Uname: Linux 4.15.0-1023-azure x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Thu Oct 4 03:32:26 2018 SourcePackage: linux-signed-azure UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1796016/+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 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
Assuming comment #23 is correct... -- 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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Server console is extremely slow on ast, after the upgrade from 16.04 to 18.04. [Fix] Remove firmware/bootloader configured framebuffer device before probing. [Test] User confirmed the patch fixes the issue. [Regression Potential] Low. The fix is in stable tree, limits to one specific device, and other DRM drivers already do this for a while. ===Original Bug Report=== After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 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: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+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 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
The fix seems to have been released for both 18.04 and 18.10 already, a couple of weeks ago. I assume the fix was already in 19.04...? -- 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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Server console is extremely slow on ast, after the upgrade from 16.04 to 18.04. [Fix] Remove firmware/bootloader configured framebuffer device before probing. [Test] User confirmed the patch fixes the issue. [Regression Potential] Low. The fix is in stable tree, limits to one specific device, and other DRM drivers already do this for a while. ===Original Bug Report=== After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 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: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+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 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card
The system was upgrade from 16.04, did you see the same issue on Linux kernel v4.4? -- 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/1810416 Title: SD card error mmc0: error -110 whilst initialising SD card Status in linux package in Ubuntu: Confirmed Bug description: When inserting card to internal card reader: laurynas@laurynas-ThinkPad-T450:~$ dmesg [342809.333716] mmc0: error -110 whilst initialising SD card laurynas@laurynas-ThinkPad-T450:~$ uname -a Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux SanDisk Extreme 64GB UHS 3. Working fine on windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laurynas 3963 F pulseaudio /dev/snd/controlC0: laurynas 3963 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 16:09:26 2019 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4 InstallationDate: Installed on 2017-02-18 (683 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BUS3GN07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JBET68WW (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS3GN07 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS3GN07 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+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 1810892] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1810892 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810892 Title: lineout jack can't work on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The rear lineout jack can't work. If users plug a headphone or audio cable into the lineout jack, nothing happens, the audio still output from internal speaker. The expected behaviour is the lineout is active and the sound is routed to lineout jack from internal speaker. [Fix] apply the ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, this will set the lineout pin to be a correct configuration value. [Test Case] plug headphone into the rear lineout jack, system can detect lineout jack is plugged and the audio output is routed to lineout jack from internal speaker. [Regression Potential] Very low, this patch is specific to one Dell machine model. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810892/+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 1810892] Re: lineout jack can't work on a Dell machine
** Description changed: - - ODM has reported that the audio still outputs from the built-in - speakers when plugging in a headphone to the rear audio out jack. + + [Impact] + The rear lineout jack can't work. If users plug a headphone or audio + cable into the lineout jack, nothing happens, the audio still output + from internal speaker. The expected behaviour is the lineout is + active and the sound is routed to lineout jack from internal speaker. + + [Fix] + apply the ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, this will set the + lineout pin to be a correct configuration value. + + + [Test Case] + plug headphone into the rear lineout jack, system can detect lineout + jack is plugged and the audio output is routed to lineout jack from + internal speaker. + + + [Regression Potential] + Very low, this patch is specific to one Dell machine model. -- 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/1810892 Title: lineout jack can't work on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] The rear lineout jack can't work. If users plug a headphone or audio cable into the lineout jack, nothing happens, the audio still output from internal speaker. The expected behaviour is the lineout is active and the sound is routed to lineout jack from internal speaker. [Fix] apply the ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, this will set the lineout pin to be a correct configuration value. [Test Case] plug headphone into the rear lineout jack, system can detect lineout jack is plugged and the audio output is routed to lineout jack from internal speaker. [Regression Potential] Very low, this patch is specific to one Dell machine model. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810892/+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 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04
May i know when can we expect the official release for this 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/1808183 Title: ASPEED server console output extremely slow after upgrade to 18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Server console is extremely slow on ast, after the upgrade from 16.04 to 18.04. [Fix] Remove firmware/bootloader configured framebuffer device before probing. [Test] User confirmed the patch fixes the issue. [Regression Potential] Low. The fix is in stable tree, limits to one specific device, and other DRM drivers already do this for a while. ===Original Bug Report=== After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 15 07:22 seq crw-rw 1 root audio 116, 33 Dec 15 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 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: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: ASUSTeK COMPUTER INC. P9D-X Series Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9D-X Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: P9D-X Series dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808183/+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 1810892] [NEW] lineout jack can't work on a Dell machine
Public bug reported: - ODM has reported that the audio still outputs from the built-in speakers when plugging in a headphone to the rear audio out jack. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1809242 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1809242 somerville -- 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/1810892 Title: lineout jack can't work on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: - ODM has reported that the audio still outputs from the built-in speakers when plugging in a headphone to the rear audio out jack. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810892/+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 1810891] Re: audio output has constant noise on a Dell machine
** Description changed: - Steps to reproduce: - 1. Install manifest and boot into OS - 2. check internal speaker status - Expected result: - Internal speaker should not occurring noise + [Impact] + the audio output (headpohne, lineout and internal speaker) has constant + noise when playing sound. - Actual result: - Internal speaker keep occurring noise (GZM-DVT-C2) + [Fix] + Set the pin configuration and some secret coeff registers, the noise + disappears. This patch is written by Realtek engineer and is upstreamd + already. - Failure rate: 2/2 + + [Test Case] + play sound via internal speaker, lineout and headphone, no noise anymore. + + + [Regression Potential] + Very low, this patch is upstreamd for a while, no regression is reported. -- 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/1810891 Title: audio output has constant noise on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] the audio output (headpohne, lineout and internal speaker) has constant noise when playing sound. [Fix] Set the pin configuration and some secret coeff registers, the noise disappears. This patch is written by Realtek engineer and is upstreamd already. [Test Case] play sound via internal speaker, lineout and headphone, no noise anymore. [Regression Potential] Very low, this patch is upstreamd for a while, no regression is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810891/+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 1810891] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1810891 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810891 Title: audio output has constant noise on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] the audio output (headpohne, lineout and internal speaker) has constant noise when playing sound. [Fix] Set the pin configuration and some secret coeff registers, the noise disappears. This patch is written by Realtek engineer and is upstreamd already. [Test Case] play sound via internal speaker, lineout and headphone, no noise anymore. [Regression Potential] Very low, this patch is upstreamd for a while, no regression is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810891/+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 1810891] [NEW] audio output has constant noise on a Dell machine
Public bug reported: Steps to reproduce: 1. Install manifest and boot into OS 2. check internal speaker status Expected result: Internal speaker should not occurring noise Actual result: Internal speaker keep occurring noise (GZM-DVT-C2) Failure rate: 2/2 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1807098 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1807098 somerville ** Summary changed: - Internal speaker has constant noise on a Dell machine + audio output has constant noise on a Dell machine -- 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/1810891 Title: audio output has constant noise on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: Steps to reproduce: 1. Install manifest and boot into OS 2. check internal speaker status Expected result: Internal speaker should not occurring noise Actual result: Internal speaker keep occurring noise (GZM-DVT-C2) Failure rate: 2/2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810891/+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 1801490] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1801490/+attachment/5227533/+files/ProcEnviron.txt ** Description changed: F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS version,unable to control brightness level by pressing f3 key MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 4.18.0-041800rc6-generic, LLVM 6.0.0) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-11-07 (791 days ago) InstallationMedia: Package: linux (not installed) Tags: bionic Uname: Linux 4.18.0-041800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + CurrentDesktop: Unity:Unity7:ubuntu + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2016-11-07 (791 days ago) + InstallationMedia: + + Package: linux (not installed) + Tags: bionic + Uname: Linux 4.18.0-041800rc6-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) + UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video + _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801490 Title: Unable fix Brightness level directly by pressing F3 key Status in linux package in Ubuntu: Incomplete Bug description: F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS version,unable to control brightness level by pressing f3 key MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 4.18.0-041800rc6-generic, LLVM 6.0.0) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-11-07 (791 days ago) InstallationMedia: Package: linux (not installed) Tags: bionic Uname: Linux 4.18.0-041800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-11-07 (791 days ago) InstallationMedia: Package: linux (not installed) Tags: bionic Uname: Linux 4.18.0-041800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801490/+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 1801490] Re: Unable fix Brightness level directly by pressing F3 key
apport information ** Tags added: apport-collected bionic ** Description changed: F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS version,unable to control brightness level by pressing f3 key - MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / - 4.18.0-041800rc6-generic, LLVM 6.0.0) + MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 4.18.0-041800rc6-generic, LLVM 6.0.0) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + CurrentDesktop: Unity:Unity7:ubuntu + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2016-11-07 (791 days ago) + InstallationMedia: + + Package: linux (not installed) + Tags: bionic + Uname: Linux 4.18.0-041800rc6-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) + UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1801490/+attachment/5227532/+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/1801490 Title: Unable fix Brightness level directly by pressing F3 key Status in linux package in Ubuntu: Incomplete Bug description: F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS version,unable to control brightness level by pressing f3 key MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 4.18.0-041800rc6-generic, LLVM 6.0.0) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-11-07 (791 days ago) InstallationMedia: Package: linux (not installed) Tags: bionic Uname: Linux 4.18.0-041800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-11-07 (791 days ago) InstallationMedia: Package: linux (not installed) Tags: bionic Uname: Linux 4.18.0-041800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801490/+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 1801490] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1801490/+attachment/5227535/+files/ProcEnviron.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801490/+attachment/5227533/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801490/+attachment/5227532/+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/1801490 Title: Unable fix Brightness level directly by pressing F3 key Status in linux package in Ubuntu: Incomplete Bug description: F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS version,unable to control brightness level by pressing f3 key MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 4.18.0-041800rc6-generic, LLVM 6.0.0) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-11-07 (791 days ago) InstallationMedia: Package: linux (not installed) Tags: bionic Uname: Linux 4.18.0-041800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-11-07 (791 days ago) InstallationMedia: Package: linux (not installed) Tags: bionic Uname: Linux 4.18.0-041800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801490/+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 1801490] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1801490/+attachment/5227534/+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/1801490 Title: Unable fix Brightness level directly by pressing F3 key Status in linux package in Ubuntu: Incomplete Bug description: F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS version,unable to control brightness level by pressing f3 key MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 4.18.0-041800rc6-generic, LLVM 6.0.0) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-11-07 (791 days ago) InstallationMedia: Package: linux (not installed) Tags: bionic Uname: Linux 4.18.0-041800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-11-07 (791 days ago) InstallationMedia: Package: linux (not installed) Tags: bionic Uname: Linux 4.18.0-041800rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-11-08 (60 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin mythtv nopasswdlogin plugdev pulse pulse-access sambashare scanner sudo tape video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801490/+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 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
I've filed a bug report. (https://bugs.freedesktop.org/show_bug.cgi?id=109246) ** Bug watch added: freedesktop.org Bugzilla #109246 https://bugs.freedesktop.org/show_bug.cgi?id=109246 -- 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/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1786752] Re: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release)
Just to follow up , on behalf of Juergen. Do we have any progress with this bug ? -- 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/1786752 Title: Reference counter issue in 4.15 (nf_xfrm_me_harder / dst_release) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading from 14.04 to 18.04, we see very frequent warnings about negative refcnts in dst_release: [ 3117.882227] WARNING: CPU: 6 PID: 0 at /build/linux-I4R9hO/linux-4.15.0/include/net/dst.h:256 nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882229] Modules linked in: xt_policy cls_u32 sch_sfq ip_vti ip_tunnel authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key nfnetlink_queue nfnetlink_log sch_htb xt_TPROXY xt_multiport veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge overlay macvlan 8021q garp mrp stp llc bonding algif_skcipher af_alg xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_REJECT nf_reject_ipv6 xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 dm_crypt iptable_nat nf_nat_ipv4 xt_DSCP xt_dscp xt_mark iptable_mangle xt_limit xt_tcpudp xt_addrtype intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp nf_conntrack_ipv4 nf_defrag_ipv4 kvm_intel xt_conntrack kvm joydev input_leds ipt_REJECT nf_reject_ipv4 ftdi_sio usbserial ipmi_si [ 3117.882265] irqbypass intel_cstate mei_me mei ioatdma acpi_pad intel_rapl_perf shpchp ipmi_devintf ipmi_msghandler acpi_power_meter lpc_ich mac_hid ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp sch_fq_codel nf_conntrack iptable_filter ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 ttm crct10dif_pclmul igb ixgbe crc32_pclmul drm_kms_helper hid_generic ghash_clmulni_intel syscopyarea i2c_algo_bit dca sysfillrect usbhid pcbc sysimgblt fb_sys_fops aesni_intel aes_x86_64 crypto_simd ahci glue_helper ptp hid mxm_wmi cryptd [ 3117.882309] drm libahci megaraid_sas pps_core mdio wmi [ 3117.882315] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW 4.15.0-30-generic #32-Ubuntu [ 3117.882316] Hardware name: Intel Corporation S2600WT2R/S2600WT2R, BIOS SE5C610.86B.01.01.0022.062820171903 06/28/2017 [ 3117.882319] RIP: 0010:nf_xfrm_me_harder+0x127/0x140 [nf_nat] [ 3117.882320] RSP: 0018:88d77f3839f0 EFLAGS: 00010246 [ 3117.882322] RAX: RBX: 90de4000 RCX: 1924 [ 3117.882323] RDX: RSI: 88d749ae6400 RDI: 88d655e96600 [ 3117.882324] RBP: 88d77f383a68 R08: 88d7493dc000 R09: 0018 [ 3117.882324] R10: 0001 R11: 88e770dedc00 R12: 88d655e96600 [ 3117.882325] R13: 88d77f383ae8 R14: 88d7799ff200 R15: 88d7493dc000 [ 3117.882327] FS: () GS:88d77f38() knlGS: [ 3117.882327] CS: 0010 DS: ES: CR0: 80050033 [ 3117.882328] CR2: ff600400 CR3: 00193de0a002 CR4: 003606e0 [ 3117.882329] DR0: DR1: DR2: [ 3117.882330] DR3: DR6: fffe0ff0 DR7: 0400 [ 3117.882331] Call Trace: [ 3117.882332] [ 3117.882337] ? nf_nat_ipv4_fn+0x15b/0x200 [nf_nat_ipv4] [ 3117.882339] nf_nat_ipv4_out+0xc5/0xe0 [nf_nat_ipv4] [ 3117.882342] iptable_nat_ipv4_out+0x15/0x20 [iptable_nat] [ 3117.882347] nf_hook_slow+0x48/0xc0 [ 3117.882353] ip_output+0xd2/0xe0 [ 3117.882355] ? ip_fragment.constprop.44+0x80/0x80 [ 3117.882357] ip_forward_finish+0x49/0x70 [ 3117.882359] ip_forward+0x366/0x440 [ 3117.882361] ? ip_frag_mem+0x20/0x20 [ 3117.882362] ip_rcv_finish+0x129/0x430 [ 3117.882364] ip_rcv+0x28f/0x3a0 [ 3117.882366] ? inet_del_offload+0x40/0x40 [ 3117.882372] __netif_receive_skb_core+0x432/0xb40 [ 3117.882379] ? handle_edge_irq+0x7c/0x190 [ 3117.882384] ? irq_exit+0x67/0xc0 [ 3117.882391] ? do_IRQ+0x82/0xd0 [ 3117.882393] __netif_receive_skb+0x18/0x60 [ 3117.882395] ? __netif_receive_skb+0x18/0x60 [ 3117.882397] netif_receive_skb_internal+0x37/0xd0 [ 3117.882398] napi_gro_receive+0xc5/0xf0 [ 3117.882407] ixgbe_clean_rx_irq+0x446/0xe30 [ixgbe] [ 3117.882411] ixgbe_poll+0x256/0x710 [ixgbe] [ 3117.882413] ? do_IRQ+0x82/0xd0 [ 3117.882415] net_rx_action+0x140/0x3a0 [ 3117.882418] __do_softirq+0xdf/0x2b2 [ 3117.882419] irq_exit+0xb6/0xc0 [ 3117.882421] do_IRQ+0x82/0xd0 [ 3117.882423] common_interrupt+0x84/0x84 [ 3117.882424] [ 3117.882427] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [ 3117.882428] RSP:
[Kernel-packages] [Bug 1803921] Re: test_095_kernel_symbols_missing_proc_self_stack failed with C
https://git.launchpad.net/qa-regression- testing/commit/?id=beefdcab8432ae502c5ca6bf6094bfea53c077c0 ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: qa-regression-testing Status: Confirmed => Fix Released ** Changed in: qa-regression-testing Assignee: Po-Hsu Lin (cypressyew) => (unassigned) ** Changed in: ubuntu-kernel-tests Assignee: Po-Hsu Lin (cypressyew) => (unassigned) -- 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/1803921 Title: test_095_kernel_symbols_missing_proc_self_stack failed with C Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Like bug 1802069 With this patch applied: http://kernel.ubuntu.com/git/ubuntu/ubuntu-cosmic.git/commit/?h=master-next=601cf8d59f415403b50e6bfbf124b3f005b7e49b This test now failed with Cosmic kernel in proposed. Result before and after update ubuntu@rumford:~$ uname -a Linux rumford 4.18.0-11-generic #12-Ubuntu SMP Tue Oct 23 19:22:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@rumford:~$ cat /proc/self/stack [<0>] proc_pid_stack+0xaa/0x100 [<0>] proc_single_show+0x56/0x90 [<0>] seq_read+0x16b/0x450 [<0>] __vfs_read+0x1b/0x40 [<0>] vfs_read+0x8f/0x140 [<0>] ksys_read+0x55/0xc0 [<0>] __x64_sys_read+0x1a/0x20 [<0>] do_syscall_64+0x5a/0x110 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [<0>] 0x ubuntu@rumford:~$ uname -a Linux rumford 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@rumford:~$ cat /proc/self/stack cat: /proc/self/stack: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1803921/+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 1802421] Re: Xenial: data corruption when using i40e with iommu
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802421
Title:
Xenial: data corruption when using i40e with iommu
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Fix Committed
Bug description:
A user reports that using an i40e with intel_iommu=on with the Xenial
GA kernel causes data corruption. Using the Xenial HWE kernel or an
out-of-tree driver more recent than the version shipped with Xenial
solves the issue.
[Impact]
Corrupted data is returned from the network card intermittently. This is
often noticeable when using apt, as the checksums are verified. If often leads
to failure of apt operations. When there are no checksums done, this could lead
to silent data corruption.
[Fix]
This was fixed somewhere post-4.4. Testing identified b32bfa17246d ("i40e:
Drop packet split receive routine") which is part of a broader refactor.
Picking this patch alone is sufficient to fix the issue. My theory is that
iommu exposes an issue in the packet split receive routine and so removing it
is sufficient to prevent the problem from occurring.
[Test]
A user tested a Xenial 4.4 kernel with this patch applied and it fixed their
issue - no data corruption was observed. (The test repeatedly deletes the apt
cache and then does apt update.)
[Regression Potential]
It's a messy change inside i40e, so the risk is that i40e will be broken in
some subtle way we haven't noticed, or have performance issues. None of these
have been observed so far.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802421/+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 1772675] Re: Intel i40e PF reset due to incorrect MDD detection (continues...again...)
[Expired for linux (Ubuntu Cosmic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772675 Title: Intel i40e PF reset due to incorrect MDD detection (continues...again...) Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Bug description: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The fix for this is currently unknown. As the "MDD event" is generated by the i40e firmware, and is completely undocumented, there is no way to tell what the i40e driver did to cause the MDD event. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] unknown since the specific fix is unknown. [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+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 1772675] Re: Intel i40e PF reset due to incorrect MDD detection (continues...again...)
[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772675 Title: Intel i40e PF reset due to incorrect MDD detection (continues...again...) Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Bug description: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The fix for this is currently unknown. As the "MDD event" is generated by the i40e firmware, and is completely undocumented, there is no way to tell what the i40e driver did to cause the MDD event. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] unknown since the specific fix is unknown. [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+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 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800859 Title: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04) Status in linux package in Ubuntu: Expired Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID)
[Kernel-packages] [Bug 1800306] Re: Computer hangs completely passed 15~25 days of usage
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800306 Title: Computer hangs completely passed 15~25 days of usage Status in linux package in Ubuntu: Expired Bug description: Computer hangs every 3 weeks or so. It seems a graphics card problem but I changed by a new one, tried nvidia driver with the same behaviour too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-138-generic 4.4.0-138.164 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 27 16:20:18 2018 HibernationDevice: RESUME=/dev/mapper/LINUX--vg-swap_1 InstallationDate: Installed on 2017-11-02 (359 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: MSI MS-7885 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-138-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-138-generic N/A linux-backports-modules-4.4.0-138-generic N/A linux-firmware 1.157.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P.50 dmi.board.asset.tag: Default string dmi.board.name: X99A RAIDER (MS-7885) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP.50:bd07/19/2016:svnMSI:pnMS-7885:pvr5.0:rvnMSI:rnX99ARAIDER(MS-7885):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7885 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800306/+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 1772675] Re: Intel i40e PF reset due to incorrect MDD detection (continues...again...)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772675 Title: Intel i40e PF reset due to incorrect MDD detection (continues...again...) Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Bug description: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The fix for this is currently unknown. As the "MDD event" is generated by the i40e firmware, and is completely undocumented, there is no way to tell what the i40e driver did to cause the MDD event. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] unknown since the specific fix is unknown. [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+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 1772675] Re: Intel i40e PF reset due to incorrect MDD detection (continues...again...)
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772675 Title: Intel i40e PF reset due to incorrect MDD detection (continues...again...) Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Bug description: [impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the nic, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [fix] The fix for this is currently unknown. As the "MDD event" is generated by the i40e firmware, and is completely undocumented, there is no way to tell what the i40e driver did to cause the MDD event. [test case] the bug is unfortunately very difficult to reproduce, but as shown in this (and previous) bug comments, some users of the i40e have traffic that can consistently reproduce the problem (although usually on the order of days, or longer, to reproduce). Reproducing is easily detected, as the nw traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued [regression potential] unknown since the specific fix is unknown. [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+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 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound
Please run this command to send us more information about the system: apport-collect 1810861 ** Summary changed: - Speakers dont show or make audio + USB type C audio adapter (from a Pixel 3) doesn't produce any sound ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810861 Title: USB type C audio adapter (from a Pixel 3) doesn't produce any sound Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I use a logitech z200 that works fine, i use it with a usb type c adapter that came with my pixel 3, my speakers arent shown at all in the settings or make sound, its not the usb c adapter because it works fine on my windows dual boot and has worked at one point on ubuntu, regardless of the fact that ubuntu has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i use lsusb, one of the results is google inc., which is my headphone adapter, i can tell because when i unplug it it goes away, even when i plug it into the 3.5 mm headphone jack it doesn't work, i don't know if im forgetting something or not, this is the second time im typing this because i accidentally closed the first tab of this, whats interesting, is now that i go to alsamixer, and press f6 i see option 1.Headphone Adapter, i select it and set the volume all the way up and go to something that makes audio and nothing happens, then i unplug it and see if it disappears, surely enough it does To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1810861] [NEW] USB type C audio adapter (from a Pixel 3) doesn't produce any sound
You have been subscribed to a public bug: I use a logitech z200 that works fine, i use it with a usb type c adapter that came with my pixel 3, my speakers arent shown at all in the settings or make sound, its not the usb c adapter because it works fine on my windows dual boot and has worked at one point on ubuntu, regardless of the fact that ubuntu has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i use lsusb, one of the results is google inc., which is my headphone adapter, i can tell because when i unplug it it goes away, even when i plug it into the 3.5 mm headphone jack it doesn't work, i don't know if im forgetting something or not, this is the second time im typing this because i accidentally closed the first tab of this, whats interesting, is now that i go to alsamixer, and press f6 i see option 1.Headphone Adapter, i select it and set the volume all the way up and go to something that makes audio and nothing happens, then i unplug it and see if it disappears, surely enough it does ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- USB type C audio adapter (from a Pixel 3) doesn't produce any sound https://bugs.launchpad.net/bugs/1810861 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 1810097] Re: HDMI is not recognized
Thanks. This means the kernel can't detect anything plugged into HDMI: /sys/class/drm/card0-HDMI-A-1/enabled:disabled So if not a kernel bug then most likely the cable isn't plugged in properly, or the cable needs replacing. Please try a different HDMI cable. ** Package changed: xorg-server (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/1810097 Title: HDMI is not recognized Status in linux package in Ubuntu: Incomplete Bug description: Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00*+ 1680x1050 59.95 1280x1024 75.0260.02 1440x900 59.89 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 72.1975.0060.3256.25 640x480 75.0072.8159.94 720x400 70.08 HDMI-1 disconnected (normal left inverted right x axis y axis) with friendly greetings from Germany Heinz Köhler ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Dec 30 17:27:38 2018 DistUpgraded: 2018-08-21 18:00:51,886 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2014-12-09 (1482 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=79c3b9e1-5aa7-47b0-8673-5fc4a350c917 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-21 (131 days ago) dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Aug 21 14:19:34 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810097/+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 1810097] [NEW] HDMI is not recognized
You have been subscribed to a public bug: Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00*+ 1680x1050 59.95 1280x1024 75.0260.02 1440x900 59.89 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 72.1975.0060.3256.25 640x480 75.0072.8159.94 720x400 70.08 HDMI-1 disconnected (normal left inverted right x axis y axis) with friendly greetings from Germany Heinz Köhler ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Dec 30 17:27:38 2018 DistUpgraded: 2018-08-21 18:00:51,886 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2014-12-09 (1482 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=79c3b9e1-5aa7-47b0-8673-5fc4a350c917 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-21 (131 days ago) dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Aug 21 14:19:34 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic ubuntu -- HDMI is not recognized https://bugs.launchpad.net/bugs/1810097 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 1809783] Re: Bluetooth always on when power on my laptop
Also, disabling bluetooth seems to be done entirely at the rfkill/systemd/kernel level. BlueZ is not involved, and bluetoothd stays active regardless. bluetoothd just loses access to the hardware when it's disabled. ** Package changed: bluez (Ubuntu) => ubuntu -- 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/1809783 Title: Bluetooth always on when power on my laptop Status in Ubuntu: Incomplete Bug description: Bluetooth works properly but it's always turned on on startup and I have to turn it off manually ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 26 09:16:08 2018 InstallationDate: Installed on 2018-12-07 (18 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE C50-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=656a2282-422f-4307-9893-2ec8c68718dc ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.10 dmi.board.asset.tag: * dmi.board.name: ZBWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.10:bd08/10/2015:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-02N01VIT:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.version: PSCMLE-02N01VIT dmi.sys.vendor: TOSHIBA hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809783/+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 1809783] Re: Bluetooth always on when power on my laptop
It appears the state is stored by rfkill, in: /var/lib/systemd/rfkill/* Maybe Budgie isn't setting it (indirectly) properly... John, can you please run this command and send us the output (after disabling Bluetooth)? grep . /var/lib/systemd/rfkill/* Also, what is the name of the tool you are using in Budgie to disable Bluetooth? ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1809783 Title: Bluetooth always on when power on my laptop Status in Ubuntu: Incomplete Bug description: Bluetooth works properly but it's always turned on on startup and I have to turn it off manually ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 26 09:16:08 2018 InstallationDate: Installed on 2018-12-07 (18 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE C50-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=656a2282-422f-4307-9893-2ec8c68718dc ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.10 dmi.board.asset.tag: * dmi.board.name: ZBWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.10:bd08/10/2015:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-02N01VIT:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.version: PSCMLE-02N01VIT dmi.sys.vendor: TOSHIBA hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809783/+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 1809783] Re: Bluetooth always on when power on my laptop
I'm not sure what you mean by init scripts. Init scripts have long been replaced by systemd. -- 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/1809783 Title: Bluetooth always on when power on my laptop Status in bluez package in Ubuntu: New Bug description: Bluetooth works properly but it's always turned on on startup and I have to turn it off manually ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 26 09:16:08 2018 InstallationDate: Installed on 2018-12-07 (18 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE C50-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=656a2282-422f-4307-9893-2ec8c68718dc ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.10 dmi.board.asset.tag: * dmi.board.name: ZBWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.10:bd08/10/2015:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-02N01VIT:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.version: PSCMLE-02N01VIT dmi.sys.vendor: TOSHIBA hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1809783/+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 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
Please file an upstream bug at https://bugs.freedesktop.org/ Product: DRI Component: DRM/amdgpu -- 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/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861/+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 1794836] Re: Update from 16.04 to 18.04 and serious screen lagging problems
That's because "nomodeset" is in your kernel parameter. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794836 Title: Update from 16.04 to 18.04 and serious screen lagging problems Status in linux package in Ubuntu: Confirmed Bug description: I have upgraded from Ubuntu 16.04 to ubuntu 18.04, and the refreshing of the screen in browsers, videos, etc... is really annoying. I would like to solve this problem since this is provoking me constant headache --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: julia 3959 F...m pulseaudio /dev/snd/pcmC1D0p: julia 3959 F...m pulseaudio /dev/snd/controlC1: julia 3959 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=3bf717b5-f3c2-45da-9ec8-5926c846f3ea InstallationDate: Installed on 2014-09-30 (1458 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Gigabyte Technology Co., Ltd. H81M-D2V Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=34beca2c-8810-4dea-81c4-ea789864bd2f ro nomodeset quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd06/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D2V dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794836/+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 1810430] Re: tpm_crb MSFT0101:00: can't request region for resource
Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1394912 ** Bug watch added: Red Hat Bugzilla #1394912 https://bugzilla.redhat.com/show_bug.cgi?id=1394912 -- 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/1810430 Title: tpm_crb MSFT0101:00: can't request region for resource Status in linux package in Ubuntu: Confirmed Bug description: New hardware (AMD Threadripper 2920x with an ASRock X399 Taichi motherboard) and a clean 18.04.1 install. I purposefully turn on AMD fTPM in the UEFI as I would like to explore using this to secure my system. However after booting with this option no /dev/tpm device node exists and the kernel boot output now includes the following... $ dmesg | grep -i tpm [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I 0001 AMI ) [0.928120] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7943a000-0x7943afff] [0.928141] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.090180] ima: No TPM chip found, activating TPM-bypass! (rc=-19) I'm using the motherboard vendors latest issued UEFI firmware and am unable to locate any other examples of this issue on my hardware. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kelvin 3554 F pulseaudio /dev/snd/controlC0: kelvin 3554 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 17:11:03 2019 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=dc67630f-0924-11e9-b9f2-7085c2b1c052 ro amd_iommu=force_isolation iommu=pt transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X399 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399Taichi:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810430/+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 1810872] 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/1810872 Title: Touchpad and wifi don't Status in linux package in Ubuntu: Confirmed Bug description: I can't use my touchpad at all and the wifi doesn't work. I tried a lot of tutorials but any of them work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patricio 1561 F pulseaudio /dev/snd/controlC0: patricio 1561 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 7 22:28:14 2019 InstallationDate: Installed on 2019-01-05 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp1s0no wireless extensions. lono wireless extensions. MachineType: TOSHIBA Satellite L45D-C ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=4224aaec-f1b1-49b5-ba77-b3fdf73c1608 ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.00 dmi.board.asset.tag: * dmi.board.name: ACWAE dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.00:bd08/12/2015:svnTOSHIBA:pnSatelliteL45D-C:pvrPSKYNU-006NC1:rvnTOSHIBA:rnACWAE:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: Satellite L45D-C dmi.product.version: PSKYNU-006NC1 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810872/+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 1654448] Re: Dell XPS 13 9350, 9360 and 9370 headphone audio hiss
Not myself, no. That was just to cover duplicate bug 1809856. If that's incorrect, feel free to remove it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: Dell XPS 13 9350, 9360 and 9370 headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1810872] [NEW] Touchpad and wifi don't
Public bug reported: I can't use my touchpad at all and the wifi doesn't work. I tried a lot of tutorials but any of them work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patricio 1561 F pulseaudio /dev/snd/controlC0: patricio 1561 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 7 22:28:14 2019 InstallationDate: Installed on 2019-01-05 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp1s0no wireless extensions. lono wireless extensions. MachineType: TOSHIBA Satellite L45D-C ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=4224aaec-f1b1-49b5-ba77-b3fdf73c1608 ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.00 dmi.board.asset.tag: * dmi.board.name: ACWAE dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.00:bd08/12/2015:svnTOSHIBA:pnSatelliteL45D-C:pvrPSKYNU-006NC1:rvnTOSHIBA:rnACWAE:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: Satellite L45D-C dmi.product.version: PSKYNU-006NC1 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810872 Title: Touchpad and wifi don't Status in linux package in Ubuntu: New Bug description: I can't use my touchpad at all and the wifi doesn't work. I tried a lot of tutorials but any of them work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patricio 1561 F pulseaudio /dev/snd/controlC0: patricio 1561 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 7 22:28:14 2019 InstallationDate: Installed on 2019-01-05 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp1s0no wireless extensions. lono wireless extensions. MachineType: TOSHIBA Satellite L45D-C ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=4224aaec-f1b1-49b5-ba77-b3fdf73c1608 ro i8042.reset quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.00 dmi.board.asset.tag: * dmi.board.name: ACWAE dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.00:bd08/12/2015:svnTOSHIBA:pnSatelliteL45D-C:pvrPSKYNU-006NC1:rvnTOSHIBA:rnACWAE:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: Satellite L45D-C dmi.product.version: PSKYNU-006NC1 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810872/+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 124406] Re: Keyboard keys get stuck and repeat
wow! see this was opened in 2007. just googled this from the future (i am in 2018) and found this. using ubuntu 18. found that what was causing it in my case was a clipboard manager i use here. closing the clipboard manager stopped the bleeding. -- 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/124406 Title: Keyboard keys get stuck and repeat Status in GNU Emacs: Invalid Status in Linux: Confirmed Status in X.Org X server: In Progress Status in linux package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Status in linux source package in Jaunty: Won't Fix Status in xorg-server source package in Jaunty: Invalid Status in Gentoo Linux: New Bug description: Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often get 'stuck' and continue being 'clicked' even after they are physically released. For example when clicking Alt-F4, sometimes it gets stuck so all the windows are closed instead of just one. My configuration is Feisty + Xgl + Compiz Fusion. My previous configuration was Edgy + Xgl + Beryl, where this didn't happen. Others have reported the same problem without using either Xgl or Compiz. The keyboard itself isn't the problem. When dual-booting to Windows, everything works fine. Also, the problem happens with two different keyboards (internal laptop, external USB). My best guess is that the problem occurs at time of high system load. Somehow during these times the key-release signal gets lost and the key-press is repeated indefinitely. This happens more often with Compiz configurations because Compiz tends to increase system load. It also happens more often with power-hungry apps like Firefox and Acrobat Reader for similar reasons. PS: When the keys would repeat all input devices would be locked up. ie. mouse won't move, clicks don't do anything, keyboard presses don't register. Then when it becomes unstuck, the mouse moves around and everything. Hope this helps. See also this forum thread for other people with the same problem: http://ubuntuforums.org/showthread.php?t=432057 To manage notifications about this bug go to: https://bugs.launchpad.net/emacs/+bug/124406/+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 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
I've since tested Linux v5.0-rc1 (https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.0-rc1/) and the issue still hasn't been fixed. -- 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/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1810702] Re: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810702 Title: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU Status in linux package in Ubuntu: Fix Committed Bug description: For HP Inc. mobile workstation with hybrid graphics support, dGPU can directly output to external monitors; however, Nvidia and AMD's Linux drivers aren't able to support this feature. The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement dGPU direct output to external monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810702/+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 1810781] Re: mpt3sas - driver using the wrong register to update a queue index in FW
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810781 Title: mpt3sas - driver using the wrong register to update a queue index in FW Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] * Adapter resets periodically during high-load activity. * I/O stalls until reset/reinit is complete (latency) and I/O performance degrades across cluster (e.g., low throughput from data spread over nodes). * The mpt3sas driver relies in a FW queue (Reply Post Descriptor Queue) in the I/O completion path; there's a MMIO register that driver uses to flag an empty entry in such queue, called Reply Post Host Index. This value is updated during the driver interrupt routine [in _base_interrupt() function]. * Happens that there are 2 registers representing the Reply Post Host Index according to the type of the adapter. They are differentiated in the driver through the "ioc->combined_reply_queue" check. By the MPI specification (vendor spec), driver should use this combined reply queue according to the number of maximum MSI-X vectors that the adapter exposes and the spec version (SAS 3.0 vs SAS 3.5). * Currently, this is wrong checked for a class of adapters, which was fixed in the upstream kernel commit 2b48be65685a [0]. Without this commit, we can observe spontaneous resets in the driver due to queue overflow (FW is not aware that there are free entries in the Reply Post Descriptor Queue). The dmesg log will show the following output in case of this error: mpt3sas_cm0: fault_state(0x2100)! mpt3sas_cm0: sending diag reset !! mpt3sas_cm0: diag reset: SUCCESS [followed by a lot of driver messages as result of the reset procedure] * During these resets, I/O is stalled so it may affect performance. [Test Case] * It's not trivial to test the problem, but given a machine with an affected device, an I/O benchmark like FIO could be used to exercise the I/O path in a heavy way and trigger the issue. * We have reports that the adapter "LSI Logic / Symbios Logic Device [1000:00ac]" is affected by the issue. And this commit resolved the problem. [Regression Potential] * This is a long-term issue from the mpt3sas driver, affecting only a class of adapters of this vendor. Since it's a clearly bug, the fix is necessary. The potential of regressions is unknown, but likely low - it changes the register used for the index updates given some set of characteristics of the adapter (according to the spec.), which restricts even more the scope of this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810781/+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 1801490] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1801490 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801490 Title: Unable fix Brightness level directly by pressing F3 key Status in linux package in Ubuntu: Incomplete Bug description: F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS version,unable to control brightness level by pressing f3 key MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 4.18.0-041800rc6-generic, LLVM 6.0.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801490/+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 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors
I'm using an RX 480 and also have the same problem on kernels 4.18 and 4.20 (tested using 4.20.0-042000 from https://kernel.ubuntu.com/~kernel- ppa/mainline/v4.20/). Adding "amdgpu.dc=0" to GRUB fixes the problem in both cases. -- 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/1790861 Title: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens: 1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep 2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all 3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again 4) step 1 all over again in an infinite loop When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other. After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep. My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action. Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic. Nothing worked. In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround. I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic. ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 30' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104385b0,00100302' Controls : 50 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e6 irq 31' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100700' Controls : 42 Simple ctrls : 6 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2 InstallationDate: Installed on 2018-09-01 (3 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.17.0-9-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1801490] Re: Unable fix Brightness level directly by pressing F3 key
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801490 Title: Unable fix Brightness level directly by pressing F3 key Status in linux package in Ubuntu: New Bug description: F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS version,unable to control brightness level by pressing f3 key MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 4.18.0-041800rc6-generic, LLVM 6.0.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801490/+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 1801490] [NEW] Unable fix Brightness level directly by pressing F3 key
You have been subscribed to a public bug: F3 key is not working for brightness control on my UBUNTU 18.04.1 LTS version,unable to control brightness level by pressing f3 key MY GRAPHICS INFORMATION AS FOLLOWS- AMD MULLINS (DRM 2.50.0 / 4.18.0-041800rc6-generic, LLVM 6.0.0) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Unable fix Brightness level directly by pressing F3 key https://bugs.launchpad.net/bugs/1801490 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 1797296] Re: nouveau lockup
Jan 7 02:41:41 ceo1homenx kernel: [40698.439354] WARNING: CPU: 6 PID: 24218 at drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau] Jan 7 02:41:41 ceo1homenx kernel: [40698.439355] Modules linked in: vfio_pci vfio_virqfd vfio_iommu_type1 vfio rfcomm ebtable_filter ebtables ip6table_filter devlink ip6_tables iptable_filter bpfilter cmac bnep bridge stp llc dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm wmi_bmof dell_smbios dell_wmi_descriptor irqbypass uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common crct10dif_pclmul crc32_pclmul videodev ghash_clmulni_intel pcbc media joydev aesni_intel dcdbas snd_hda_codec_hdmi input_leds snd_hda_codec_realtek snd_hda_codec_generic aes_x86_64 nouveau snd_usb_audio snd_hda_intel snd_usbmidi_lib snd_hda_codec crypto_simd cryptd snd_hda_core snd_hwdep glue_helper snd_pcm i915 snd_seq_midi snd_seq_midi_event intel_cstate intel_rapl_perf snd_rawmidi mxm_wmi ttm Jan 7 02:41:41 ceo1homenx kernel: [40698.439378] snd_seq 8250_dw btusb btrtl btbcm btintel bluetooth ecdh_generic drm_kms_helper snd_seq_device snd_timer snd idma64 soundcore drm i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt mac_hid virt_dma mei_me mei video wmi acpi_pad sch_fq_codel parport_pc ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx ahci i2c_i801 intel_lpss_pci mdio libahci intel_lpss pinctrl_sunrisepoint pinctrl_intel Jan 7 02:41:41 ceo1homenx kernel: [40698.439399] CPU: 6 PID: 24218 Comm: kworker/6:1 Tainted: GW 4.18.0-13-generic #14-Ubuntu Jan 7 02:41:41 ceo1homenx kernel: [40698.439400] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018 Jan 7 02:41:41 ceo1homenx kernel: [40698.439423] Workqueue: events nouveau_cli_work [nouveau] Jan 7 02:41:41 ceo1homenx kernel: [40698.439436] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau] Jan 7 02:41:41 ceo1homenx kernel: [40698.439436] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 7a a9 b7 f9 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 Jan 7 02:41:41 ceo1homenx kernel: [40698.439454] RSP: 0018:b8f8486ffdb8 EFLAGS: 00010282 Jan 7 02:41:41 ceo1homenx kernel: [40698.439455] RAX: fffe RBX: b8f8486ffde8 RCX: Jan 7 02:41:41 ceo1homenx kernel: [40698.439455] RDX: 0010 RSI: b8f8486ffd28 RDI: b8f8486ffdc8 Jan 7 02:41:41 ceo1homenx kernel: [40698.439456] RBP: b8f8486ffdd8 R08: c0970b40 R09: Jan 7 02:41:41 ceo1homenx kernel: [40698.439456] R10: 8af646b1d300 R11: 0030 R12: b8f8486ffe20 Jan 7 02:41:41 ceo1homenx kernel: [40698.439457] R13: dead0200 R14: dead0100 R15: 8af646b1dde0 Jan 7 02:41:41 ceo1homenx kernel: [40698.439458] FS: () GS:8af73ed8() knlGS: Jan 7 02:41:41 ceo1homenx kernel: [40698.439459] CS: 0010 DS: ES: CR0: 80050033 Jan 7 02:41:41 ceo1homenx kernel: [40698.439459] CR2: 7f2b0f778004 CR3: 0002d040a001 CR4: 003626e0 Jan 7 02:41:41 ceo1homenx kernel: [40698.439460] DR0: DR1: DR2: Jan 7 02:41:41 ceo1homenx kernel: [40698.439460] DR3: DR6: fffe0ff0 DR7: 0400 Jan 7 02:41:41 ceo1homenx kernel: [40698.439461] Call Trace: Jan 7 02:41:41 ceo1homenx kernel: [40698.439483] nouveau_vma_del+0x75/0xc0 [nouveau] Jan 7 02:41:41 ceo1homenx kernel: [40698.439504] nouveau_gem_object_delete_work+0x3a/0x60 [nouveau] Jan 7 02:41:41 ceo1homenx kernel: [40698.439524] nouveau_cli_work+0xc3/0x100 [nouveau] Jan 7 02:41:41 ceo1homenx kernel: [40698.439526] ? __schedule+0x2a6/0x840 Jan 7 02:41:41 ceo1homenx kernel: [40698.439528] process_one_work+0x20f/0x3c0 Jan 7 02:41:41 ceo1homenx kernel: [40698.439530] worker_thread+0x34/0x400 Jan 7 02:41:41 ceo1homenx kernel: [40698.439531] kthread+0x120/0x140 Jan 7 02:41:41 ceo1homenx kernel: [40698.439533] ? pwq_unbound_release_workfn+0xd0/0xd0 Jan 7 02:41:41 ceo1homenx kernel: [40698.439534] ? kthread_bind+0x40/0x40 Jan 7 02:41:41 ceo1homenx kernel: [40698.439535] ret_from_fork+0x35/0x40 Jan 7 02:41:41 ceo1homenx kernel: [40698.439536] ---[ end trace 4a36f9e4d35c3e8b ]--- -- 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/1797296 Title: nouveau lockup Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: Oct 10 11:38:30 sun kernel: [17891.545097] nouveau :03:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Oct 10 11:38:30 sun kernel: [17891.545109] nouveau :03:00.0: fifo: runlist 0: scheduled
[Kernel-packages] [Bug 1797296] Re: nouveau lockup
an 7 06:39:01 ceo1homenx CRON[29352]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi) Jan 7 06:47:12 ceo1homenx kernel: [55429.029596] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Jan 7 06:47:12 ceo1homenx kernel: [55429.029607] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery Jan 7 06:47:12 ceo1homenx kernel: [55429.029615] nouveau :01:00.0: fifo: channel 12: killed Jan 7 06:47:12 ceo1homenx kernel: [55429.029622] nouveau :01:00.0: fifo: engine 0: scheduled for recovery Jan 7 06:47:12 ceo1homenx kernel: [55429.029951] nouveau :01:00.0: Xorg[1901]: channel 12 killed! Jan 7 06:47:37 ceo1homenx libvirtd[1522]: 2019-01-07 12:47:37.719+: 1522: error : virKeepAliveTimerInternal:140 : internal error: connection closed due to keepalive timeo ut Jan 7 06:49:46 ceo1homenx kernel: [55582.936599] INFO: task kworker/u16:12:28366 blocked for more than 120 seconds. Jan 7 06:49:46 ceo1homenx kernel: [55582.936602] Tainted: GW 4.18.0-13-generic #14-Ubuntu Jan 7 06:49:46 ceo1homenx kernel: [55582.936603] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 7 06:49:46 ceo1homenx kernel: [55582.936604] kworker/u16:12 D0 28366 2 0x8000 Jan 7 06:49:46 ceo1homenx kernel: [55582.936636] Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Jan 7 06:49:46 ceo1homenx kernel: [55582.936637] Call Trace: Jan 7 06:49:46 ceo1homenx kernel: [55582.936642] __schedule+0x29e/0x840 Jan 7 06:49:46 ceo1homenx kernel: [55582.936644] schedule+0x2c/0x80 Jan 7 06:49:46 ceo1homenx kernel: [55582.936646] schedule_timeout+0x258/0x360 Jan 7 06:49:46 ceo1homenx kernel: [55582.936674] ? nv50_wndw_atomic_destroy_state+0x1d/0x20 [nouveau] Jan 7 06:49:46 ceo1homenx kernel: [55582.936676] dma_fence_default_wait+0x1fc/0x260 Jan 7 06:49:46 ceo1homenx kernel: [55582.936678] ? dma_fence_release+0xa0/0xa0 Jan 7 06:49:46 ceo1homenx kernel: [55582.936679] dma_fence_wait_timeout+0x3e/0xf0 Jan 7 06:49:46 ceo1homenx kernel: [55582.936685] drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper] Jan 7 06:49:46 ceo1homenx kernel: [55582.936704] nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau] Jan 7 06:49:46 ceo1homenx kernel: [55582.936705] ? __switch_to_asm+0x40/0x70 Jan 7 06:49:46 ceo1homenx kernel: [55582.936706] ? __switch_to_asm+0x34/0x70 Jan 7 06:49:46 ceo1homenx kernel: [55582.936725] nv50_disp_atomic_commit_work+0x12/0x20 [nouveau] Jan 7 06:49:46 ceo1homenx kernel: [55582.936727] process_one_work+0x20f/0x3c0 Jan 7 06:49:46 ceo1homenx kernel: [55582.936728] worker_thread+0x34/0x400 Jan 7 06:49:46 ceo1homenx kernel: [55582.936730] kthread+0x120/0x140 Jan 7 06:49:46 ceo1homenx kernel: [55582.936731] ? pwq_unbound_release_workfn+0xd0/0xd0 Jan 7 06:49:46 ceo1homenx kernel: [55582.936732] ? kthread_bind+0x40/0x40 Jan 7 06:49:46 ceo1homenx kernel: [55582.936733] ret_from_fork+0x35/0x40 Jan 7 06:49:46 ceo1homenx kernel: [55582.936736] INFO: task kworker/u16:1:28944 blocked for more than 120 seconds. Jan 7 06:49:46 ceo1homenx kernel: [55582.936737] Tainted: GW 4.18.0-13-generic #14-Ubuntu Jan 7 06:49:46 ceo1homenx kernel: [55582.936738] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 7 06:49:46 ceo1homenx kernel: [55582.936739] kworker/u16:1 D0 28944 2 0x8000 Jan 7 06:49:46 ceo1homenx kernel: [55582.936758] Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau] Jan 7 06:49:46 ceo1homenx kernel: [55582.936758] Call Trace: Jan 7 06:49:46 ceo1homenx kernel: [55582.936760] __schedule+0x29e/0x840 Jan 7 06:49:46 ceo1homenx kernel: [55582.936761] schedule+0x2c/0x80 Jan 7 06:49:46 ceo1homenx kernel: [55582.936763] schedule_timeout+0x258/0x360 Jan 7 06:49:46 ceo1homenx kernel: [55582.936780] ? nv50_wndw_atomic_destroy_state+0x1d/0x20 [nouveau] Jan 7 06:49:46 ceo1homenx kernel: [55582.936782] dma_fence_default_wait+0x1fc/0x260 Jan 7 06:49:46 ceo1homenx kernel: [55582.936783] ? dma_fence_release+0xa0/0xa0 Jan 7 06:49:46 ceo1homenx kernel: [55582.936785] dma_fence_wait_timeout+0x3e/0xf0 Jan 7 06:49:46 ceo1homenx kernel: [55582.936789] drm_atomic_helper_wait_for_fences+0x3f/0xc0 [drm_kms_helper] Jan 7 06:49:46 ceo1homenx kernel: [55582.936807] nv50_disp_atomic_commit_tail+0x78/0x860 [nouveau] Jan 7 06:49:46 ceo1homenx kernel: [55582.936807] ? __switch_to_asm+0x40/0x70 Jan 7 06:49:46 ceo1homenx kernel: [55582.936808] ? __switch_to_asm+0x34/0x70 Jan 7 06:49:46 ceo1homenx kernel: [55582.936826] nv50_disp_atomic_commit_work+0x12/0x20 [nouveau] Jan 7 06:49:46 ceo1homenx kernel: [55582.936827] process_one_work+0x20f/0x3c0 Jan 7 06:49:46 ceo1homenx kernel: [55582.936829] worker_thread+0x34/0x400 Jan 7 06:49:46 ceo1homenx kernel: [55582.936830] kthread+0x120/0x140 Jan 7 06:49:46 ceo1homenx kernel:
[Kernel-packages] [Bug 1802691] Re: Slow send speed with Intel I219-V on Ubuntu 18.04.1
I also encountered network performance degradation on my server, however I'm not running Ubuntu but Debian with a self-compiled kernel. With bisecting the kernel, I could track this issue down to this commit between 4.14.2 and 4.14.3: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0f478f25d50cb6464678284a13f514fefc16e271 I was tempted to undo this change in my kernel, however this change works around a bug in the I219 adapter and I didn't want to end up with an unstable system. Related to this bug I read about TCP segmentation offload and changed tso and gso values with ethtool. Eventually "ethtool -K enp0s31f6 tso" off did the trick for me and network performance is back to normal. You might have to change the name of enp0s31f6 to the name of your Ethernet adapter or play with on/off values for tso and gso. In order to persist this setting after a reboot, I created a udev rule that calls ethtool, maybe this option works for you as well. -- 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/1802691 Title: Slow send speed with Intel I219-V on Ubuntu 18.04.1 Status in linux package in Ubuntu: Confirmed Bug description: Testing with iperf3 send speed is only 750mbps while receive speed is normal - 940mbps. Ubuntu 18.04.1 Msi b250m mortar --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: django 1016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-09 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A69 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: B250M MORTAR ARCTIC (MS-7A69) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A69 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802691/+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 1810457] Re: Update hisilicon SoC-specific drivers
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810457 Title: Update hisilicon SoC-specific drivers Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: In Progress Bug description: [Impact] Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream periodically. [Test Case] [Fix] Various upstream patches. [Regression Risk] The number of changes here obviously comes with regression risk. However, these drivers are only used for two HiSilicon SoCs and their corresponding development platforms - D05 and D06. We are therefore able to mitigate the risk by directly testing these changes on the impacted devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457/+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 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
perhaps i spoke to soon - even with the kernel changes i'm able to reproduce the squeaky-voice issue. i've also tried creating ~/.pulse/daemon.conf with default-sample-rate = 16000 which does not fix 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/843431 Title: Logitech camera microphone does not work / makes "chipmunk" sound Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Status in linux package in Debian: New Bug description: Did not know which application to log so feel free to let me know and I'll upload the correct log. In Natty, this mic worked great. Now, in the sound control panel, the mic does not show any input level at all and sound recorder does not record any sound. edit: I can also confirm the same behavior as Alex Popovskiy. It either works but plays too fast (high pitch) or it doesn't work at all. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Sep 6 20:31:13 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1594 F pulseaudio /dev/snd/controlC0: alex 1594 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xf9ef4000 irq 16' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,18490397,0010' Controls : 36 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-:00:13.2-6, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0809' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6400 Mono: Capture 6400 [100%] [31.00dB] [on] DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=8ccfea11-7ba8-42e2-bc75-a37e20a8c83c InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=3c8a3aec-07c0-47ad-bab8-0365abb68a42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 RelatedPackageVersions: linux-restricted-modules-3.0.0-10-generic N/A linux-backports-modules-3.0.0-10-generic N/A linux-firmware1.60 Tags: oneiric running-unity Uname: Linux 3.0.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/07/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: M3A770DE 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.:bvrP1.70:bd09/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A770DE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/843431/+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 1810636] Re: Suspect QCA6174 btcoex | Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570 [Pending PulseAudio testing]
It might be worth saying, however, without the pulseaudio-modules-bt in [2] in comment #27, the throughput of the WLAN was not affected when playing sound via the A2DP sync and I was seeing abotu 18 MB/s. Maybe I'm a bit premature in saying it's solely a pulseaudio-modules-bt issue. Regardless, it seems to be working a lot better with LDAC. -- 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/1810636 Title: Suspect QCA6174 btcoex | Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570 [Pending PulseAudio testing] Status in linux package in Ubuntu: Confirmed Bug description: I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570 with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness ever since I have owned this laptop. This problem has persisted for me with previous kernels. If I disable wifi and use media on machine locally, the problem doesn't occur. Note: I've reverted back v4.18.0-13-generic and reproduced the problem for the apport-collect report. It started with Ubuntu 18.04 and continues with 18.10. It's particularly noticeable when the when saturating the WLAN connection with throughput, i.e. copying a large file sequentially across from a samba share, but also streaming video online results in the audio progressively delaying over-time. Re-establishing the Bluetooth audio sync restores the sync, but slowly creeps out again. I've upgraded my linux-firmware package to disco 176 to match v4.20 kernel drivers ref: https://launchpad.net/ubuntu/+source/linux- firmware/1.176 The ath10k_core driver that supports this device has a reference for btcoex: ref https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598 It's possible that the Bluetooth component firmware is not supporting or communicating btcoex compatibility, but this is starting to reach the edge of my ability to diagnose the problem. This btcoex support in ath9k has resolved/improved the Bluetooth bandwidth problem for older Qualcomm chipsets as shown in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164 As a troubleshooting step, I've also tried the very latest firmware-6 file from, but I'm continuing to experience the problem ref: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berg 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-07-02 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c825a7b0-a5ac-41de-bd57-7663fef8a1f1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.176 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (79 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07GHH0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810636/+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 1810636] Re: QCA6174 doesn't utilise btcoex - Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570
Ok, I'm pretty sure this is a pulseaudio issue now and I'm going to close. I reverted back to linux-firmware 1.176, and I had also used undervolt [1] to help reduce thermal load on the Core i9 Dell XPS 15 which has suffered from thermal shutdown under high load. I disabled undervolt service from running and ensured everything was back to normal values - the stuttering improved, but was still present. I then focused on the difference between my Mi8 and my Ubuntu 18.10 installation. The Mi8 is running a LinesageOS ROM that supports LDAC/Apt-X codecs. I noticed with the regular AD2P codec in Ubuntu that I was getting some noise included in the Bluetooth audio encoding, and it sounded much cleaner via the Mi8 connection. I then found pulseaudio- modules-bt repo on github [2] that includes [3] a Ubuntu 18.04|18.10 repo that enabled LDAC/Apt-X codecs, LDAC is supported by the Sony bluetooth speaker. After installing and rebooting the machine, I confirmed that the codec was correctly initialised in the a2dp sync: berg@bxps:~$ pactl list sinks | grep -e bluez -e a2dp_codec Name: bluez_sink.E0_37_BF_09_F9_8B.a2dp_sink Driver: module-bluez5-device.c Monitor Source: bluez_sink.E0_37_BF_09_F9_8B.a2dp_sink.monitor bluetooth.a2dp_codec = "LDAC" device.api = "bluez" bluez.path = "/org/bluez/hci0/dev_E0_37_BF_09_F9_8B" bluez.class = "0x240414" bluez.alias = "bshg" The sound is now perfect, and copying files across the network results in no stuttering. I think this proves that the btcoex support is working correctly and there is no issue specifically with the Qualcomm firmware. I notice if I pair the bluetooth speaker and play back audio my network throughput is limited to about 14-15 MB/s, when I turn of the speaker it improves to 17-18 MB/s. So the module is correctly allowing bluetooth to operate with priority. Resuming the undervolt [1] service, I notice no stuttering as well with the updated pulseaudio and pulseaudio-module-bt packages in [2]. I'm going to continue testing for a few days before closing this bug, but I'm pretty sure I've gotten to the bottom of this one. Thanks @kaihenfeng. [1] https://github.com/georgewhewell/undervolt [2] https://github.com/EHfive/pulseaudio-modules-bt [3] https://github.com/EHfive/pulseaudio-modules-bt/wiki/Packages ** Summary changed: - QCA6174 doesn't utilise btcoex - Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570 + Suspect QCA6174 btcoex | Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570 [Pending PulseAudio testing] -- 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/1810636 Title: Suspect QCA6174 btcoex | Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570 [Pending PulseAudio testing] Status in linux package in Ubuntu: Confirmed Bug description: I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570 with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness ever since I have owned this laptop. This problem has persisted for me with previous kernels. If I disable wifi and use media on machine locally, the problem doesn't occur. Note: I've reverted back v4.18.0-13-generic and reproduced the problem for the apport-collect report. It started with Ubuntu 18.04 and continues with 18.10. It's particularly noticeable when the when saturating the WLAN connection with throughput, i.e. copying a large file sequentially across from a samba share, but also streaming video online results in the audio progressively delaying over-time. Re-establishing the Bluetooth audio sync restores the sync, but slowly creeps out again. I've upgraded my linux-firmware package to disco 176 to match v4.20 kernel drivers ref: https://launchpad.net/ubuntu/+source/linux- firmware/1.176 The ath10k_core driver that supports this device has a reference for btcoex: ref https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598 It's possible that the Bluetooth component firmware is not supporting or communicating btcoex compatibility, but this is starting to reach the edge of my ability to diagnose the problem. This btcoex support in ath9k has resolved/improved the Bluetooth bandwidth problem for older Qualcomm chipsets as shown in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164 As a troubleshooting step, I've also tried the very latest firmware-6 file from, but I'm continuing to experience the problem ref: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Kernel-packages] [Bug 1810267] Re: hard lockup on multiple CPUs in spl_cache_flush
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v5.0 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc1/ ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810267 Title: hard lockup on multiple CPUs in spl_cache_flush Status in linux package in Ubuntu: Confirmed Bug description: Photo of failed machine, and video of a second lockup at https://photos.app.goo.gl/9qUxysZ4LN1NRdrA7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jan 2 20:14:38 2019 InstallationDate: Installed on 2013-12-09 (1850 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-43-generic root=ZFS=tr2srv/ROOT/ubuntu ro nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-06-26 (189 days ago) dmi.bios.date: 10/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0808 dmi.board.asset.tag: Default string dmi.board.name: PRIME X399-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0808:bd10/12/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX399-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810267/+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 1810430] Re: tpm_crb MSFT0101:00: can't request region for resource
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810430 Title: tpm_crb MSFT0101:00: can't request region for resource Status in linux package in Ubuntu: Confirmed Bug description: New hardware (AMD Threadripper 2920x with an ASRock X399 Taichi motherboard) and a clean 18.04.1 install. I purposefully turn on AMD fTPM in the UEFI as I would like to explore using this to secure my system. However after booting with this option no /dev/tpm device node exists and the kernel boot output now includes the following... $ dmesg | grep -i tpm [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I 0001 AMI ) [0.928120] tpm_crb MSFT0101:00: can't request region for resource [mem 0x7943a000-0x7943afff] [0.928141] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.090180] ima: No TPM chip found, activating TPM-bypass! (rc=-19) I'm using the motherboard vendors latest issued UEFI firmware and am unable to locate any other examples of this issue on my hardware. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kelvin 3554 F pulseaudio /dev/snd/controlC0: kelvin 3554 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 17:11:03 2019 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=dc67630f-0924-11e9-b9f2-7085c2b1c052 ro amd_iommu=force_isolation iommu=pt transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X399 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399Taichi:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810430/+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 1781879]
(In reply to Hieu Cao from comment #169) > It worked on v4.20 automatically. Few days ago, but I also uninstalled it > either. Because the annoyning of disconnecting. I wonder if it fixed the > disconnecting? I just want to make sure that to reinstall linux again. > > (In reply to Andy Shevchenko from comment #168) > > This bug has been fixed in v4.20. > Does it fix the disconnecting problem? in my case (Asus GL703GE) it does not. Disconnection Problem persists, but you can take now a 4.20 Kernal without patch and the Touchpad will work except if you put 5 Fingers or the Palm on it (on GL703GE) with kind regards Marc Landolt -- 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/1781879 Title: Latest ASUS trackpad doesn't work in Ubuntu Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: It seems there might be a new hardware variant of the elan trackpad in the newer ASUS machines. The issue is the shown here with some reasonably deep investigation. Is this something that I can do or am I reduced to having to find out a mouse if I want to use Linux? https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/ user@TUF-GAMING-FX504GD-FX80GD:~$ xinput Virtual core pointer id=2[master pointer (3)] ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ↳ Logitech USB Receiver id=12 [slave pointer (2)] ↳ Logitech USB Receiver id=13 [slave pointer (2)] Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ Sleep Button id=11 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)] ↳ Asus WMI hotkeys id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=17 [slave keyboard (3)] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1781879/+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 1809316] Re: HDMI Audio failing after resuming from sleep
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809316 Title: HDMI Audio failing after resuming from sleep Status in linux package in Ubuntu: Confirmed Bug description: This issue occurs in both 16.04 and 18.04 on Dell Precision 7530 Before sleep, the sound settings show a single HDMI / Displayport "HDA NVidia" sound device (see attachment) Afterwards, there are several 'copies' of this device (see attachment) - No sound comes out of any of the HDMI devices Screen Captures + Logs included in .zip attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809316/+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 1810457] Re: Update hisilicon SoC-specific drivers
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- 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/1810457 Title: Update hisilicon SoC-specific drivers Status in linux package in Ubuntu: In Progress Bug description: [Impact] Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream periodically. [Test Case] [Fix] Various upstream patches. [Regression Risk] The number of changes here obviously comes with regression risk. However, these drivers are only used for two HiSilicon SoCs and their corresponding development platforms - D05 and D06. We are therefore able to mitigate the risk by directly testing these changes on the impacted devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
Today the problem presented itself, twice, with kernel 4.15.0-43-generic in Xubuntu 18.10. -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1809993] Re: Lenovo X1C6 trackpad functions broken
That fixed it! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809993 Title: Lenovo X1C6 trackpad functions broken Status in linux package in Ubuntu: Confirmed Bug description: Summary: After kernel update the trackpad advanced functions, like two finger scrolling and mouse acceleration have stopped working. Expected Result: Two finer scroll works and the mouse has acceleration features work Actual Result: Two finer scroll works and the mouse has acceleration features do not work Steps to reproduce: 1. Lenovo X1C6 (LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET59W (1.34 ) 11/08/2018) 2. Install 18.04 LTS 3. config-4.15.0-42-generic acceleration works, while config-4.15.0-43-generic does not This appears to be some sort of regression or change in behavior between kernel versions. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: powersj1597 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7 InstallationDate: Installed on 2018-12-06 (22 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 002: ID 5986:2115 Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KHCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET59W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET59W(1.34):bd11/08/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809993/+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 1807469] Re: Bionic update: upstream stable patchset 2018-12-07
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807469
Title:
Bionic update: upstream stable patchset 2018-12-07
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2018-12-07 (ported from v4.14.53 and v4.17.4)
from git://git.kernel.org/
x86/e820: put !E820_TYPE_RAM regions into memblock.reserved
dm: use bio_split() when splitting out the already processed bio
dm: rename 'bio' member of dm_io structure to 'orig_bio'
dm: ensure bio submission follows a depth-first tree walk
kasan: depend on CONFIG_SLUB_DEBUG
i2c: gpio: initialize SCL to HIGH again
ALSA: hda - Force to link down at runtime suspend on ATI/AMD HDMI
Input: silead - add MSSL0002 ACPI HID
Input: silead - add Chuwi Hi8 support
media: rc: mce_kbd decoder: fix stuck keys
remoteproc: Prevent incorrect rproc state on xfer mem ownership failure
mfd: twl-core: Fix clock initialization
f2fs: don't use GFP_ZERO for page caches
libnvdimm, pmem: Unconditionally deep flush on *sync
scsi: qla2xxx: Spinlock recursion in qla_target
scsi: scsi_debug: Fix memory leak on module unload
locking/rwsem: Fix up_read_non_owner() warning with DEBUG_RWSEMS
MIPS: pb44: Fix i2c-gpio GPIO descriptor table
pinctrl: armada-37xx: Fix spurious irq management
PCI: Account for all bridges on bus when distributing bus numbers
mtd: rawnand: mxc: set spare area size register explicitly
mtd: rawnand: fix return value check for bad block status
of: overlay: validate offset from property fixups
ARM64: dts: meson-gx: fix ATF reserved memory region
softirq: Reorder trace_softirqs_on to prevent lockdep splat
hwrng: core - Always drop the RNG in hwrng_unregister()
powerpc/e500mc: Set assembler machine type to e500mc
powerpc/64s: Set assembler machine type to POWER4
libnvdimm, pmem: Do not flush power-fail protected CPU caches
ASoC: mediatek: preallocate pages use platform device
PCI / PM: Do not clear state_saved for devices that remain suspended
mtd: spi-nor: intel-spi: Fix atomic sequence handling
spi-nor: intel-spi: Remove unused preopcodes field
hwmon: (k10temp) Add support for Stoney Ridge and Bristol Ridge CPUs
platform/chrome: cros_ec_lpc: do not try DMI match when ACPI device found
platform/chrome: cros_ec_lpc: Register the driver if ACPI entry is missing.
x86/platform/UV: Add kernel parameter to set memory block size
x86/platform/UV: Use new set memory block size function
dm thin: handle running out of data space vs concurrent discard
dm zoned: avoid triggering reclaim from inside dmz_map()
x86/efi: Fix efi_call_phys_epilog() with CONFIG_X86_5LEVEL=y
block: Fix cloning of requests with a special payload
block: Fix transfer when chunk sectors exceeds max
slub: fix failure when we delete and create a slab cache
ALSA: hda/realtek - Add a quirk for FSC ESPRIMO U9210
ALSA: hda/realtek - Fix pop noise on Lenovo P50 & co
ALSA: timer: Fix UBSAN warning at SNDRV_TIMER_IOCTL_NEXT_DEVICE ioctl
Input: elan_i2c_smbus - fix more potential stack buffer overflows
Input: xpad - fix GPD Win 2 controller name
udf: Detect incorrect directory size
xen: Remove unnecessary BUG_ON from __unbind_from_irq()
mm: fix devmem_is_allowed() for sub-page System RAM intersections
mm/ksm.c: ignore STABLE_FLAG of rmap_item->address in rmap_walk_ksm()
rbd: flush rbd_dev->watch_dwork after watch is unregistered
pwm: lpss: platform: Save/restore the ctrl register over a suspend/resume
Input: elan_i2c - add ELAN0618 (Lenovo v330 15IKB) ACPI ID
ACPI / LPSS: Add missing prv_offset setting for byt/cht PWM devices
NFSv4: Fix a typo in nfs41_sequence_process
NFSv4: Revert commit 5f83d86cf531d ("NFSv4.x: Fix wraparound issues..")
NFSv4: Fix possible 1-byte stack overflow in nfs_idmap_read_and_verify_message
nfsd: restrict rd_maxcount to svc_max_payload in nfsd_encode_readdir
media: dvb_frontend: fix locking issues at dvb_frontend_get_event()
media: cx231xx: Add support for AverMedia DVD EZMaker 7
media: v4l2-compat-ioctl32: prevent go past max size
media: vsp1: Release buffers for each video node
perf intel-pt: Fix packet decoding of CYC packets
perf intel-pt: Fix "Unexpected indirect
[Kernel-packages] [Bug 1808185] Re: Bionic update: upstream stable patchset 2018-12-12
** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808185 Title: Bionic update: upstream stable patchset 2018-12-12 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2018-12-12 (ported from v4.14.54 and v4.17.5) from git://git.kernel.org/ x86/mm: Don't free P4D table when it is folded at runtime ARM64: dts: meson-gxl-s905x-p212: Add phy-supply for usb0 drm/i915: Fix PIPESTAT irq ack on i965/g4x drm/amd/display: release spinlock before committing updates to stream drm/amdgpu: GPU vs CPU page size fixes in amdgpu_vm_bo_split_mapping drm/amdgpu: Don't default to DC support for Kaveri and older drm/amdgpu: remove DC special casing for KB/ML drm/i915/dp: Send DPCD ON for MST before phy_up drm/amd/display: Clear connector's edid pointer drm/amdgpu: fix clear_all and replace handling in the VM (v2) iio: mma8452: Fix ignoring MMA8452_INT_DRDY usb: typec: tcpm: fix logbuffer index is wrong if _tcpm_log is re-entered net: dsa: b53: Add BCM5389 support net/sonic: Use dma_mapping_error() platform/x86: asus-wmi: Fix NULL pointer dereference sched/core: Require cpu_active() in select_task_rq(), for user tasks sched/core: Fix rules for running on online && !active CPUs fs: clear writeback errors in inode_init_always perf bpf: Fix NULL return handling in bpf__prepare_load() perf test: "Session topology" dumps core on s390 net: qmi_wwan: Add Netgear Aircard 779S atm: zatm: fix memcmp casting iwlwifi: pcie: compare with number of IRQs requested for, not number of CPUs ipvs: fix buffer overflow with sync daemon and service netfilter: nft_limit: fix packet ratelimiting s390/dasd: use blk_mq_rq_from_pdu for per request data netfilter: ebtables: handle string from userspace with care afs: Fix directory permissions check xfrm6: avoid potential infinite loop in _decode_session6() ARM: dts: imx6q: Use correct SDMA script for SPI5 core netfilter: nf_tables: use WARN_ON_ONCE instead of BUG_ON in nft_do_chain() netfilter: ip6t_rpfilter: provide input interface for route lookup netfilter: don't set F_IFACE on ipv6 fib lookups netfilter: nf_tables: fix NULL-ptr in nf_tables_dump_obj() netfilter: nf_tables: add missing netlink attrs to policies netfilter: nf_tables: fix memory leak on error exit return netfilter: nf_tables: increase nft_counters_enabled in nft_chain_stats_replace() netfilter: nf_tables: disable preemption in nft_update_chain_stats() netfilter: nft_meta: fix wrong value dereference in nft_meta_set_eval netfilter: nf_tables: bogus EBUSY in chain deletions netfilter: nf_tables: don't assume chain stats are set when jumplabel is set netfilter: nft_compat: fix handling of large matchinfo size netfilter: nft_compat: prepare for indirect info storage netfilter: nf_tables: nft_compat: fix refcount leak on xt module drm/i915: Enable provoking vertex fix on Gen9 systems. drm/amdgpu: Refactor amdgpu_vram_mgr_bo_invisible_size helper drm/amdgpu: Use kvmalloc_array for allocating VRAM manager nodes array drm/atmel-hlcdc: check stride values in the first plane drm/qxl: Call qxl_bo_unref outside atomic context drm/amdgpu: fix the missed vcn fw version report drm/amdgpu: Add APU support in vi_set_vce_clocks drm/amdgpu: Add APU support in vi_set_uvd_clocks vt: prevent leaking uninitialized data to userspace via /dev/vcs* serdev: fix memleak on module unload serial: 8250_pci: Remove stalled entries in blacklist staging: android: ion: Return an ERR_PTR in ion_map_kernel n_tty: Access echo_* variables carefully. n_tty: Fix stall at n_tty_receive_char_special(). xhci: Fix kernel oops in trace_xhci_free_virt_device usb: typec: ucsi: Fix for incorrect status data issue usb: typec: ucsi: acpi: Workaround for cache mode issue acpi: Add helper for deactivating memory region usb: dwc2: fix the incorrect bitmaps for the ports of multi_tt hub USB: serial: cp210x: add Silicon Labs IDs for Windows Update USB: serial: cp210x: add CESINEL device ids usb: cdc_acm: Add quirk for Uniden UBC125 scanner To manage notifications about this bug go to:
[Kernel-packages] [Bug 1808399] Re: Bionic update: upstream stable patchset 2018-12-13
** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808399 Title: Bionic update: upstream stable patchset 2018-12-13 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2018-12-13 (ported from v4.14.55 and v4.17.6) from git://git.kernel.org/ i2c: core: smbus: fix a potential missing-check bug drm/amdgpu: Dynamically probe for ATIF handle (v2) drm/amdgpu: Add amdgpu_atpx_get_dhandle() ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl scsi: aacraid: Fix PD performance regression over incorrect qd being set drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM sched, tracing: Fix trace_sched_pi_setprio() for deboosting staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() netfilter: nf_log: don't hold nf_log_mutex during user access mtd: cfi_cmdset_0002: Change erase functions to check chip good only mtd: cfi_cmdset_0002: Change erase functions to retry for error mtd: cfi_cmdset_0002: Change definition naming to retry write operation dm: prevent DAX mounts if not supported dm: set QUEUE_FLAG_DAX accordingly in dm_table_set_restrictions() dax: check for QUEUE_FLAG_DAX in bdev_dax_supported() dax: change bdev_dax_supported() to support boolean returns fs: allow per-device dax status checking for filesystems media: cx25840: Use subdev host data for PLL override Kbuild: fix # escaping in .cmd files for future Make Revert "dpaa_eth: fix error in dpaa_remove()" f2fs: truncate preallocated blocks in error case media: vb2: core: Finish buffers at the end of the stream HID: debug: check length before copy_to_user() HID: hiddev: fix potential Spectre v1 HID: i2c-hid: Fix "incomplete report" noise ext4: check superblock mapped prior to committing ext4: add more mount time checks of the superblock ext4: add more inode number paranoia checks ext4: avoid running out of journal credits when appending to an inline file ext4: never move the system.data xattr out of the inode body ext4: include the illegal physical block in the bad map ext4_error msg ext4: verify the depth of extent tree in ext4_find_extent() ext4: only look at the bg_flags field if it is valid ext4: always check block group bounds in ext4_init_block_bitmap() ext4: make sure bitmaps and the inode table don't overlap with bg descriptors ext4: always verify the magic number in xattr blocks ext4: add corruption check in ext4_xattr_set_entry() jbd2: don't mark block as modified if the handle is out of credits drm/udl: fix display corruption of the last line drm: Use kvzalloc for allocating blob property memory cifs: Fix infinite loop when using hard mount option cifs: Fix memory leak in smb2_set_ea() cifs: Fix use after free of a mid_q_entry vfio: Use get_user_pages_longterm correctly drbd: fix access after free s390: Correct register corruption in critical section cleanup scsi: target: Fix truncated PR-in ReadKeys response tracing: Fix missing return symbol in function_graph output mm: hugetlb: yield when prepping struct pages userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808399/+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 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
i'm having this issue on 18.10 as well, 4.18.0-13-generic with a Logitech C310 (046d:081b). it's been an issue since 18.04 and older for me; i can't remember when it worked without issue, but it did at some point. it appears this commit [0] is the cause as after restoring the specific USB_QUIRK_RESET_RESUME line for my model and recompiling the kernel i cannot reproduce the squeaky-voice issue. with the standard kernel i can reliably reproduce it with Audacity by recording, stopping the recording, then starting another recording - after ~3 "correct" recordings the pitch changes. with the recompiled kernel it appears the device is being "reset" for each recording: usb 2-1.6: reset high-speed USB device number 4 using ehci-pci i do not see this when using the standard 4.18.0-13-generic kernel, so i'm guessing this is what the quirk does and usb_interface_quirk_list in quirks.c isn't catching my webcam. i believe there should be a match based on the code; lsusb output includes the following Interface which looks like it matches the call (USB_VENDOR_AND_INTERFACE_INFO(0x046d, USB_CLASS_VIDEO, 1, 0)) since USB_CLASS_VIDEO is 0x0e which matches the bInterfaceClass, and subclass/protocol also match. note that this is not the first interface in the lsusb output, not sure if that matters. Bus 002 Device 004: ID 046d:081b Logitech, Inc. Webcam C310 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association ... Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass14 Video bInterfaceSubClass 1 Video Control bInterfaceProtocol 0 iInterface 0 ... please let me know if there is anything else i can provide to help debug this issue. [0] https://github.com/torvalds/linux/commit/e387ef5c47ddeaeaa3cbdc54424cdb7a28dae2c0 -- 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/843431 Title: Logitech camera microphone does not work / makes "chipmunk" sound Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Status in linux package in Debian: New Bug description: Did not know which application to log so feel free to let me know and I'll upload the correct log. In Natty, this mic worked great. Now, in the sound control panel, the mic does not show any input level at all and sound recorder does not record any sound. edit: I can also confirm the same behavior as Alex Popovskiy. It either works but plays too fast (high pitch) or it doesn't work at all. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Sep 6 20:31:13 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1594 F pulseaudio /dev/snd/controlC0: alex 1594 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xf9ef4000 irq 16' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,18490397,0010' Controls : 36 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-:00:13.2-6, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0809' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6400 Mono: Capture 6400 [100%] [31.00dB] [on] DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=8ccfea11-7ba8-42e2-bc75-a37e20a8c83c InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic
[Kernel-packages] [Bug 1810821] [NEW] Cosmic update: 4.18.20 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.18.20 upstream stable release from git://git.kernel.org/ powerpc/traps: restore recoverability of machine_check interrupts powerpc/64/module: REL32 relocation range check powerpc/mm: Fix page table dump to work on Radix powerpc/mm: fix always true/false warning in slice.c drm/amd/display: fix bug of accessing invalid memory Input: wm97xx-ts - fix exit path powerpc/Makefile: Fix PPC_BOOK3S_64 ASFLAGS powerpc/eeh: Fix possible null deref in eeh_dump_dev_log() tty: check name length in tty_find_polling_driver() tracing/kprobes: Check the probe on unloaded module correctly drm/amdgpu/powerplay: fix missing break in switch statements ARM: imx_v6_v7_defconfig: Select CONFIG_TMPFS_POSIX_ACL powerpc/nohash: fix undefined behaviour when testing page size support powerpc/mm: Don't report hugepage tables as memory leaks when using kmemleak drm/omap: fix memory barrier bug in DMM driver drm/amd/display: fix gamma not being applied drm/hisilicon: hibmc: Do not carry error code in HiBMC framebuffer pointer media: pci: cx23885: handle adding to list failure media: coda: don't overwrite h.264 profile_idc on decoder instance MIPS: kexec: Mark CPU offline before disabling local IRQ powerpc/boot: Ensure _zimage_start is a weak symbol powerpc/memtrace: Remove memory in chunks MIPS/PCI: Call pcie_bus_configure_settings() to set MPS/MRRS sc16is7xx: Fix for multi-channel stall media: tvp5150: fix width alignment during set_selection() powerpc/selftests: Wait all threads to join staging:iio:ad7606: fix voltage scales drm: rcar-du: Update Gen3 output limitations drm/amdgpu: Fix SDMA TO after GPU reset v3 staging: most: video: fix registration of an empty comp core_component 9p locks: fix glock.client_id leak in do_lock udf: Prevent write-unsupported filesystem to be remounted read-write ARM: dts: imx6ull: keep IMX6UL_ prefix for signals on both i.MX6UL and i.MX6ULL 9p: clear dangling pointers in p9stat_free ovl: fix error handling in ovl_verify_set_fh() ovl: check whiteout in ovl_create_over_whiteout() serial: sh-sci: Fix could not remove dev_attr_rx_fifo_timeout scsi: qla2xxx: Fix incorrect port speed being set for FC adapters scsi: qla2xxx: Fix process response queue for ISP26XX and above scsi: qla2xxx: Remove stale debug trace message from tcm_qla2xxx scsi: qla2xxx: shutdown chip if reset fail scsi: qla2xxx: Fix duplicate switch database entries scsi: qla2xxx: Fix driver hang when FC-NVMe LUNs are configured fuse: Fix use-after-free in fuse_dev_do_read() fuse: Fix use-after-free in fuse_dev_do_write() fuse: fix blocked_waitq wakeup fuse: set FR_SENT while locked ovl: fix recursive oi->lock in ovl_link() scsi: qla2xxx: Fix re-using LoopID when handle is in use scsi: qla2xxx: Fix NVMe session hang on unload arm64: dts: stratix10: Support Ethernet Jumbo frame arm64: dts: stratix10: fix multicast filtering clk: meson-gxbb: set fclk_div3 as CLK_IS_CRITICAL clk: meson: axg: mark fdiv2 and fdiv3 as critical zram: close udev startup race condition as default groups MIPS: Loongson-3: Fix CPU UART irq delivery problem MIPS: Loongson-3: Fix BRIDGE irq delivery problem xtensa: add NOTES section to the linker script xtensa: make sure bFLT stack is 16 byte aligned xtensa: fix boot parameters address translation um: Drop own definition of PTRACE_SYSEMU/_SINGLESTEP clk: s2mps11: Fix matching when built as module and DT node contains compatible clk: at91: Fix division by zero in PLL recalc_rate() clk: sunxi-ng: h6: fix bus clocks' divider position clk: rockchip: fix wrong mmc sample phase shift for rk3328 clk: rockchip: Fix static checker warning in rockchip_ddrclk_get_parent call libceph: bump CEPH_MSG_MAX_DATA_LEN Revert "ceph: fix dentry leak in splice_dentry()" thermal: core: Fix use-after-free in thermal_cooling_device_destroy_sysfs mach64: fix display corruption on big endian machines mach64: fix image corruption due to reading accelerator registers acpi/nfit, x86/mce: Handle only uncorrectable machine checks acpi/nfit, x86/mce: Validate a MCE's address before using it acpi, nfit: Fix ARS overflow continuation reset: hisilicon: fix potential NULL pointer dereference vhost/scsi: truncate T10 PI iov_iter to prot_bytes scsi: qla2xxx: Initialize port speed to avoid setting lower speed SCSI: fix queue cleanup race before queue initialization is done Revert "powerpc/8xx: Use L1 entry APG to handle _PAGE_ACCESSED for CONFIG_SWAP" soc: ti: QMSS: Fix usage of irq_set_affinity_hint ocfs2: fix a misuse a of brelse after failing ocfs2_check_dir_entry ocfs2: free up write
[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty
** Changed in: linux (Ubuntu Trusty) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791758 Title: ldisc crash on reopened tty Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: [Impact] The following Oops was discovered by user: [684766.39] BUG: unable to handle kernel paging request at 2268 [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0 [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0 [684766.669194] Oops: [#1] SMP [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev [684766.679406] input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P OE 4.4.0-124-generic #148~14.04.1-Ubuntu [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [684766.686062] Workqueue: events_unbound flush_to_ldisc [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 88170dc2c000 [684766.687670] RIP: 0010:[] [] n_tty_receive_buf_common+0x6a/0xae0 [684766.688870] RSP: 0018:88170dc2fd28 EFLAGS: 00010202 [684766.689521] RAX: RBX: 88162c895000 RCX: 0001 [684766.690488] RDX: RSI: 88162c895020 RDI: 8819c2d3d4d8 [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 81ec2ba0 [684766.692480] R10: 0004 R11: R12: 8819c2d3d400 [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 8819c2d3d400 [684766.694390] FS: () GS:8819d73c() knlGS: [684766.695484] CS: 0010 DS: ES: CR0: 80050033 [684766.696182] CR2: 2268 CR3: 00195752 CR4: 00360670 [684766.697141] DR0: DR1: DR2: [684766.698114] DR3: DR6: fffe0ff0 DR7: 0400 [684766.699079] Stack: [684766.699412] 8819c2d3d4d8 8819c2d3d648 [684766.700467] 8819c2d3d620 8819c9c10400 88170dc2fd68 8106312e [684766.701501] 88170dc2fd78 0001 88162c895020 [684766.702534] Call Trace: [684766.702905] [] ? kvm_sched_clock_read+0x1e/0x30 [684766.703685] [] n_tty_receive_buf2+0x14/0x20 [684766.704505] [] flush_to_ldisc+0xd5/0x120 [684766.705269] [] process_one_work+0x156/0x400 [684766.706008] [] worker_thread+0x11a/0x480 [684766.706686] [] ? rescuer_thread+0x310/0x310 [684766.707386] [] kthread+0xd8/0xf0 [684766.707993] [] ? kthread_park+0x60/0x60 [684766.708664] [] ret_from_fork+0x55/0x80 [684766.709335] [] ? kthread_park+0x60/0x60 [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00 [684766.713290] RIP [] n_tty_receive_buf_common+0x6a/0xae0 [684766.714105] RSP [684766.714609] CR2: 2268 The issue happened in a VM KDUMP was configured, so a full Kernel crashdump was created User has Ubuntu Trusty, Kernel 4.4.0-124 on its VM [Test Case] * Deploy a Trusty KVM instance with a LTS Xenial kernel (v4.4 series) * SSH
[Kernel-packages] [Bug 1810820] Re: Cosmic update: 4.18.19 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + 4.18.19 upstream stable release + from git://git.kernel.org/ -4.18.19 upstream stable release -from git://git.kernel.org/ + mtd: rawnand: marvell: fix the IRQ handler complete() condition + mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB + mtd: spi-nor: intel-spi: Add support for Intel Ice Lake SPI serial flash + mtd: spi-nor: fsl-quadspi: Don't let -EINVAL on the bus + spi: spi-mem: Adjust op len based on message/transfer size limitations + spi: bcm-qspi: switch back to reading flash using smaller chunks + spi: bcm-qspi: fix calculation of address length + bcache: trace missed reading by cache_missed + bcache: correct dirty data statistics + bcache: fix miss key refill->end in writeback + hwmon: (pmbus) Fix page count auto-detection. + jffs2: free jffs2_sb_info through jffs2_kill_sb() + block: setup bounce bio_sets properly + block: don't deal with discard limit in blkdev_issue_discard() + block: make sure discard bio is aligned with logical block size + block: make sure writesame bio is aligned with logical block size + cpufreq: conservative: Take limits changes into account properly + dma-mapping: fix panic caused by passing empty cma command line argument + pcmcia: Implement CLKRUN protocol disabling for Ricoh bridges + ACPI / OSL: Use 'jiffies' as the time bassis for acpi_os_get_timer() + ACPICA: AML Parser: fix parse loop to correctly skip erroneous extended opcodes + kprobes/x86: Use preempt_enable() in optimized_callback() + mailbox: PCC: handle parse error + acpi, nfit: Fix Address Range Scrub completion tracking + parisc: Fix address in HPMC IVA + parisc: Fix map_pages() to not overwrite existing pte entries + parisc: Fix exported address of os_hpmc handler + ALSA: hda - Add quirk for ASUS G751 laptop + ALSA: hda - Fix headphone pin config for ASUS G751 + ALSA: hda - Add mic quirk for the Lenovo G50-30 (17aa:3905) + ALSA: hda: Add 2 more models to the power_save blacklist + ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops + x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation + x86/xen: Fix boot loader version reported for PVH guests + x86/corruption-check: Fix panic in memory_corruption_check() when boot option without value is provided + x86/mm/pat: Disable preemption around __flush_tlb_all() + ARM: dts: exynos: Disable pull control for MAX8997 interrupts on Origen + drm: fix use of freed memory in drm_mode_setcrtc + bpf: do not blindly change rlimit in reuseport net selftest + nvme: remove ns sibling before clearing path + Revert "perf tools: Fix PMU term format max value calculation" + selftests: usbip: add wait after attach and before checking port status + xsk: do not call synchronize_net() under RCU read lock + xfrm: policy: use hlist rcu variants on insert + perf vendor events intel: Fix wrong filter_band* values for uncore events + r8169: Enable MSI-X on RTL8106e + nfp: flower: fix pedit set actions for multiple partial masks + nfp: flower: use offsets provided by pedit instead of index for ipv6 + sched/fair: Fix the min_vruntime update logic in dequeue_entity() + perf evsel: Store ids for events with their own cpus perf_event__synthesize_event_update_cpus + perf tools: Fix use of alternatives to find JDIR + perf cpu_map: Align cpu map synthesized events properly. + perf report: Don't crash on invalid inline debug information + x86/fpu: Remove second definition of fpu in __fpu__restore_sig() + net: qla3xxx: Remove overflowing shift statement + r8169: re-enable MSI-X on RTL8168g + drm: Get ref on CRTC commit object when waiting for flip_done + selftests: ftrace: Add synthetic event syntax testcase + i2c: rcar: cleanup DMA for all kinds of failure + net: socionext: Reset tx queue in ndo_stop + locking/lockdep: Fix debug_locks off performance problem + netfilter: xt_nat: fix DNAT target for shifted portmap ranges + ataflop: fix error handling during setup + swim: fix cleanup on setup error + arm64: cpufeature: ctr: Fix cpu capability check for late CPUs + nfp:
[Kernel-packages] [Bug 1810820] [NEW] Cosmic update: 4.18.19 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.18.19 upstream stable release
from git://git.kernel.org/
mtd: rawnand: marvell: fix the IRQ handler complete() condition
mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB
mtd: spi-nor: intel-spi: Add support for Intel Ice Lake SPI serial flash
mtd: spi-nor: fsl-quadspi: Don't let -EINVAL on the bus
spi: spi-mem: Adjust op len based on message/transfer size limitations
spi: bcm-qspi: switch back to reading flash using smaller chunks
spi: bcm-qspi: fix calculation of address length
bcache: trace missed reading by cache_missed
bcache: correct dirty data statistics
bcache: fix miss key refill->end in writeback
hwmon: (pmbus) Fix page count auto-detection.
jffs2: free jffs2_sb_info through jffs2_kill_sb()
block: setup bounce bio_sets properly
block: don't deal with discard limit in blkdev_issue_discard()
block: make sure discard bio is aligned with logical block size
block: make sure writesame bio is aligned with logical block size
cpufreq: conservative: Take limits changes into account properly
dma-mapping: fix panic caused by passing empty cma command line argument
pcmcia: Implement CLKRUN protocol disabling for Ricoh bridges
ACPI / OSL: Use 'jiffies' as the time bassis for acpi_os_get_timer()
ACPICA: AML Parser: fix parse loop to correctly skip erroneous extended opcodes
kprobes/x86: Use preempt_enable() in optimized_callback()
mailbox: PCC: handle parse error
acpi, nfit: Fix Address Range Scrub completion tracking
parisc: Fix address in HPMC IVA
parisc: Fix map_pages() to not overwrite existing pte entries
parisc: Fix exported address of os_hpmc handler
ALSA: hda - Add quirk for ASUS G751 laptop
ALSA: hda - Fix headphone pin config for ASUS G751
ALSA: hda - Add mic quirk for the Lenovo G50-30 (17aa:3905)
ALSA: hda: Add 2 more models to the power_save blacklist
ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops
x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation
x86/xen: Fix boot loader version reported for PVH guests
x86/corruption-check: Fix panic in memory_corruption_check() when boot option
without value is provided
x86/mm/pat: Disable preemption around __flush_tlb_all()
ARM: dts: exynos: Disable pull control for MAX8997 interrupts on Origen
drm: fix use of freed memory in drm_mode_setcrtc
bpf: do not blindly change rlimit in reuseport net selftest
nvme: remove ns sibling before clearing path
Revert "perf tools: Fix PMU term format max value calculation"
selftests: usbip: add wait after attach and before checking port status
xsk: do not call synchronize_net() under RCU read lock
xfrm: policy: use hlist rcu variants on insert
perf vendor events intel: Fix wrong filter_band* values for uncore events
r8169: Enable MSI-X on RTL8106e
nfp: flower: fix pedit set actions for multiple partial masks
nfp: flower: use offsets provided by pedit instead of index for ipv6
sched/fair: Fix the min_vruntime update logic in dequeue_entity()
perf evsel: Store ids for events with their own cpus
perf_event__synthesize_event_update_cpus
perf tools: Fix use of alternatives to find JDIR
perf cpu_map: Align cpu map synthesized events properly.
perf report: Don't crash on invalid inline debug information
x86/fpu: Remove second definition of fpu in __fpu__restore_sig()
net: qla3xxx: Remove overflowing shift statement
r8169: re-enable MSI-X on RTL8168g
drm: Get ref on CRTC commit object when waiting for flip_done
selftests: ftrace: Add synthetic event syntax testcase
i2c: rcar: cleanup DMA for all kinds of failure
net: socionext: Reset tx queue in ndo_stop
locking/lockdep: Fix debug_locks off performance problem
netfilter: xt_nat: fix DNAT target for shifted portmap ranges
ataflop: fix error handling during setup
swim: fix cleanup on setup error
arm64: cpufeature: ctr: Fix cpu capability check for late CPUs
nfp: devlink port split support for 1x100G CXP NIC
tun: Consistently configure generic netdev params via rtnetlink
s390/sthyi: Fix machine name validity indication
hwmon: (pwm-fan) Set fan speed to 0 on suspend
lightnvm: pblk: fix race on sysfs line state
lightnvm: pblk: fix two sleep-in-atomic-context bugs
lightnvm: pblk: fix race condition on metadata I/O
spi: spi-ep93xx: Use dma_data_direction for ep93xx_spi_dma_{finish,prepare}
perf tools: Free temporary 'sys' string in read_event_files()
perf tools: Cleanup trace-event-info 'tdata' leak
perf strbuf: Match va_{add,copy} with va_end
cpupower: Fix coredump on VMWare
bcache: Populate writeback_rate_minimum attribute
mmc: sdhci-pci-o2micro: Add quirk
[Kernel-packages] [Bug 1809934] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1809934 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: cosmic -- 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/1809934 Title: AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot Status in linux package in Ubuntu: Incomplete Bug description: CPU: AMD Ryzen 5 2400G / AMD Ryzen 3 2200G Version: Ubuntu 18.04.1 Desktop (AMD64) Kernel: 4.15.0-43 generic Mainboard: ASUS Prime X370-Pro (4207), ASRock B450 Pro4 (1.80), MSI B350 Tomahawk (7A34v1K), Gigabyte GA-AB350M-Gaming3 (F24c) Detailed information: AMD AGESA version "PinnaclePI-AM4 1.0.0.6" based firmware is released by many major mainboard manufacturers lately. However, this 1.0.0.6 based firmware with Raven Ridge processors (2200G, 2400G and more) cause system hangs on boot if a system is running 4.15.0 kernel. If install kernel version 4.18.0-13-generic from "linux-image-generic- hwe-18.04-edge" has no issue. Here is boot messages output (dumped via serial port and truncated): [4.385021] [drm] ring test on 5 succeeded in 3 usecs [4.385030] [drm] ring test on 6 succeeded in 2 usecs [4.385035] [drm] ring test on 7 succeeded in 1 usecs [4.385044] [drm] ring test on 8 succeeded in 2 usecs [4.385090] [drm] ring test on 10 succeeded in 2 usecs [5.406001] clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc' as unstable because the skew is too large: [5.406002] clocksource: 'hpet' wd_now: 5152d87 wd_last: 40b14df mask: [5.406004] clocksource: 'tsc' cs_now: f4c92bc9d cs_last: ebf5adbce mask: [5.406006] tsc: Marking TSC unstable due to clocksource watchdog [5.406014] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [5.406015] sched_clock: Marking unstable (5406009219, 0)<-(5548358599, -142345214) [7.906021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [9.156104] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: writing more dwords to the ring than expected! [ 11.656035] ata2.00: ATA-8: TOSHIBA DT01ACA200, MX4OABB0, max UDMA/133 [ 32.204004] watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [kworker/2:1:60] [ 32.204005] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 amdgpu(+) chash i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect uas sysimgblt fb_sys_fops drm r8169 usb_storage i2c_piix4 mii ahci libahci wmi video gpio_a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809934/+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 1810781] Re: mpt3sas - driver using the wrong register to update a queue index in FW
Patch submitted to kernel-team mailing list, got 2 ACKs. https://lists.ubuntu.com/archives/kernel-team/2019-January/097471.html -- 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/1810781 Title: mpt3sas - driver using the wrong register to update a queue index in FW Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Bug description: [Impact] * Adapter resets periodically during high-load activity. * I/O stalls until reset/reinit is complete (latency) and I/O performance degrades across cluster (e.g., low throughput from data spread over nodes). * The mpt3sas driver relies in a FW queue (Reply Post Descriptor Queue) in the I/O completion path; there's a MMIO register that driver uses to flag an empty entry in such queue, called Reply Post Host Index. This value is updated during the driver interrupt routine [in _base_interrupt() function]. * Happens that there are 2 registers representing the Reply Post Host Index according to the type of the adapter. They are differentiated in the driver through the "ioc->combined_reply_queue" check. By the MPI specification (vendor spec), driver should use this combined reply queue according to the number of maximum MSI-X vectors that the adapter exposes and the spec version (SAS 3.0 vs SAS 3.5). * Currently, this is wrong checked for a class of adapters, which was fixed in the upstream kernel commit 2b48be65685a [0]. Without this commit, we can observe spontaneous resets in the driver due to queue overflow (FW is not aware that there are free entries in the Reply Post Descriptor Queue). The dmesg log will show the following output in case of this error: mpt3sas_cm0: fault_state(0x2100)! mpt3sas_cm0: sending diag reset !! mpt3sas_cm0: diag reset: SUCCESS [followed by a lot of driver messages as result of the reset procedure] * During these resets, I/O is stalled so it may affect performance. [Test Case] * It's not trivial to test the problem, but given a machine with an affected device, an I/O benchmark like FIO could be used to exercise the I/O path in a heavy way and trigger the issue. * We have reports that the adapter "LSI Logic / Symbios Logic Device [1000:00ac]" is affected by the issue. And this commit resolved the problem. [Regression Potential] * This is a long-term issue from the mpt3sas driver, affecting only a class of adapters of this vendor. Since it's a clearly bug, the fix is necessary. The potential of regressions is unknown, but likely low - it changes the register used for the index updates given some set of characteristics of the adapter (according to the spec.), which restricts even more the scope of this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810781/+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 1810818] [NEW] Cosmic update: 4.18.18 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.18.18 upstream stable release
from git://git.kernel.org/
eeprom: at24: Add support for address-width property
vfs: swap names of {do,vfs}_clone_file_range()
bpf: fix partial copy of map_ptr when dst is scalar
gpio: mxs: Get rid of external API call
clk: sunxi-ng: sun4i: Set VCO and PLL bias current to lowest setting
fscache: Fix incomplete initialisation of inline key space
cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)
fscache: Fix out of bound read in long cookie keys
ptp: fix Spectre v1 vulnerability
drm/edid: Add 6 bpc quirk for BOE panel in HP Pavilion 15-n233sl
drm/edid: VSDB yCBCr420 Deep Color mode bit definitions
drm: fb-helper: Reject all pixel format changing requests
RDMA/ucma: Fix Spectre v1 vulnerability
IB/ucm: Fix Spectre v1 vulnerability
cdc-acm: do not reset notification buffer index upon urb unlinking
cdc-acm: correct counting of UART states in serial state notification
cdc-acm: fix race between reset and control messaging
usb: usbip: Fix BUG: KASAN: slab-out-of-bounds in vhci_hub_control()
usb: gadget: storage: Fix Spectre v1 vulnerability
usb: roles: intel_xhci: Fix Unbalanced pm_runtime_enable
usb: xhci: pci: Enable Intel USB role mux on Apollo Lake platforms
USB: fix the usbfs flag sanitization for control transfers
tracing: Fix synthetic event to accept unsigned modifier
tracing: Fix synthetic event to allow semicolon at end
Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15IGM
drm/sun4i: Fix an ulong overflow in the dotclock driver
sched/fair: Fix throttle_list starvation with low CFS quota
x86/tsc: Force inlining of cyc2ns bits
x86, hibernate: Fix nosave_regions setup for hibernation
x86/percpu: Fix this_cpu_read()
x86/time: Correct the attribute on jiffies' definition
x86/swiotlb: Enable swiotlb for > 4GiG RAM on 32-bit kernels
x86/fpu: Fix i486 + no387 boot crash by only saving FPU registers on context
switch if there is an FPU
Linux 4.18.18
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Cosmic)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ 4.18.18 upstream stable release
+ from git://git.kernel.org/
-4.18.18 upstream stable release
-from git://git.kernel.org/
+ eeprom: at24: Add support for address-width property
+ vfs: swap names of {do,vfs}_clone_file_range()
+ bpf: fix partial copy of map_ptr when dst is scalar
+ gpio: mxs: Get rid of external API call
+ clk: sunxi-ng: sun4i: Set VCO and PLL bias current to lowest setting
+ fscache: Fix incomplete initialisation of inline key space
+ cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)
+ fscache: Fix out of bound read in long cookie keys
+ ptp: fix Spectre v1 vulnerability
+ drm/edid: Add 6 bpc quirk for BOE panel in HP Pavilion 15-n233sl
+ drm/edid: VSDB yCBCr420 Deep Color mode bit definitions
+ drm: fb-helper: Reject all pixel format changing requests
+ RDMA/ucma: Fix Spectre v1 vulnerability
+ IB/ucm: Fix Spectre v1 vulnerability
+ cdc-acm: do not reset notification buffer index upon urb unlinking
+ cdc-acm: correct counting of UART states in serial state notification
+ cdc-acm: fix race between reset and control messaging
+ usb: usbip: Fix BUG: KASAN: slab-out-of-bounds in vhci_hub_control()
+ usb: gadget: storage: Fix Spectre v1 vulnerability
+ usb:
[Kernel-packages] [Bug 1809934] Re: AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809934 Title: AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot Status in linux package in Ubuntu: New Bug description: CPU: AMD Ryzen 5 2400G / AMD Ryzen 3 2200G Version: Ubuntu 18.04.1 Desktop (AMD64) Kernel: 4.15.0-43 generic Mainboard: ASUS Prime X370-Pro (4207), ASRock B450 Pro4 (1.80), MSI B350 Tomahawk (7A34v1K), Gigabyte GA-AB350M-Gaming3 (F24c) Detailed information: AMD AGESA version "PinnaclePI-AM4 1.0.0.6" based firmware is released by many major mainboard manufacturers lately. However, this 1.0.0.6 based firmware with Raven Ridge processors (2200G, 2400G and more) cause system hangs on boot if a system is running 4.15.0 kernel. If install kernel version 4.18.0-13-generic from "linux-image-generic- hwe-18.04-edge" has no issue. Here is boot messages output (dumped via serial port and truncated): [4.385021] [drm] ring test on 5 succeeded in 3 usecs [4.385030] [drm] ring test on 6 succeeded in 2 usecs [4.385035] [drm] ring test on 7 succeeded in 1 usecs [4.385044] [drm] ring test on 8 succeeded in 2 usecs [4.385090] [drm] ring test on 10 succeeded in 2 usecs [5.406001] clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc' as unstable because the skew is too large: [5.406002] clocksource: 'hpet' wd_now: 5152d87 wd_last: 40b14df mask: [5.406004] clocksource: 'tsc' cs_now: f4c92bc9d cs_last: ebf5adbce mask: [5.406006] tsc: Marking TSC unstable due to clocksource watchdog [5.406014] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [5.406015] sched_clock: Marking unstable (5406009219, 0)<-(5548358599, -142345214) [7.906021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [9.156104] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: writing more dwords to the ring than expected! [ 11.656035] ata2.00: ATA-8: TOSHIBA DT01ACA200, MX4OABB0, max UDMA/133 [ 32.204004] watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [kworker/2:1:60] [ 32.204005] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 amdgpu(+) chash i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect uas sysimgblt fb_sys_fops drm r8169 usb_storage i2c_piix4 mii ahci libahci wmi video gpio_a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809934/+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 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Uploaded phase-changed: Monday, 07. January 2019 10:00 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages copies requested -- 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/1810370 Title: linux-oem: 4.15.0-1031.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Uploaded phase-changed: Monday, 07. January 2019 10:00 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+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 1809934] [NEW] AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot
You have been subscribed to a public bug: CPU: AMD Ryzen 5 2400G / AMD Ryzen 3 2200G Version: Ubuntu 18.04.1 Desktop (AMD64) Kernel: 4.15.0-43 generic Mainboard: ASUS Prime X370-Pro (4207), ASRock B450 Pro4 (1.80), MSI B350 Tomahawk (7A34v1K), Gigabyte GA-AB350M-Gaming3 (F24c) Detailed information: AMD AGESA version "PinnaclePI-AM4 1.0.0.6" based firmware is released by many major mainboard manufacturers lately. However, this 1.0.0.6 based firmware with Raven Ridge processors (2200G, 2400G and more) cause system hangs on boot if a system is running 4.15.0 kernel. If install kernel version 4.18.0-13-generic from "linux-image-generic- hwe-18.04-edge" has no issue. Here is boot messages output (dumped via serial port and truncated): [4.385021] [drm] ring test on 5 succeeded in 3 usecs [4.385030] [drm] ring test on 6 succeeded in 2 usecs [4.385035] [drm] ring test on 7 succeeded in 1 usecs [4.385044] [drm] ring test on 8 succeeded in 2 usecs [4.385090] [drm] ring test on 10 succeeded in 2 usecs [5.406001] clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc' as unstable because the skew is too large: [5.406002] clocksource: 'hpet' wd_now: 5152d87 wd_last: 40b14df mask: [5.406004] clocksource: 'tsc' cs_now: f4c92bc9d cs_last: ebf5adbce mask: [5.406006] tsc: Marking TSC unstable due to clocksource watchdog [5.406014] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [5.406015] sched_clock: Marking unstable (5406009219, 0)<-(5548358599, -142345214) [7.906021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [9.156104] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: writing more dwords to the ring than expected! [ 11.656035] ata2.00: ATA-8: TOSHIBA DT01ACA200, MX4OABB0, max UDMA/133 [ 32.204004] watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [kworker/2:1:60] [ 32.204005] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 amdgpu(+) chash i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect uas sysimgblt fb_sys_fops drm r8169 usb_storage i2c_piix4 mii ahci libahci wmi video gpio_a ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amdgpu bot-comment -- AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot https://bugs.launchpad.net/bugs/1809934 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 1809783] Re: Bluetooth always on when power on my laptop
The bluetooth status should be store/restored by the bluez init scripts ** No longer affects: gnome-shell (Ubuntu) ** Package changed: gnome-bluetooth (Ubuntu) => bluez (Ubuntu) -- 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/1809783 Title: Bluetooth always on when power on my laptop Status in bluez package in Ubuntu: New Bug description: Bluetooth works properly but it's always turned on on startup and I have to turn it off manually ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 26 09:16:08 2018 InstallationDate: Installed on 2018-12-07 (18 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE C50-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=656a2282-422f-4307-9893-2ec8c68718dc ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.10 dmi.board.asset.tag: * dmi.board.name: ZBWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.10:bd08/10/2015:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-02N01VIT:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.version: PSCMLE-02N01VIT dmi.sys.vendor: TOSHIBA hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1809783/+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 1809783] [NEW] Bluetooth always on when power on my laptop
You have been subscribed to a public bug: Bluetooth works properly but it's always turned on on startup and I have to turn it off manually ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 26 09:16:08 2018 InstallationDate: Installed on 2018-12-07 (18 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE C50-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=656a2282-422f-4307-9893-2ec8c68718dc ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: 5.10 dmi.board.asset.tag: * dmi.board.name: ZBWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr5.10:bd08/10/2015:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-02N01VIT:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.version: PSCMLE-02N01VIT dmi.sys.vendor: TOSHIBA hciconfig: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- Bluetooth always on when power on my laptop https://bugs.launchpad.net/bugs/1809783 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1807259] Re: sky2 ethernet card doesn't work after returning from suspend
Yes, this helps. Will there be a fix for this which doesn't require to set kernel parameters? As well do you know what changed between kernel 4.13 and 4.15? I had a brief look at the sky2 driver git history in the kernel and I didn't see a suspicious related change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807259 Title: sky2 ethernet card doesn't work after returning from suspend Status in linux package in Ubuntu: Confirmed Bug description: I am on "Linux Mint 18.2 Sonya". Upgrading to Kernel 4.15.0-39.42~16.04.1 leaves the ethernet adapter inactive after resume from suspend. I reverted to a 4.13 kernel for this reason for which it works. the bug seems to be similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921. $ lshw -class network WARNUNG: Sie sollten dieses Programm mit Systemverwalterrechten (root) ausführen. *-network DEAKTIVIERT Beschreibung: Kabellose Verbindung Produkt: BCM4312 802.11b/g LP-PHY Hersteller: Broadcom Corporation Physische ID: 0 Bus-Informationen: pci@:0c:00.0 Logischer Name: wlp12s0 Version: 01 Seriennummer: 00:26:5e:33:a9:6d Breite: 64 bits Takt: 33MHz Fähigkeiten: bus_master cap_list ethernet physical wireless Konfiguration: broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334) latency=0 multicast=yes wireless=IEEE 802.11 Ressourcen: irq:17 memory:f69fc000-f69f *-network Beschreibung: Ethernet interface Produkt: 88E8040 PCI-E Fast Ethernet Controller Hersteller: Marvell Technology Group Ltd. Physische ID: 0 Bus-Informationen: pci@:09:00.0 Logischer Name: enp9s0 Version: 13 Seriennummer: 00:25:64:4a:26:00 Größe: 100Mbit/s Kapazität: 100Mbit/s Breite: 64 bits Takt: 33MHz Fähigkeiten: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation Konfiguration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full ip=192.168.1.7 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s Ressourcen: irq:24 memory:f68fc000-f68f ioport:de00(Größe=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807259/+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 1810807] [NEW] Xenial update: 4.4.163 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.163 upstream stable release
from git://git.kernel.org/
Linux 4.4.163
x86/time: Correct the attribute on jiffies' definition
l2tp: hold tunnel socket when handling control frames in l2tp_ip and l2tp_ip6
cpuidle: Do not access cpuidle_devices when !CONFIG_CPU_IDLE
x86/percpu: Fix this_cpu_read()
sched/fair: Fix throttle_list starvation with low CFS quota
Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15IGM
USB: fix the usbfs flag sanitization for control transfers
usb: gadget: storage: Fix Spectre v1 vulnerability
cdc-acm: correct counting of UART states in serial state notification
IB/ucm: Fix Spectre v1 vulnerability
RDMA/ucma: Fix Spectre v1 vulnerability
ptp: fix Spectre v1 vulnerability
cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)
ahci: don't ignore result code of ahci_reset_controller()
crypto: shash - Fix a sleep-in-atomic bug in shash_setkey_unaligned
mremap: properly flush TLB before releasing the page
rtnetlink: Disallow FDB configuration for non-Ethernet device
vhost: Fix Spectre V1 vulnerability
net: drop skb on failure in ip_check_defrag()
sctp: fix race on sctp_id2asoc
r8169: fix NAPI handling under high load
net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules
net: socket: fix a missing-check bug
net: sched: gred: pass the right attribute to gred_change_table_def()
net/ipv6: Fix index counter for unicast addresses in in6_dump_addrs
ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called
ipv6: mcast: fix a use-after-free in inet6_mc_check
net: bridge: remove ipv6 zero address check in mcast queries
bridge: do not add port to router list when receives query with source 0.0.0.0
perf tools: Disable parallelism for 'make clean'
mtd: spi-nor: Add support for is25wp series chips
fs/fat/fatent.c: add cond_resched() to fat_count_free_clusters()
ARM: dts: imx53-qsb: disable 1.2GHz OPP
MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
igb: Remove superfluous reset to PHY and page 0 selection
MIPS: microMIPS: Fix decoding of swsp16 instruction
scsi: aacraid: Fix typo in blink status
bonding: avoid defaulting hard_header_len to ETH_HLEN on slave removal
PM / devfreq: tegra: fix error return code in tegra_devfreq_probe()
ASoC: spear: fix error return code in spdif_in_probe()
spi: xlp: fix error return code in xlp_spi_probe()
spi/bcm63xx: fix error return code in bcm63xx_spi_probe()
MIPS: Handle non word sized instructions when examining frame
spi/bcm63xx-hspi: fix error return code in bcm63xx_hsspi_probe()
usb: dwc3: omap: fix error return code in dwc3_omap_probe()
usb: ehci-omap: fix error return code in ehci_hcd_omap_probe()
usb: imx21-hcd: fix error return code in imx21_probe()
gpio: msic: fix error return code in platform_msic_gpio_probe()
sparc64: Fix exception handling in UltraSPARC-III memcpy.
gpu: host1x: fix error return code in host1x_probe()
sparc64 mm: Fix more TSB sizing issues
video: fbdev: pxa3xx_gcu: fix error return code in pxa3xx_gcu_probe()
tty: serial: sprd: fix error return code in sprd_probe()
l2tp: hold socket before dropping lock in l2tp_ip{, 6}_recv()
brcmfmac: Fix glom_skb leak in brcmf_sdiod_recv_chain
gro: Allow tunnel stacking in the case of FOU/GUE
vti6: flush x-netns xfrm cache when vti interface is removed
ALSA: timer: Fix zero-division by continue of uninitialized instance
ixgbe: Correct X550EM_x revision check
ixgbe: fix RSS limit for X550
net/mlx5e: Correctly handle RSS indirection table when changing number of
channels
net/mlx5e: Fix LRO modify
ixgbevf: Fix handling of NAPI budget when multiple queues are enabled per vector
fuse: Dont call set_page_dirty_lock() for ITER_BVEC pages for async_dio
drm/nouveau/fbcon: fix oops without fbdev emulation
bpf: generally move prog destruction to RCU deferral
usb-storage: fix bogus hardware error messages for ATA pass-thru devices
sch_red: update backlog as well
sparc/pci: Refactor dev_archdata initialization into pci_init_dev_archdata
scsi: Add STARGET_CREATED_REMOVE state to scsi_target_state
xfrm: Clear sk_dst_cache when applying per-socket policy.
arm64: Fix potential race with hardware DBM in ptep_set_access_flags()
CIFS: handle guest access errors to Windows shares
ASoC: wm8940: Enable cache usage to fix crashes on resume
ASoC: ak4613: Enable cache usage to fix crashes on resume
MIPS: Fix FCSR Cause bit handling for correct SIGFPE issue
usbvision: revert commit 588afcc1
perf/core: Don't leak event in the syscall error path
aacraid: Start adapter after updating
[Kernel-packages] [Bug 1810806] [NEW] Bionic update: 4.4.163 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.163 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug -- 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/1810806 Title: Bionic update: 4.4.163 upstream stable release Status in linux package in Ubuntu: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.163 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810806/+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 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Correct. Since I have been using Deep instead of S2Idle I have seen the
issue less -- though it has only been a couple of days as I was not
using this machine over the holidays. Even when it does break, Deep
suspending and resuming the machine brings the wireless back up and
working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807974
Title:
Wireless regularly breaking (ath10k firmware crashed!) after upgrade
to Cosmic
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when
this machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has
[Kernel-packages] [Bug 1808912] Re: scsi: libsas: fix a race condition when smp task timeout
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress -- 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/1808912 Title: scsi: libsas: fix a race condition when smp task timeout Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] When the lldd is processing the complete sas task in interrupt and set the task stat as SAS_TASK_STATE_DONE, the smp timeout timer is able to be triggered at the same time. And smp_task_timedout() will complete the task wheter the SAS_TASK_STATE_DONE is set or not. Then the sas task may freed before lldd end the interrupt process. Thus a use-after-free will happen. [Test Case] This is hard to reproduce, so regression test only. [Fix] b90cd6f2b9 scsi: libsas: fix a race condition when smp task timeout [Regression Risk] Only 2 line moved in libsas and maintainer has reviewed/approved. I will say it's low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808912/+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 1719545] Re: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats
** Changed in: linux (Ubuntu) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719545 Title: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2017-06-29 02:30:22 == ---Problem Description--- cpupower monitor shows multiple stop Idle_Stats ---uname output--- Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS. Then execute the cpupower monitor command to fetch all the Idle_Stats values. root@zz376p1:~# cpupower monitor |Idle_Stats PKG |CORE|CPU | snoo | stop | stop 0| 8| 0| 0.00| 0.00| 2.79 0| 8| 1| 0.00| 0.00| 70.68 0| 8| 2| 0.00| 0.00| 99.87 0| 8| 3| 0.00| 0.00| 67.28 0| 12| 4| 0.00| 0.00| 5.17 0| 12| 5| 0.00| 0.00| 12.50 0| 12| 6| 0.00| 0.00| 99.74 0| 12| 7| 0.00| 0.00| 0.00 8|2048| 8| 0.00| 0.00| 22.14 8|2048| 9| 0.00| 0.00| 102.3 8|2048| 10| 0.00| 0.00| 0.00 8|2048| 11| 0.00| 0.00| 99.97 8|2052| 12| 0.00| 0.00| 99.70 8|2052| 13| 0.00| 0.00| 23.86 8|2052| 14| 0.00| 0.00| 113.1 8|2052| 15| 0.00| 0.00| 0.00 As can be seen it shows 2 columns for stop. root@zz376p1:~# uname -a Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@zz376p1:~# cat /etc/os-release NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial root@zz376p1:~# cat /proc/cpuinfo | tail processor : 15 cpu : POWER9 (raw), altivec supported clock : 2600.00MHz revision: 1.0 (pvr 004e 0100) timebase: 51200 platform: PowerNV model : 8375-42A machine : PowerNV 8375-42A firmware: OPAL Userspace tool common name: /usr/bin/cpupower The userspace tool has the following bit modes: 64-bit Userspace rpm: linux-tools-common Userspace tool obtained from project website: na *Additional Instructions for pavsu...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. . There are 3 idle_stats (3 states) in this system. root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s snoo [T] -> snooze stop [T] -> stop0_lite stop [T] -> stop1_lite root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 3 Available idle states: snooze stop0_lite stop1_lite snooze: Flags/Description: snooze Latency: 0 Usage: 224 Duration: 423 stop0_lite: Flags/Description: stop0_lite Latency: 0 Usage: 1685 Duration: 530522 stop1_lite: Flags/Description: stop1_lite Latency: 4 Usage: 12693 Duration: 5405898106 root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s snoo [T] -> snooze stop [T] -> stop0_lite stop [T] -> stop1_lite root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 3 Available idle states: snooze stop0_lite stop1_lite snooze: Flags/Description: snooze Latency: 0 Usage: 272 Duration: 905 stop0_lite: Flags/Description: stop0_lite Latency: 0 Usage: 2141 Duration: 536399 stop1_lite: Flags/Description: stop1_lite Latency: 4 Usage: 15396 Duration: 6625668881 cpu monitor will print the results of all the 3 available idle_stats . The first stop -> stop0_lite stats and The second stop -> stop1_lite stats. cpupower monitor header prints the header list by getting the name of the idle stats. name (name description) snoo [T] -> snooze stop [T] -> stop0_lite
[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches
Marking as Incomplete while awaiting answer to the question in comment #11. ** Changed in: ubuntu-power-systems Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760099 Title: Additional spectre and meltdown patches Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2018-03-29 08:53:56 == Hi Canonical, There are some additional patches for Spectre and Meltdown that is required on ppc64el. We would need to have them included on all Ubuntu kernels. This is the patch series: [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,08/10] powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,04/10] powerpc/powernv: Set or clear security feature flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,03/10] powerpc/pseries: Set or clear security feature flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown http://patchwork.ozlabs.org/project/linuxppc- dev/list/?series=36012=* == Comment: #1 - Breno Leitao - 2018-03-29 08:55:48 == This is a better formatted patch series list: [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1() [v2,08/10] powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus() [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown() [v2,05/10] powerpc/64s: Move cpu_show_meltdown() [v2,04/10] powerpc/powernv: Set or clear security feature flags [v2,03/10] powerpc/pseries: Set or clear security feature flags [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1760099/+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 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Do you mean the issue happen less frequently when using S3 instead of
S2Idle? I thought this should be the other way around.
--
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/1807974
Title:
Wireless regularly breaking (ath10k firmware crashed!) after upgrade
to Cosmic
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when
this machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has appeared/become much worse on Cosmic.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-11-generic 4.18.0-11.12
ProcVersionSignature:
[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Uploaded phase-changed: Monday, 07. January 2019 10:00 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed -- 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/1810370 Title: linux-oem: 4.15.0-1031.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Uploaded phase-changed: Monday, 07. January 2019 10:00 UTC reason: promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+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 1810392] Re: [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops inside guest
Assigning to kernel team initially, although this may be a qemu/libvirt 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/1810392 Title: [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops inside guest Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Migrating back Power9 to source cause Kernel Oops inside guest Contact Information = Balamuruhan S / balamuruh...@in.ibm.com ---uname output--- source and target host Kernel: 4.18.0-8-generic Guest Kernel: 4.18.0-8-generic Machine Type = Boston ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Due to Bug 172310, Turn off the firewalld in source and target host machines. 1. Define a healthy guest and placed image in NFS share. 2. Mounted the image location in destination and start the guest to perform migration. 3. Perform migration from source to target, 08:07:54 INFO | Migrating VM avocado-vt-vm1-migration from qemu:///system to qemu+ssh://9.40.194.13/system 08:07:54 DEBUG| Running virsh command: migrate --live --domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60 08:07:54 INFO | Running '/usr/bin/virsh -c 'qemu:///system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60' 08:08:21 DEBUG| [stdout] 08:08:21 INFO | Command '/usr/bin/virsh -c 'qemu:///system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60' finished with 0 after 26.9465551376s 08:08:21 DEBUG| status: 0 08:08:21 DEBUG| stdout: 08:08:21 DEBUG| stderr: 08:08:21 INFO | Migration exit status: 0 4. check VM uptime after successful migration, 08:07:44 INFO | Check VM uptime before migration: 57.66 5. Migration is successful from source to destination, now perform migration back to source 08:08:49 INFO | Migrating VM avocado-vt-vm1-migration from qemu+ssh://9.40.194.13/system to qemu:///system 08:08:49 DEBUG| Running virsh command: migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system --timeout 60 08:08:49 INFO | Running '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system --timeout 60' 08:09:22 DEBUG| [stdout] 08:09:22 INFO | Command '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system --timeout 60' finished with 0 after 32.8640539646s 08:09:22 DEBUG| status: 0 08:09:22 DEBUG| stdout: 08:09:22 DEBUG| stderr: 08:09:22 INFO | Migration exit status: 0 6. check uptime of VM after migration and it is observed that VM have gone for reboot 08:10:22 INFO | Check VM uptime after migrating back to source: 31.09 5. By checking the VM console Call Trace is observed as mentioned below The time stamp during the call trace observed inside guest matches with the timestamp during which migration is triggered. Stack trace output: no Attachment: 1. VM sosreport 2. source and target sosreport 3. VM console log with call trace 4. Guest xml 5. Test job log Oops output: 2018-10-26 08:08:26: root@ubuntu1810:~# 2018-10-26 08:09:11: [ 144.512549] Unable to handle kernel paging request for data at address 0x71ff9672fa0e0989 2018-10-26 08:09:11: [ 144.512655] Faulting instruction address: 0xc03af7cc 2018-10-26 08:09:11: [ 144.512741] Oops: Kernel access of bad area, sig: 11 [#1] 2018-10-26 08:09:11: [ 144.512789] LE SMP NR_CPUS=2048 NUMA pSeries 2018-10-26 08:09:11: [ 144.512859] Modules linked in: iscsi_target_mod target_core_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter kvm dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel nfsd ib_iser auth_rpcgss rdma_cm nfs_acl iw_cm lockd ib_cm grace ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear virtio_net net_failover crc32c_vpmsum virtio_blk virtio_scsi failover 2018-10-26 08:09:11: [ 144.513801] CPU: 5 PID: 1072 Comm: systemd-network Not tainted 4.18.0-8-generic #9-Ubuntu 2018-10-26 08:09:11: [ 144.513872] NIP: c03af7cc LR: c03af7b8 CTR: c0c9ea80 2018-10-26 08:09:11: [ 144.513943] REGS: c000f19ab910 TRAP: 0380 Not tainted (4.18.0-8-generic) 2018-10-26
[Kernel-packages] [Bug 1810392] Re: [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops inside guest
IBM, is this reproducible with the latest Bionic 4.18 kernel as well ? ** Changed in: ubuntu-power-systems Status: New => Triaged -- 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/1810392 Title: [Ubuntu 1810] Migrating Power9 guest back to source causes kernel Oops inside guest Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Migrating back Power9 to source cause Kernel Oops inside guest Contact Information = Balamuruhan S / balamuruh...@in.ibm.com ---uname output--- source and target host Kernel: 4.18.0-8-generic Guest Kernel: 4.18.0-8-generic Machine Type = Boston ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Due to Bug 172310, Turn off the firewalld in source and target host machines. 1. Define a healthy guest and placed image in NFS share. 2. Mounted the image location in destination and start the guest to perform migration. 3. Perform migration from source to target, 08:07:54 INFO | Migrating VM avocado-vt-vm1-migration from qemu:///system to qemu+ssh://9.40.194.13/system 08:07:54 DEBUG| Running virsh command: migrate --live --domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60 08:07:54 INFO | Running '/usr/bin/virsh -c 'qemu:///system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60' 08:08:21 DEBUG| [stdout] 08:08:21 INFO | Command '/usr/bin/virsh -c 'qemu:///system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu+ssh://9.40.194.13/system --timeout 60' finished with 0 after 26.9465551376s 08:08:21 DEBUG| status: 0 08:08:21 DEBUG| stdout: 08:08:21 DEBUG| stderr: 08:08:21 INFO | Migration exit status: 0 4. check VM uptime after successful migration, 08:07:44 INFO | Check VM uptime before migration: 57.66 5. Migration is successful from source to destination, now perform migration back to source 08:08:49 INFO | Migrating VM avocado-vt-vm1-migration from qemu+ssh://9.40.194.13/system to qemu:///system 08:08:49 DEBUG| Running virsh command: migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system --timeout 60 08:08:49 INFO | Running '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system --timeout 60' 08:09:22 DEBUG| [stdout] 08:09:22 INFO | Command '/usr/bin/virsh -c 'qemu+ssh://9.40.194.13/system' migrate --live --domain avocado-vt-vm1-migration --desturi qemu:///system --timeout 60' finished with 0 after 32.8640539646s 08:09:22 DEBUG| status: 0 08:09:22 DEBUG| stdout: 08:09:22 DEBUG| stderr: 08:09:22 INFO | Migration exit status: 0 6. check uptime of VM after migration and it is observed that VM have gone for reboot 08:10:22 INFO | Check VM uptime after migrating back to source: 31.09 5. By checking the VM console Call Trace is observed as mentioned below The time stamp during the call trace observed inside guest matches with the timestamp during which migration is triggered. Stack trace output: no Attachment: 1. VM sosreport 2. source and target sosreport 3. VM console log with call trace 4. Guest xml 5. Test job log Oops output: 2018-10-26 08:08:26: root@ubuntu1810:~# 2018-10-26 08:09:11: [ 144.512549] Unable to handle kernel paging request for data at address 0x71ff9672fa0e0989 2018-10-26 08:09:11: [ 144.512655] Faulting instruction address: 0xc03af7cc 2018-10-26 08:09:11: [ 144.512741] Oops: Kernel access of bad area, sig: 11 [#1] 2018-10-26 08:09:11: [ 144.512789] LE SMP NR_CPUS=2048 NUMA pSeries 2018-10-26 08:09:11: [ 144.512859] Modules linked in: iscsi_target_mod target_core_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter kvm dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel nfsd ib_iser auth_rpcgss rdma_cm nfs_acl iw_cm lockd ib_cm grace ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear virtio_net net_failover crc32c_vpmsum virtio_blk virtio_scsi failover 2018-10-26 08:09:11: [ 144.513801] CPU: 5 PID: 1072 Comm: systemd-network Not tainted 4.18.0-8-generic #9-Ubuntu 2018-10-26 08:09:11: [ 144.513872] NIP: c03af7cc LR: c03af7b8 CTR: c0c9ea80 2018-10-26 08:09:11: [ 144.513943] REGS: c000f19ab910 TRAP:
[Kernel-packages] [Bug 1810619] Re: Sleep mode doesn't work
When I do some test, the screen goes off but the laptop doesn't seems to enter in sleep mode. The battery continue to discharge after enter in sleep mode : 39% when I stopped to work and 0% a few hours after (9 hours). Fans are stopped. With : sudo sh -c 'echo disabled > /sys/bus/serio/devices/serio0/power/wakeup' Entering in sleep mode make a shutdown directly. I've no hibernation option on my kubuntu 18.10. Thanks for explications -- 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/1810619 Title: Sleep mode doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with linux-image-4.18.0-13. The screen goes off correctly but any touch resume the laptop. This is the log : Jan 5 11:15:25 skeleton systemd[1]: Reached target Sleep. Jan 5 11:15:25 skeleton systemd[1]: Starting Suspend... Jan 5 11:15:25 skeleton systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 5 11:15:25 skeleton systemd-sleep[6229]: Suspending system... Jan 5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle) an 5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 5 11:15:25 skeleton systemd[1]: Started Network Manager Script Dispatcher Service. Jan 5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 scripts) Jan 5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running ordered scripts... [...] Resume : Jan 5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... done. Jan 5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes ... (elapsed 0.088 seconds) done. Jan 5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled. Jan 5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use no_console_suspend to debug) Jan 5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled. Jan 5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done. Jan 5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 enxe4b97acfa7e9: carrier on Jan 5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 4.18.0-12). Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810619/+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 1810781] Re: mpt3sas - driver using the wrong register to update a queue index in FW
** Description changed: [Impact] * Adapter resets periodically during high-load activity. * I/O stalls until reset/reinit is complete (latency) and I/O performance degrades across cluster (e.g., low throughput from data spread over nodes). * The mpt3sas driver relies in a FW queue (Reply Post Descriptor Queue) in the I/O completion path; there's a MMIO register that driver uses to flag an empty entry in such queue, called Reply Post Host Index. This value is updated during the driver interrupt routine [in _base_interrupt() function]. * Happens that there are 2 registers representing the Reply Post Host Index according to the type of the adapter. They are differentiated in the driver through the "ioc->combined_reply_queue" check. By the MPI specification (vendor spec), driver should use this combined reply queue according to the number of maximum MSI-X vectors that the adapter exposes and the spec version (SAS 3.0 vs SAS 3.5). * Currently, this is wrong checked for a class of adapters, which was fixed in the upstream kernel commit 2b48be65685a [0]. Without this commit, we can observe spontaneous resets in the driver due to queue overflow (FW is not aware that there are free entries in the Reply Post Descriptor Queue). The dmesg log will show the following output in case of this error: mpt3sas_cm0: fault_state(0x2100)! mpt3sas_cm0: sending diag reset !! mpt3sas_cm0: diag reset: SUCCESS [followed by a lot of driver messages as result of the reset procedure] * During these resets, I/O is stalled so it may affect performance. [Test Case] * It's not trivial to test the problem, but given a machine with an affected device, an I/O benchmark like FIO could be used to exercise the - I/O path in a heavy way and trigger the issue. We have reports that the - adapter "LSI Logic / Symbios Logic Device [1000:00ac]" is affected by - the issue. + I/O path in a heavy way and trigger the issue. + + * We have reports that the adapter "LSI Logic / Symbios Logic Device + [1000:00ac]" is affected by the issue. And this commit resolved the + problem. [Regression Potential] * This is a long-term issue from the mpt3sas driver, affecting only a - class of adapters of this vendor. Since it's a clear bug, the fix is + class of adapters of this vendor. Since it's a clearly bug, the fix is necessary. The potential of regressions is unknown, but likely low - it changes the register used for the index updates given some set of characteristics of the adapter (according to the spec.), which restricts even more the scope of this patch. -- 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/1810781 Title: mpt3sas - driver using the wrong register to update a queue index in FW Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Bug description: [Impact] * Adapter resets periodically during high-load activity. * I/O stalls until reset/reinit is complete (latency) and I/O performance degrades across cluster (e.g., low throughput from data spread over nodes). * The mpt3sas driver relies in a FW queue (Reply Post Descriptor Queue) in the I/O completion path; there's a MMIO register that driver uses to flag an empty entry in such queue, called Reply Post Host Index. This value is updated during the driver interrupt routine [in _base_interrupt() function]. * Happens that there are 2 registers representing the Reply Post Host Index according to the type of the adapter. They are differentiated in the driver through the "ioc->combined_reply_queue" check. By the MPI specification (vendor spec), driver should use this combined reply queue according to the number of maximum MSI-X vectors that the adapter exposes and the spec version (SAS 3.0 vs SAS 3.5). * Currently, this is wrong checked for a class of adapters, which was fixed in the upstream kernel commit 2b48be65685a [0]. Without this commit, we can observe spontaneous resets in the driver due to queue overflow (FW is not aware that there are free entries in the Reply Post Descriptor Queue). The dmesg log will show the following output in case of this error: mpt3sas_cm0: fault_state(0x2100)! mpt3sas_cm0: sending diag reset !! mpt3sas_cm0: diag reset: SUCCESS [followed by a lot of driver messages as result of the reset procedure] * During these resets, I/O is stalled so it may affect performance. [Test Case] * It's not trivial to test the problem, but given a machine with an affected device, an I/O benchmark like FIO could be used to exercise the I/O path in a heavy way and trigger the issue. * We
[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- 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/1810370 Title: linux-oem: 4.15.0-1031.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Uploaded phase-changed: Monday, 07. January 2019 10:00 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+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 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Uploaded phase-changed: Monday, 07. January 2019 10:00 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- 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/1810370 Title: linux-oem: 4.15.0-1031.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Uploaded phase-changed: Monday, 07. January 2019 10:00 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+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 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Done, thanks Kai-Heng. How can I check I'm using the new versions?
$ dmesg | grep ath10k
[ 15.152725] ath10k_pci :02:00.0: enabling device ( -> 0002)
[ 15.154816] ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[ 15.436782] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id
0x00340aff sub 1a56:143a
[ 15.436784] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[ 15.437201] ath10k_pci :02:00.0: firmware ver
RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features
wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a
[ 15.502002] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 16.081468] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 16.084029] ath10k_pci :02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1
[ 16.176519] ath10k_pci :02:00.0 wlp2s0: renamed from wlan0
[ 19.218623] ath10k_pci :02:00.0: Unknown eventid: 118809
I will let you know how I get on. Even before loading the new firmware I
am seeing this issue far less frequently (only twice so far today) since
I changed s2idle to deep sleep (Bug #1808957), so I suspect it does
relate to idle/power saving.
--
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/1807974
Title:
Wireless regularly breaking (ath10k firmware crashed!) after upgrade
to Cosmic
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681]
[Kernel-packages] [Bug 1810636] Re: QCA6174 doesn't utilise btcoex - Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570
Subscribed ath10k maintainer. I think he uses Launchpad, but if he doesn't reply here, please raise this issue to linux- wirel...@vger.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/1810636 Title: QCA6174 doesn't utilise btcoex - Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570 with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness ever since I have owned this laptop. This problem has persisted for me with previous kernels. If I disable wifi and use media on machine locally, the problem doesn't occur. Note: I've reverted back v4.18.0-13-generic and reproduced the problem for the apport-collect report. It started with Ubuntu 18.04 and continues with 18.10. It's particularly noticeable when the when saturating the WLAN connection with throughput, i.e. copying a large file sequentially across from a samba share, but also streaming video online results in the audio progressively delaying over-time. Re-establishing the Bluetooth audio sync restores the sync, but slowly creeps out again. I've upgraded my linux-firmware package to disco 176 to match v4.20 kernel drivers ref: https://launchpad.net/ubuntu/+source/linux- firmware/1.176 The ath10k_core driver that supports this device has a reference for btcoex: ref https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598 It's possible that the Bluetooth component firmware is not supporting or communicating btcoex compatibility, but this is starting to reach the edge of my ability to diagnose the problem. This btcoex support in ath9k has resolved/improved the Bluetooth bandwidth problem for older Qualcomm chipsets as shown in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164 As a troubleshooting step, I've also tried the very latest firmware-6 file from, but I'm continuing to experience the problem ref: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berg 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-07-02 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c825a7b0-a5ac-41de-bd57-7663fef8a1f1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.176 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (79 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07GHH0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810636/+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 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
Now it's a different issue. The original issue, which is the system gets woken up early by btusb, seems to be solved. I don't see "PM: Device :00:14.0 failed to suspend async: error -16" in your new message. So does this issue happen when Bluetooth is completely disabled? -- 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/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Bug description: I have XPS9370 with self-installed Ubuntu 18.10 (not project sputnik) with Killer 1435 wireless module. And sometimes I find wifi and bluetooth missing after sleep. I cannot exactly define preconditions, but it seems there are following steps to reproduce the issue 1. Connect something via bluetooth (I use bluetooth headset) 2. Send laptop to sleep 3. Wake it and find wifi and bluetooth missing. I have to mention that I have also been experienced bluetooth only missing, but it somehow transformed to the issue with both wireless devices. Dmesg after waking up with the issue attached --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kao2362 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-22 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=34230cbd-d3d2-4cb8-855a-307883bc35ea ro quiet splash mem_sleep_default=deep video=1920x1080 usbcore.dyndbg=+p vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0VM1FG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0VM1FG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+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
