[Kernel-packages] [Bug 1879658] Re: Cannot create ipvlans with > 1500 MTU on recent Bionic kernels
** Changed in: linux (Ubuntu Bionic) 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/1879658 Title: Cannot create ipvlans with > 1500 MTU on recent Bionic kernels Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [IMPACT] Setting an MTU larger than the default 1500 results in an error on the recent (4.15.0-92+) Bionic/Xenial -hwe kernels when attempting to create ipvlan interfaces: # ip link add test0 mtu 9000 link eno1 type ipvlan mode l2 RTNETLINK answers: Invalid argument This breaks Docker and other applications which use a Jumbo MTU (9000) when using ipvlans. The bug is caused by the following recent commit to Bionic & Xenial-hwe; which is pulled in via the stable patchset below, which enforces a strict min/max MTU when MTUs are being set up via rtnetlink for ipvlans: Breaking commit: --- Ubuntu-hwe-4.15.0-92.93~16.04.1 * Bionic update: upstream stable patchset 2020-02-21 (LP: #1864261) * net: rtnetlink: validate IFLA_MTU attribute in rtnl_create_link() The above patch applies checks of dev->min_mtu and dev->max_mtu to avoid a malicious user from crashing the kernel with a bad value. It was patching the original patchset to centralize min/max MTU checking from various different subsystems of the networking kernel. However, in that patchset, the max_mtu had not been set to the largest phys (64K) or jumbo (9000 bytes), and defaults to 1500. The recent commit above which enforces strict bounds checking for MTU size exposes the bug of the max mtu not being set correctly for the ipvlan driver (this has been previously fixed in bonding, teaming drivers). Fix: --- This was fixed in the upstream kernel as of v4.18-rc2 for ipvlans, but was not backported to Bionic along with other patches. The missing commit in the Bionic backport: ipvlan: use ETH_MAX_MTU as max mtu commit 548feb33c598dfaf9f8e066b842441ac49b84a8a [Test Case] 1. Install any kernel earlier than 4.15.0-92 (Bionic/Xenial-hwe) 2. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2 (where test1 eno1 is the physical interface you are adding the ipvlan on) 3. # ip link ... 14: test1@eno1: mtu 9000 qdisc noop state DOWN mode DEFAULT group default qlen 1000 ... // check that your test1 ipvlan is created with mtu 9000 4. Install 4.15.0-92 kernel or later 5. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2 RTNETLINK answers: Invalid argument 6. With the above fix commit backported to the xenial-hwe/Bionic, the jumbo mtu ipvlan creation works again, identical to before 92. [Regression Potential] This commit is in upstream mainline as of v4.18-rc2, and hence is already in Cosmic and later, i.e. all post Bionic releases currently. Hence there's low regression potential here. It only impacts ipvlan functionality, and not other networking systems, so core systems should not be affected by this. And affects on setup so it either works or doesn't. Patch is trivial. It only impacts Bionic/Xenial-hwe 4.15.0-92 onwards versions (where the latent bug got exposed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879321] Re: Fix Pericom USB controller OHCI/EHCI PME# defect
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879321 Title: Fix Pericom USB controller OHCI/EHCI PME# defect Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-oem-5.6 source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] Pericom EHCI/OHCI USB Controller can't detect hotplug event when it's runtime-suspended, due to its unreliable PME#. [Fix] Disable PME for all its power state since all of them don't work reliably. [Test] Hotplugging event can be reliably detected by the device, after the fix gets applied. [Regression Potentia] Low. This targets specific device, without touching any logic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1879321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Please test below. hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7774 hda-verb /dev/snd/hwC0D0 0x20 0x500 0x45 hda-verb /dev/snd/hwC0D0 0x20 0x400 0x5289 I think Headset Mic should be worked. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] Re: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: == [Impact] * Mellanox CX5 port multi-pathing is broken on s390x due to non- standard topology of PCI IDs (phys. and virtual) * The Mellanox Connect-X 5 PCI driver (mlx5) implements multi-path that can be used to combine multiple networking ports to improve performance and reliability. * For that purpose, the mlx5 driver combines PCI functions based on topology information (the function number) as determined by their PCI ID. * Currently the Linux on Z PCI bus does not reflect PCI topology information in the PCI ID. As a result, the mlx5 multi-path function is broken and cannot be activated. [Fix] * Backport 1: https://launchpadlibrarian.net/479699471/0001-s390-pci- Improve-handling-of-unset-UID.patch * Backport 2: https://launchpadlibrarian.net/479699482/0002-s390-pci- embedding-hotplug_slot-in-zdev.patch * Backport 3: https://launchpadlibrarian.net/479699492/0003-s390-pci- Expose-new-port-attribute-for-PCIe-function.patch * Backport 4: https://launchpadlibrarian.net/479699497/0004-s390-pci- adaptation-of-iommu-to-multifunction.patch * Backport 5: https://launchpadlibrarian.net/479700706/0005-s390-pci- define-kernel-parameters-for-PCI-multifunct.patch * Backport 6: https://launchpadlibrarian.net/479700712/0006-s390-pci- define-RID-and-RID-available.patch * Backport 7: https://launchpadlibrarian.net/479700739/0007-s390-pci- create-zPCI-bus.patch * Backport 8: https://launchpadlibrarian.net/479700769/0008-s390-pci- adapt-events-for-zbus.patch * Backport 9: https://launchpadlibrarian.net/479700786/0009-s390-pci- Handling-multifunctions.patch * Backport 10: https://launchpadlibrarian.net/479700794/0010-s390-pci- Do-not-disable-PF-when-VFs-exist.patch * Backport 11: https://launchpadlibrarian.net/479700798/0011-s390-pci- Documentation-for-zPCI.patch * Backport 12: https://launchpadlibrarian.net/479700799/0012-s390-pci- removes-wrong-PCI-multifunction-assignment.patch [Test Case] * Prepare an IBM z13 or LinuxONE III (or newer) system with two or more RoCE Express PCI 2(.1) adapters. * Assign the adapters (and it's virtual functions) to an LPAR. * Verify whether the physical and virtual functions are grouped in arbitrary order or in consecutive order - physical first (for example with lspci -t ...) [Regression Potential] * The regression potential can be considered as moderate, since: * It is purely s390x specific code (arch/s390/* drivers/iommu/s390-iommu.c and drivers/pci/hotplug/s390_pci_hpc.c - and some doc adjustments, too). * It largely affects zPCI, the s390x specific PCI code layer. * PCI cards available for s390x are optional cards (RoCE and zEDC) and not very wide-spread. * The situation described above affects the RoCE adapters only (Mellanox based). * The patches are also upstream accepted and available via linux-next, but to apply them to focal kernel 5.4 the above backports are needed. * However, the code is modified by several patches (12), hence there is a chance to break zPCI with them. * For upfront testing a PPA got created with a focal (master-next) kernel that incl. all the above patches. __ Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1
[Kernel-packages] [Bug 1879688] Re: shiftfs: fix btrfs snapshot deletion
** Changed in: linux (Ubuntu Eoan) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879688 Title: shiftfs: fix btrfs snapshot deletion Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Bug description: SRU Justification Impact: Stéphane discovered a problem during NorthSec which makes heavy use of shiftfs. In containers with a btrfs root filesystem that make use of shiftfs userns root is not able to delete subvolumes that have been created by another users which it would be able to do otherwise. This makes it impossible for LXD to delete nested containers. To reproduce this as root in the container: btrfs subvolume create my-subvol chown 1000:1000 my-subvol btrfs subvolume delete my-subvol The deletion will fail when it should have succeeded. Fix: For improved security we drop all capabilities before we forward btrfs ioctls in shiftfs. To fix the above problem we can retain the CAP_DAC_OVERRIDE capability only if we are userns root. Regression Potential: Limited to shiftfs. Even though we drop all capabilities in all capability sets we really mostly care about dropping CAP_SYS_ADMIN and we mostly do this for ioctl that e.g. allow you to traverse the btrfs filesystem and with CAP_SYS_ADMIN retained in the underlay would allow you to list subvolumes you shouldn't be able to list. This fix only retains CAP_DAC_OVERRIDE and only for the deletion of subvolumes and only by userns root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Focal) 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff
[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
First I would need some feedback that this is indeed fixing the problem. PPA is for maintaining software outside of the repos, I don't intend to maintain it, the ubuntu team needs to fix this, which they should be able to do easily if there is a 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/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878480] Re: Centrino Wireless-N 1000 [Condor Peak]
Ok, please test kernel v4.15, which is used in 18.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/1878480 Title: Centrino Wireless-N 1000 [Condor Peak] Status in linux package in Ubuntu: Incomplete Bug description: After upgrade to 20.04 my wireless starts to be very unstable, it goes from 65mbs to 1mbs. I need to reenable wirless ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 2846 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 20:57:07 2020 HibernationDevice: RESUME=UUID=0f71c458-758c-439d-9dd0-b7ddcd620218 MachineType: Alienware M14xR1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=fcba8370-4563-4d59-8a53-f1a70ebb8e1d ro quiet splash nouveau.blacklist=1 nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2011 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: M14xR1 dmi.board.vendor: Alienware dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd12/24/2011:svnAlienware:pnM14xR1:pvrA08:rvnAlienware:rnM14xR1:rvrA08:cvnAlienware:ct8:cvrA08: dmi.product.family: 103C_5335KV dmi.product.name: M14xR1 dmi.product.sku: xxx123x#ABA dmi.product.version: A08 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839124] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle
This should be fixed in Linux v5.6. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839124 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: A generic issue which happens on Intel BT(8087:0aaa) and Atheros BT(0cf3:e005)(0cf3:e007). Once the system has paired with BT4 devices(disconnected), the system will be waken up randomly from S3/s2idle while receiving advertising packet from any random BT4 devices in the environment which are even not paired/connected. By removing all previously paired BT4 devices(disconnected) from BT menu can fix this issue. The advertising packet could be none connectable undirected or connectable undirected. And the BT4 devices we found can reproduce this issue are 1. Microsoft Surface 1678 2. Logitech K375s 3. Microsoft Designer Mouse --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1539 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0FN010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle
Dean, Can you please attach the output of the following command: # cat /sys/kernel/debug/pmc_core/package_cstate_show I suspect the package stays at PC2/PC3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881601 Title: Fan excessively runs, even when idle Status in linux package in Ubuntu: In Progress Bug description: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Ok, can you please blacklist elan_i2c and try again? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882008] 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/1882008 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 Status in linux package in Ubuntu: Confirmed Bug description: terminal says to "apt --fix broken install" doing that doesnt work ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: linux-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaswat1593 F pulseaudio /dev/snd/controlC0: shaswat1593 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 4 09:48:47 2020 DpkgHistoryLog: Start-Date: 2020-06-04 09:48:45 Commandline: apt --fix-broken install Requested-By: shaswat (1000) Install: linux-tools-common:amd64 (5.4.0-33.37, automatic) DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.4.0-33.37_all.deb ... Unpacking linux-tools-common (5.4.0-33.37) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-33.37_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 InstallationDate: Installed on 2020-05-06 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E1-472 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=315e55da-ed68-4b87-882f-3732bfb41034 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.08 dmi.board.name: EA40_HW dmi.board.vendor: Acer dmi.board.version: V2.08 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.08 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.08:bd10/14/2013:svnAcer:pnAspireE1-472:pvrV2.08:rvnAcer:rnEA40_HW:rvrV2.08:cvnAcer:ct9:cvrV2.08: dmi.product.family: Aspire E1-472 dmi.product.name: Aspire E1-472 dmi.product.sku: Aspire E1-472_0762_2.08 dmi.product.version: V2.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882012] 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 1882012 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/1882012 Title: Dependency issue for 3.2 linux-lowlatency meta package Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: When trying to install linux-lowlatency package on Precise 3.2, it will fail with: The following packages have unmet dependencies: linux-lowlatency : Depends: linux-headers-lowlatency (= 3.2.0.82.69) but it is not going to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Ok, it's LP: #1874464. Does this issue also happen on System76 platforms? In addition to L1.1, does it help if L1.2 gets 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Incomplete Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d4016fe38 EFLAGS: 0246 ORIG_RAX: ff13 Apr 2
[Kernel-packages] [Bug 1882012] [NEW] Dependency issue for 3.2 linux-lowlatency meta package
Public bug reported: When trying to install linux-lowlatency package on Precise 3.2, it will fail with: The following packages have unmet dependencies: linux-lowlatency : Depends: linux-headers-lowlatency (= 3.2.0.82.69) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 3.2 kqa-blocker precise sru-20200518 ** Tags added: 3.2 kqa-blocker precise sru-20200518 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882012 Title: Dependency issue for 3.2 linux-lowlatency meta package Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: When trying to install linux-lowlatency package on Precise 3.2, it will fail with: The following packages have unmet dependencies: linux-lowlatency : Depends: linux-headers-lowlatency (= 3.2.0.82.69) but it is not going to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Jeremy, the link you provided is the same as 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Incomplete Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d4016fe38 EFLAGS: 0246 ORIG_RAX: ff13 Apr 23 10:07:43 surprise kernel: RAX: 8a758ee6ad00 RBX: b4d69160 RCX:
[Kernel-packages] [Bug 1882008] [NEW] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common
Public bug reported: terminal says to "apt --fix broken install" doing that doesnt work ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: linux-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaswat1593 F pulseaudio /dev/snd/controlC0: shaswat1593 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 4 09:48:47 2020 DpkgHistoryLog: Start-Date: 2020-06-04 09:48:45 Commandline: apt --fix-broken install Requested-By: shaswat (1000) Install: linux-tools-common:amd64 (5.4.0-33.37, automatic) DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.4.0-33.37_all.deb ... Unpacking linux-tools-common (5.4.0-33.37) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-33.37_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 InstallationDate: Installed on 2020-05-06 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E1-472 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=315e55da-ed68-4b87-882f-3732bfb41034 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.08 dmi.board.name: EA40_HW dmi.board.vendor: Acer dmi.board.version: V2.08 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.08 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.08:bd10/14/2013:svnAcer:pnAspireE1-472:pvrV2.08:rvnAcer:rnEA40_HW:rvrV2.08:cvnAcer:ct9:cvrV2.08: dmi.product.family: Aspire E1-472 dmi.product.name: Aspire E1-472 dmi.product.sku: Aspire E1-472_0762_2.08 dmi.product.version: V2.08 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882008 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 Status in linux package in Ubuntu: New Bug description: terminal says to "apt --fix broken install" doing that doesnt work ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: linux-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaswat1593 F pulseaudio /dev/snd/controlC0: shaswat1593 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 4 09:48:47 2020 DpkgHistoryLog: Start-Date: 2020-06-04 09:48:45 Commandline: apt --fix-broken install Requested-By: shaswat (1000) Install: linux-tools-common:amd64 (5.4.0-33.37, automatic) DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.4.0-33.37_all.deb ... Unpacking linux-tools-common (5.4.0-33.37) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-33.37_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 InstallationDate: Installed on 2020-05-06 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E1-472 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=315e55da-ed68-4b87-882f-3732bfb41034 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
[Kernel-packages] [Bug 1879949] Re: NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can not log in: Failed to acquire modesetting permission
** Summary changed: - Can not log in + NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can not log in: Failed to acquire modesetting permission -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879949 Title: NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can not log in: Failed to acquire modesetting permission Status in linux package in Ubuntu: Incomplete Bug description: I'm on Ubuntu 20.04. After upgrading from linux 5.4.0-26-generic to 5.4.0-31-generic I could not log in anymore. I was stuck in the display manager. Then I rebooted into the old kernel and sent these reports. I'm not sure if this is related but I can't put my display onto the correct resolution anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jesko 3203 F pulseaudio /dev/snd/controlC1: jesko 3203 F pulseaudio /dev/snd/controlC2: jesko 3203 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:07:25 2020 InstallationDate: Installed on 2020-05-20 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B79 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=9f451f12-4a89-4dcc-9eca-97df16101efc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PLUS (MS-7B79) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd11/16/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B79 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
This is also in unstable now. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Won't Fix Status in linux source package in Eoan: Invalid Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] External monitor connected via a Type-C dongle when device is in PC10 may not be light up. [Fix] Patches series https://patchwork.freedesktop.org/series/75941/ from intel-gfx mailing list, which has been merged in drm-tip tree with tip commit 0f8925090ac7. [Test Case] 1. Ensure device may enter PC10. $ sudo powertop --auto-tune $ sudo watch cat /sys/kernel/debug/pmc_core/package_cstate_show Press Meta+L to lock screen for a while and unlock again, "Package C10" field should have non-zero counts. 2. Press Meta+L to lock screen again. 3. After screen turns black and wait a few more seconds, connect external monitor to a type C port via a type C dongle and wake the device. 4. Check if external monitor is also light up as an extended/mirrored screen. [Regression Potential] Medium. == Original Bug Description == When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 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-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/2
Re: [Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
That is not an easy answer. In the world of UCS, there are several factors that can affect this: 1) Type of IOM (I/O Module) 2) Port config of the IOM (single link or port-channel) 3) Number of inks from the Fabric Interconnect to said IOM 4) Model of adapter in the blade. Depending on the combination of these things, it can be a 10, 20, or 40 GB link. On Wed, Jun 3, 2020, 9:40 PM Lee Trager <1881...@bugs.launchpad.net> wrote: > MAAS 2.7 introduced network testing. As part of network testing we added > the following features which require accurate interface and link speed > information. > > 1. The interface and uplink speeds are now shown in the API and over the > UI. > 2. MAAS now warns when an interface is connected to an uplink which is > slower than its maximum supported speed. > 3. Users may now acquire machines based on its uplink speed. > > I could stop verifying that link speed >= max interface speed however > that will mean 1 is incorrect and 2 is broken. I understand that some > interfaces achieve higher speeds by using more physical ports but > neither ethtool nor LXD give any information on this. > > Does anyone know the proper way to calculate the maximum supported > interface speed on a device like this? > > ** Summary changed: > > - Kernel does not report interface speed correctly for Cisco UCS B200 M5 > blade > + MAAS does not properly detect max interface speed for interfaces which > use multiple phyiscal ports(Cisco UCS B200 M5 blade) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1881821 > > Title: > MAAS does not properly detect max interface speed for interfaces which > use multiple phyiscal ports(Cisco UCS B200 M5 blade) > > Status in MAAS: > Triaged > Status in MAAS 2.7 series: > Triaged > Status in MAAS 2.8 series: > Triaged > Status in linux package in Ubuntu: > Confirmed > > Bug description: > MAAS 2.7.1 > Ubuntu 18.04.4 > > When attempting to commission a Cisco UCS B200 M5 blade, the > commissioning finishes (if smartctl-validate is disabled), however on > the machine in question in the Networking tab, it only shows 2 nics, > eth0 and eth1. and shows no storage. > > Going to SSH in the middle of commissioning, running lshw shows all 10 > NICs, and the disk of the proper size. > > This is causing the buckets.yaml for FCE to be inaccurate, and thus > cannot write a bucketsconfig.yaml since the actual devices don't show > up. > > This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for > commissioning, all have the same behavior. > > I was previously hitting this bug > https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from > comment #10, and am no longer getting any commissioning errors. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: MAAS does not properly detect max interface speed for interfaces which use multiple phyiscal ports(Cisco UCS B200 M5 blade) Status in MAAS: Triaged Status in MAAS 2.7 series: Triaged Status in MAAS 2.8 series: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881909] Re: Screen tearing [Optimus - GeForce 610m]
** Tags added: tearing ** Summary changed: - Screen tearing [Optimus - GeForce 610m] + Screen tearing with Nvidia Optimus ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1881909 Title: Screen tearing with Nvidia Optimus Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I have screen tearing when using nvidia card with 390 driver, affect browsers such as firefox and chromium also desktop since I have screen tearing when moving window around. I have no such problem when using using 18.04.4 and nvidia card with 390 driver. Intel graphic have no such problem weather in 18.04 or 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 21:18:49 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652] InstallationDate: Installed on 2020-06-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK Computer Inc. K43SD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SD.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K43SD 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.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K43SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1881909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
MAAS 2.7 introduced network testing. As part of network testing we added the following features which require accurate interface and link speed information. 1. The interface and uplink speeds are now shown in the API and over the UI. 2. MAAS now warns when an interface is connected to an uplink which is slower than its maximum supported speed. 3. Users may now acquire machines based on its uplink speed. I could stop verifying that link speed >= max interface speed however that will mean 1 is incorrect and 2 is broken. I understand that some interfaces achieve higher speeds by using more physical ports but neither ethtool nor LXD give any information on this. Does anyone know the proper way to calculate the maximum supported interface speed on a device like this? ** Summary changed: - Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade + MAAS does not properly detect max interface speed for interfaces which use multiple phyiscal ports(Cisco UCS B200 M5 blade) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: MAAS does not properly detect max interface speed for interfaces which use multiple phyiscal ports(Cisco UCS B200 M5 blade) Status in MAAS: Triaged Status in MAAS 2.7 series: Triaged Status in MAAS 2.8 series: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Alright, that's a different amdgpu kernel issue in comment #8. So let's not confuse this bug by including Xorg. Just focus on the kernel issues... ** No longer affects: xorg-server (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/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 9YN58EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881494/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Tags added: oem-priority stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881675] Re: iwlwifi Microcode SW Error ubuntu 20.04
** Tags added: hwe-networking-wifi ** Summary changed: - iwlwifi Microcode SW Error ubuntu 20.04 + Intel Wireless 8260 [8086:24f3] Subsystem [8086:0010] iwlwifi Microcode SW Error ubuntu 20.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/1881675 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:0010] iwlwifi Microcode SW Error ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, this bug happens and keep logging as long as I do not not shut down the computer. Internet becomes irresponsive, and the whole computer is slowed. It will keep logging until saturating the hard drive. I had to format the hard drive and reinstall to be able to use the computer again once. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846676] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846823] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846829] iwlwifi :02:00.0: Status: 0x0040, count: 6 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846833] iwlwifi :02:00.0: Loaded firmware version: 36.77d01142.0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846838] iwlwifi :02:00.0: 0x0039 | BAD_COMMAND Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846842] iwlwifi :02:00.0: 0x0230 | trm_hw_status0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846845] iwlwifi :02:00.0: 0x | trm_hw_status1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846849] iwlwifi :02:00.0: 0x00024200 | branchlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846853] iwlwifi :02:00.0: 0x00039872 | interruptlink1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846856] iwlwifi :02:00.0: 0x | interruptlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846860] iwlwifi :02:00.0: 0x0002 | data1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846863] iwlwifi :02:00.0: 0xDEADBEEF | data2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846867] iwlwifi :02:00.0: 0xDEADBEEF | data3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846870] iwlwifi :02:00.0: 0x2D004C01 | beacon time Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846874] iwlwifi :02:00.0: 0x39E4BA08 | tsf low Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846877] iwlwifi :02:00.0: 0x0046 | tsf hi Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846880] iwlwifi :02:00.0: 0x | time gp1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846884] iwlwifi :02:00.0: 0xE24C9E94 | time gp2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846887] iwlwifi :02:00.0: 0x0001 | uCode revision type Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846891] iwlwifi :02:00.0: 0x0024 | uCode version major Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846894] iwlwifi :02:00.0: 0x77D01142 | uCode version minor Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846898] iwlwifi :02:00.0: 0x0201 | hw version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846901] iwlwifi :02:00.0: 0x00489008 | board version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846905] iwlwifi :02:00.0: 0x000D0304 | hcmd Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846908] iwlwifi :02:00.0: 0x24022080 | isr0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846912] iwlwifi :02:00.0: 0x | isr1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846915] iwlwifi :02:00.0: 0x0820180A | isr2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846919] iwlwifi :02:00.0: 0x004154C0 | isr3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846922] iwlwifi :02:00.0: 0x | isr4 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846926] iwlwifi :02:00.0: 0x9B5E009D | last cmd Id Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846929] iwlwifi :02:00.0: 0x | wait_event Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846933] iwlwifi :02:00.0: 0x0080 | l2p_control Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846936] iwlwifi :02:00.0: 0x00010030 | l2p_duration Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846940] iwlwifi :02:00.0: 0x003F | l2p_mhvalid Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846943] iwlwifi :02:00.0: 0x0080 | l2p_addr_match Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846946] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846950] iwlwifi :02:00.0: 0x08081421 | timestamp Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846953] iwlwifi :02:00.0: 0x3848 | flow_handler Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847013] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847016] iwlwifi :0
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Dan, Please try Kai-Heng's suggestion adding "pcie_aspm=off" to see if it helps If it does, please also attach the following logs 1. sudo lspci -xxxs 00:01.3 2. sudo lspci -xxxs 05:00.0 Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Incomplete Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018
[Kernel-packages] [Bug 1873384] Re: [Dell Inspiron 5577] Headphone has no sound out
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Just in case this can help anybody. On Ubuntu Studio 20.04 (Xfce), headphones audio started to work after I selected "Audio mixer..." -> "Input Devices" -> "Headset Microphone (plugged in)". It was "Microphone (plugged in) before I changed. No idea why I had to change something in "Input Devices" to make work something else in "Output Devices" ;-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873384 Title: [Dell Inspiron 5577] Headphone has no sound out Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Computer: Dell inspiron 15 5577 Gaming intel i5 7300HQ version System: Kubuntu 20.04 Bug: Plug-in headphone has no sound out, meanwhile computer's speaker is okay when unplugged the headphone. Additional information: Headphone is okay when kubuntu 18.04.3 is installed on the computer. Alsamixer is checked and headphone are not mute. Headphone plugin state can be correctly detected, and speaker can automatically mute until headphone unplugged. External usb soundcard is usable with headphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.12 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 11:14:43 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sherlockholmes 1242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) MachineType: Dell Inc. Inspiron 5577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 090HMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle
So, I've spent some time on this, and I'll be honest, I don't have a lot of answers. I know that -9 is awful. I've booted them all and ran powerstat on all of them logged into the desktop with nothing extra running. Attached is a tar file with the results of all of the kernels I have installed, which includes the four you uploaded and two more. I'm currently running -23 and so far it seems to be better than -33 but don't take that for sure yet. I'll run this for a while and then move over to -33 and see if there's a difference. I just wanted to update this to thank you for the kernels and let you know I'm investigating. ** Attachment added: "powerstat-5.4.x.tgz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+attachment/5380179/+files/powerstat-5.4.x.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881601 Title: Fan excessively runs, even when idle Status in linux package in Ubuntu: In Progress Bug description: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Hi, I'm just passing by. Regarding amdgpu issues related with Ryzen / Vega iGPU, there are a couple steps you can try: 1. Try a newer firmware blob. Download e.g. 1a. Download the latest firmware and unpack it https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20200519.tar.gz 1b. Backup your /lib/firmware folder 1c. sudo make install A newer firmware could fix the issue (it did for me on Ubuntu 18.04). If this fixes your problem, remember to freeze the linux-firmware package otherwise the next update will overwrite your changes and instability will come back. 2. Try a newer libdrm. Kernel updates for amdgpu go hand in hand with libdrm, but sometimes backports get these out of sync, or you try a mainline kernel but without a mainline libdrm. Download latest libdrm from https://gitlab.freedesktop.org/mesa/drm compile it and replace your Ubuntu's installation with your custom build one -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: gdm3 (Ubuntu) Milestone: None => ubuntu-20.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
I still find it weird that no issues occur in Windows. Will try to reproduce with kernel 5.7 and attach 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/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
Switching the ports so that the WD15 dock is connected to the USB-C port closer to the power socket and the display is connected to the other USB-C port fixed the issue. Apple USB-C to HDMI dongle exhibited the same issue when plugged into the same port. When the WD15 was connected to the port closer to the power socket with a display attached, USB devices intermittently disconnected and reconnected. Likely a hardware defect, but @mapengyu could you try to reproduce with the ports switched 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/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages
[Kernel-packages] [Bug 1877192] Re: RTL8723bs bluetooth not working on 20.04
I confirm that Bluetooth now works on the Intel Compute Stick STCK1A8LFC with the rtl8723bs hardware for the 5.7.0-050700 #202005312130 kernel from the above link. dmesg showed the expected Bluetooth firmware loading, and all necessary modules were automatically loaded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877192 Title: RTL8723bs bluetooth not working on 20.04 Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 20.04 installed on atom-based tablet ACER Aspire Switch 10. And bluetooth does not work. In fact it looks like ubuntu does not recognize bluetooth HW at all. But the system does have bluetooth module which under windows is recognized as RTK8723 (ACPI\RTK8723\some-id) At the same time WiFi works without issues (the same module, if I am not mistaken). $ lsb_release -d Description:Ubuntu 20.04 LTS $ uname -vr 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 $ dmesg | grep -i 8723 [8.087918] r8723bs: module is from the staging directory, the quality is unknown, you have been warned. [8.088914] r8723bs: module verification failed: signature and/or required key missing - tainting kernel [8.092667] RTL8723BS: module init start [8.092671] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40 [8.092673] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40 [8.303955] RTL8723BS: rtw_ndev_init(wlan0) [8.304653] RTL8723BS: module init ret =0 [ 13.200223] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin [ 17.832536] RTL8723BS: rtw_set_802_11_connect(wlan0) fw_state = 0x0008 [ 17.889893] RTL8723BS: start auth [ 17.892815] RTL8723BS: auth success, start assoc [ 17.901012] RTL8723BS: rtw_cfg80211_indicate_connect(wlan0) BSS not found !! [ 17.901053] RTL8723BS: assoc success [ 17.913846] RTL8723BS: send eapol packet [ 17.939873] RTL8723BS: send eapol packet [ 17.942652] RTL8723BS: set pairwise key camid:4, addr:50:c7:bf:31:a1:fa, kid:0, type:AES [ 17.944712] RTL8723BS: set group key camid:5, addr:50:c7:bf:31:a1:fa, kid:1, type:TKIP $ rfkill list all 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: acer-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1288 F pulseaudio /dev/snd/controlC0: user 1288 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lspci-vt: -[:00]-+-00.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register +-02.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display +-14.0 Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI +-1a.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine \-1f.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:2968 Synaptics, Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Acer Aspire SW5-012 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=140a1a3c-1a0a-4aab-b323-f621e6497a7e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 StagingDrivers: r8723bs Tags: focal staging Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Fendi2
[Kernel-packages] [Bug 1881950] 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/1881950 Title: Wireless mouse does not work Status in linux package in Ubuntu: Confirmed Bug description: Wireless mouse does not work, it is not detected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 20:38:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:236a] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:236a] InstallationDate: Installed on 2019-08-25 (282 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. X555LDB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=68cdded4-86f5-4f37-b6be-86a1a345547a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LDB.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LDB 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.:bvrX555LDB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LDB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881950] Re: Wireless mouse does not work
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881950 Title: Wireless mouse does not work Status in linux package in Ubuntu: Confirmed Bug description: Wireless mouse does not work, it is not detected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 20:38:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:236a] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:236a] InstallationDate: Installed on 2019-08-25 (282 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. X555LDB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=68cdded4-86f5-4f37-b6be-86a1a345547a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LDB.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LDB 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.:bvrX555LDB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LDB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881950] [NEW] Wireless mouse does not work
You have been subscribed to a public bug: Wireless mouse does not work, it is not detected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 20:38:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:236a] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:236a] InstallationDate: Installed on 2019-08-25 (282 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. X555LDB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=68cdded4-86f5-4f37-b6be-86a1a345547a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LDB.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LDB 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.:bvrX555LDB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LDB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- Wireless mouse does not work https://bugs.launchpad.net/bugs/1881950 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 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I believe https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/ is the cause. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Incomplete Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d4016fe38 EFLAGS: 0246 ORIG_RAX: ff13 Apr 23 10:07:43 surprise kernel: RAX: 8a758ee6a
[Kernel-packages] [Bug 1836030] Re: enable realtek ethernet device ASPM function
I believe this change has caused https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836030 Title: enable realtek ethernet device ASPM function Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: = SRU for 5.4 Focal kernel === [Impact] The PC state stays at PC3 if r8169 driver doesn't enable ASPM. [Fix] Applied same series of patches from v5.5-rc1 and disable ASPM L1.1 only, instead of disable ASPM completely. [Test] Verified on machines with realtek Ethernet device, the Ethernet works well after S3 test 30 times and the system can enter PC10. [Regression Potential] Low, from realtek engineer, r8169 driver supports ASPM L0s and L1, and we only disable ASPM L1.1 which is pretty safe and should be disabled by default. == SRU for 5.0 OEM OSP1 kernel = [Impact] The PC state stays at PC3 if realtek ethernet doesn't enable ASPM. [Fix] Discussed with upstream and they would like to use sysfs to toggle the ASPM link states, but the patches didn't get merged yet, so we merger them as SAUCE patches. [Test] Verified on machines with realtek ethernet device, the ethernet works well and the system can enter PC10. [Regression Potential] High. From upstream maintainer, enable realtek ethernet ASPM may lead to some serious issue, so regression is expected. Those regression should come from old realtek chips, we'll make sure all new platforms with realtek NIC have no any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881675] Re: iwlwifi Microcode SW Error ubuntu 20.04
Looks similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214 What do you think? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881675 Title: iwlwifi Microcode SW Error ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, this bug happens and keep logging as long as I do not not shut down the computer. Internet becomes irresponsive, and the whole computer is slowed. It will keep logging until saturating the hard drive. I had to format the hard drive and reinstall to be able to use the computer again once. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846676] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846823] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846829] iwlwifi :02:00.0: Status: 0x0040, count: 6 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846833] iwlwifi :02:00.0: Loaded firmware version: 36.77d01142.0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846838] iwlwifi :02:00.0: 0x0039 | BAD_COMMAND Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846842] iwlwifi :02:00.0: 0x0230 | trm_hw_status0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846845] iwlwifi :02:00.0: 0x | trm_hw_status1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846849] iwlwifi :02:00.0: 0x00024200 | branchlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846853] iwlwifi :02:00.0: 0x00039872 | interruptlink1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846856] iwlwifi :02:00.0: 0x | interruptlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846860] iwlwifi :02:00.0: 0x0002 | data1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846863] iwlwifi :02:00.0: 0xDEADBEEF | data2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846867] iwlwifi :02:00.0: 0xDEADBEEF | data3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846870] iwlwifi :02:00.0: 0x2D004C01 | beacon time Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846874] iwlwifi :02:00.0: 0x39E4BA08 | tsf low Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846877] iwlwifi :02:00.0: 0x0046 | tsf hi Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846880] iwlwifi :02:00.0: 0x | time gp1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846884] iwlwifi :02:00.0: 0xE24C9E94 | time gp2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846887] iwlwifi :02:00.0: 0x0001 | uCode revision type Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846891] iwlwifi :02:00.0: 0x0024 | uCode version major Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846894] iwlwifi :02:00.0: 0x77D01142 | uCode version minor Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846898] iwlwifi :02:00.0: 0x0201 | hw version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846901] iwlwifi :02:00.0: 0x00489008 | board version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846905] iwlwifi :02:00.0: 0x000D0304 | hcmd Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846908] iwlwifi :02:00.0: 0x24022080 | isr0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846912] iwlwifi :02:00.0: 0x | isr1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846915] iwlwifi :02:00.0: 0x0820180A | isr2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846919] iwlwifi :02:00.0: 0x004154C0 | isr3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846922] iwlwifi :02:00.0: 0x | isr4 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846926] iwlwifi :02:00.0: 0x9B5E009D | last cmd Id Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846929] iwlwifi :02:00.0: 0x | wait_event Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846933] iwlwifi :02:00.0: 0x0080 | l2p_control Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846936] iwlwifi :02:00.0: 0x00010030 | l2p_duration Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846940] iwlwifi :02:00.0: 0x003F | l2p_mhvalid Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846943] iwlwifi :02:00.0: 0x0080 | l2p_addr_match Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846946] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846950] iwlwifi :02:00.0: 0x08081421 | timestamp Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846953] iwlwifi :02:00.0: 0x3848 | flow_handler Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847013] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847016] iwlwifi :02:00.0: Status: 0x0040, count: 7 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847020] iwlwifi :02:00.0: 0x0070 | NMI_INTERRUPT_LMAC_FATAL
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
I could only attached one file. Here is udevadm.log ** Attachment added: "udevadm.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5380156/+files/udevadm.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hi Kai, Thanks again for trying to fix this bug. I attached two files called dmesg.log and udevadm.log. I really appreciate your help Cristian ** Attachment added: "dmseg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+attachment/5380155/+files/dmseg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707341] Re: nm-dispatcher caused kernel crash.
thank you for your bug report, if the kernel crash it's a bug there, it should be robust to anything userpace is doing, reassigning ** Package changed: network-manager (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/1707341 Title: nm-dispatcher caused kernel crash. Status in linux package in Ubuntu: Confirmed Bug description: After "waking" (shaking my mouse) to revive the display server my machine was usable for about 1 minute after the wake. Then all of the sudden all of my USB devices lost power completely, my hard drives stopped spinning and the system was at a stand still. Reading into the log files I find that the last thing the system did before it died. It was in the process of a "dhcp4 change". I would also like to mention I was running 3 VNC server sessions at the same time, but none of the viewers were active. I also confirmed that the power supply is defiantly not the reason its a 1000 watt platinum PSU that is under a year old and the system was usable again after a reboot. I am using Kernel version 4.11.7 built from the mainline with the Ubuntu configuration. There were no custom modules loaded (nothing outside of the 16.04.2 repo) here is the log /var/log/syslog Jul 28 22:27:43 Nova-Omega dhclient[3065]: DHCPACK of 10.10.20.115 from 10.10.20.1 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] address 10.10.20.115 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] plen 24 (255.255.255.0) Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] gateway 10.10.20.1 Jul 28 22:27:43 Nova-Omega dhclient[3065]: bound to 10.10.20.115 -- renewal in 243 seconds. Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] server identifier 10.10.20.1 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] lease time 600 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] nameserver '8.8.8.8' Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] nameserver '8.8.4.4' Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] dhcp4 (enp35s0): state changed bound -> bound Jul 28 22:27:43 Nova-Omega dbus[1039]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jul 28 22:27:43 Nova-Omega systemd[1]: Starting Network Manager Script Dispatcher Service... Jul 28 22:27:43 Nova-Omega dbus[1039]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jul 28 22:27:43 Nova-Omega systemd[1]: Started Network Manager Script Dispatcher Service. Jul 28 22:27:43 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: new request (2 scripts) Jul 28 22:27:43 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: start running ordered scripts... Jul 28 22:31:46 Nova-Omega dhclient[3065]: DHCPREQUEST of 10.10.20.115 on enp35s0 to 10.10.20.1 port 67 (xid=0x2d7aba42) Jul 28 22:31:46 Nova-Omega dhclient[3065]: DHCPACK of 10.10.20.115 from 10.10.20.1 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1854] address 10.10.20.115 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1854] plen 24 (255.255.255.0) Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] gateway 10.10.20.1 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] server identifier 10.10.20.1 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] lease time 600 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] nameserver '8.8.8.8' Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] nameserver '8.8.4.4' Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1856] dhcp4 (enp35s0): state changed bound -> bound Jul 28 22:31:46 Nova-Omega dbus[1039]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jul 28 22:31:46 Nova-Omega systemd[1]: Starting Network Manager Script Dispatcher Service... Jul 28 22:31:46 Nova-Omega dhclient[3065]: bound to 10.10.20.115 -- renewal in 298 seconds. Jul 28 22:31:46 Nova-Omega dbus[1039]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jul 28 22:31:46 Nova-Omega systemd[1]: Started Network Manager Script Dispatcher Service. Jul 28 22:31:46 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: new request (2 scripts) Jul 28 22:31:46 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: start running ordered scripts... Jul 28 22:33:16 Nova-Omega smartd[1021]: Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 27 to 26 Jul 28 22:33:16 Nova-Omega smartd[1021]: Device: /dev/sda
[Kernel-packages] [Bug 1707341] [NEW] nm-dispatcher caused kernel crash.
You have been subscribed to a public bug: After "waking" (shaking my mouse) to revive the display server my machine was usable for about 1 minute after the wake. Then all of the sudden all of my USB devices lost power completely, my hard drives stopped spinning and the system was at a stand still. Reading into the log files I find that the last thing the system did before it died. It was in the process of a "dhcp4 change". I would also like to mention I was running 3 VNC server sessions at the same time, but none of the viewers were active. I also confirmed that the power supply is defiantly not the reason its a 1000 watt platinum PSU that is under a year old and the system was usable again after a reboot. I am using Kernel version 4.11.7 built from the mainline with the Ubuntu configuration. There were no custom modules loaded (nothing outside of the 16.04.2 repo) here is the log /var/log/syslog Jul 28 22:27:43 Nova-Omega dhclient[3065]: DHCPACK of 10.10.20.115 from 10.10.20.1 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] address 10.10.20.115 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] plen 24 (255.255.255.0) Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] gateway 10.10.20.1 Jul 28 22:27:43 Nova-Omega dhclient[3065]: bound to 10.10.20.115 -- renewal in 243 seconds. Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5871] server identifier 10.10.20.1 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] lease time 600 Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] nameserver '8.8.8.8' Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] nameserver '8.8.4.4' Jul 28 22:27:43 Nova-Omega NetworkManager[1181]: [1501295263.5872] dhcp4 (enp35s0): state changed bound -> bound Jul 28 22:27:43 Nova-Omega dbus[1039]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jul 28 22:27:43 Nova-Omega systemd[1]: Starting Network Manager Script Dispatcher Service... Jul 28 22:27:43 Nova-Omega dbus[1039]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jul 28 22:27:43 Nova-Omega systemd[1]: Started Network Manager Script Dispatcher Service. Jul 28 22:27:43 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: new request (2 scripts) Jul 28 22:27:43 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: start running ordered scripts... Jul 28 22:31:46 Nova-Omega dhclient[3065]: DHCPREQUEST of 10.10.20.115 on enp35s0 to 10.10.20.1 port 67 (xid=0x2d7aba42) Jul 28 22:31:46 Nova-Omega dhclient[3065]: DHCPACK of 10.10.20.115 from 10.10.20.1 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1854] address 10.10.20.115 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1854] plen 24 (255.255.255.0) Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] gateway 10.10.20.1 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] server identifier 10.10.20.1 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] lease time 600 Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] nameserver '8.8.8.8' Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1855] nameserver '8.8.4.4' Jul 28 22:31:46 Nova-Omega NetworkManager[1181]: [1501295506.1856] dhcp4 (enp35s0): state changed bound -> bound Jul 28 22:31:46 Nova-Omega dbus[1039]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jul 28 22:31:46 Nova-Omega systemd[1]: Starting Network Manager Script Dispatcher Service... Jul 28 22:31:46 Nova-Omega dhclient[3065]: bound to 10.10.20.115 -- renewal in 298 seconds. Jul 28 22:31:46 Nova-Omega dbus[1039]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jul 28 22:31:46 Nova-Omega systemd[1]: Started Network Manager Script Dispatcher Service. Jul 28 22:31:46 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: new request (2 scripts) Jul 28 22:31:46 Nova-Omega nm-dispatcher: req:1 'dhcp4-change' [enp35s0]: start running ordered scripts... Jul 28 22:33:16 Nova-Omega smartd[1021]: Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 27 to 26 Jul 28 22:33:16 Nova-Omega smartd[1021]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 27 to 26 Jul 28 22:33:17 Nova-Omega smartd[1021]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 214 to 222 Jul 28 22:37:27 Nova-Omega rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1043" x-info="http://www.rsyslog.com";] start Jul 28 22:37:27 Nova-Omega rsyslogd-: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)?
[Kernel-packages] [Bug 1881427] Re: zfs-linux 0.8.3-1ubuntu14 has a broken backport of Linux 5.7 compat
Fix released in zfs-linux 0.8.4-1ubuntu3 ** Changed in: zfs-linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1881427 Title: zfs-linux 0.8.3-1ubuntu14 has a broken backport of Linux 5.7 compat Status in zfs-linux package in Ubuntu: Fix Released Bug description: The backport of upstream commit 68dde63d138882860109178f4ab0b7b1b1bb3cfd in 0.8.3-1ubuntu14 is not correct for the 0.8.3 stable series and causes an oops on boot with a 5.7 kernel. The patch that shipped in 0.8.4 is slightly different, and works correctly: https://github.com/openzfs/zfs/commit/e6142ac0f28891a0ef3de366a45bb857a17ee25a [ 13.848194] BUG: kernel NULL pointer dereference, address: 0040 [ 13.848415] #PF: supervisor write access in kernel mode [ 13.848572] #PF: error_code(0x0002) - not-present page [ 13.848813] PGD 0 P4D 0 [ 13.848896] Oops: 0002 [#1] SMP PTI [ 13.849006] CPU: 3 PID: 1501 Comm: z_zvol Tainted: P OE 5.7.0-rc7-customskl #1 [ 13.849254] Hardware name: System manufacturer System Product Name/ROG MAXIMUS X HERO (WI-FI AC), BIOS 2301 02/25/2020 [ 13.849623] RIP: 0010:zvol_create_minor_impl+0x52a/0x810 [zfs] [ 13.849800] Code: 48 8b 54 24 18 49 89 87 08 01 00 00 48 8b 44 24 20 49 89 97 10 01 00 00 49 8b 97 a8 01 00 00 49 89 87 00 01 00 00 48 c1 e8 09 <48> 89 42 40 49 8b bf b0 01 00 00 e8 f6 3e f2 cf 49 8b bf b0 01 00 [ 13.850346] RSP: 0018:b75ac1df7cf8 EFLAGS: 00010206 [ 13.850504] RAX: 0200 RBX: 3471fa85c299b9ef RCX: [ 13.850715] RDX: RSI: 8000 RDI: a286a5775000 [ 13.850926] RBP: a286a0c60fb0 R08: a286ae55580f R09: [ 13.851137] R10: a286ae55582c R11: a286ae55580f R12: [ 13.851347] R13: R14: a286962ff380 R15: a286ac071800 [ 13.851560] FS: () GS:a286beac() knlGS: [ 13.851799] CS: 0010 DS: ES: CR0: 80050033 [ 13.851970] CR2: 0040 CR3: 00051f20a001 CR4: 003606e0 [ 13.852181] DR0: DR1: DR2: [ 13.852392] DR3: DR6: fffe0ff0 DR7: 0400 [ 13.852602] Call Trace: [ 13.852733] zvol_task_cb+0x258/0x570 [zfs] [ 13.852867] ? __schedule+0x1d8/0x560 [ 13.852988] taskq_thread+0x2c3/0x490 [spl] [ 13.853119] ? __switch_to_asm+0x34/0x70 [ 13.853241] ? wake_up_q+0xa0/0xa0 [ 13.853350] kthread+0xfb/0x130 [ 13.853453] ? task_done+0x90/0x90 [spl] [ 13.853573] ? kthread_park+0x90/0x90 [ 13.853686] ret_from_fork+0x35/0x40 [ 13.853797] Modules linked in: input_leds btusb uvcvideo btbcm btrtl videobuf2_vmalloc btintel videobuf2_memops snd_usb_audio videobuf2_v4l2 bluetooth videobuf2_common hid_generic videodev snd_usbmidi_lib ecdh_generic mc usbhid ecc intel_rapl_msr intel_rapl_common uas usb_storage zfs(POE) x86_pkg_temp_thermal zunicode(POE) intel_powerclamp zlua(POE) mxm_wmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel amdgpu snd_intel_dspcfg crct10dif_pclmul snd_hda_codec crc32_pclmul crc32c_intel snd_hwdep snd_hda_core rtwpci snd_pcm_oss rtw88 snd_mixer_oss zcommon(POE) ghash_clmulni_intel snd_pcm znvpair(POE) vfat zavl(POE) icp(POE) fat snd_seq_oss spl(OE) mac80211 snd_seq_midi mfd_core gpu_sched i2c_algo_bit aesni_intel snd_rawmidi ttm snd_seq_midi_event crypto_simd xhci_pci snd_seq xhci_hcd cryptd deflate snd_seq_device drm_kms_helper glue_helper efi_pstore cfg80211 e1000e snd_timer syscopyarea intel_cstate sysfillrect rfkill ptp sysimgblt efivars pps_core [ 13.853860] i2c_i801 usbcore snd libarc4 sr_mod intel_rapl_perf fb_sys_fops cec cdrom mei_hdcp usb_common sg rc_core soundcore video wmi acpi_pad button squashfs sch_fq_codel coretemp hwmon loop drm i2c_core nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables [ 13.857103] CR2: 0040 [ 13.857207] ---[ end trace a20c8291d85b28f4 ]--- [ 13.994917] RIP: 0010:zvol_create_minor_impl+0x52a/0x810 [zfs] [ 13.994993] Code: 48 8b 54 24 18 49 89 87 08 01 00 00 48 8b 44 24 20 49 89 97 10 01 00 00 49 8b 97 a8 01 00 00 49 89 87 00 01 00 00 48 c1 e8 09 <48> 89 42 40 49 8b bf b0 01 00 00 e8 f6 3e f2 cf 49 8b bf b0 01 00 [ 13.997900] RSP: 0018:b75ac1df7cf8 EFLAGS: 00010206 [ 14.000564] RAX: 0200 RBX: 3471fa85c299b9ef RCX: [ 14.003239] RDX: RSI: 8000 RDI: a286a5775000 [ 14.005901] RBP: a286a0c60fb0 R08: a286ae55580f R09: [ 14.008580] R10: a286ae55582c R11: a286ae55580f R12: [ 14.011210] R13:
[Kernel-packages] [Bug 1881951] 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/1881951 Title: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: occured when installing packages with synaptic ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm bnep intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi coretemp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core iwlmvm mac80211 btusb btrtl dell_laptop uvcvideo mei_hdcp btbcm btintel rtsx_usb_ms bluetooth intel_cstate intel_rapl_perf memstick ledtrig_audio dell_smm_hwmon i915 iwlwifi cfg80211 dell_wmi dell_smbios dcdbas wmi_bmof mei_me mei mac_hid sparse_keymap dell_wmi_descriptor dell_rbtn rtsx_usb_sdmmc rtsx_usb hid_rmi rmi_core videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc i2c_i801 r8169 lpc_ich realtek wmi i2c_hid ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eon1423 F pulseaudio /dev/snd/controlC0: eon1423 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 4 00:53:57 2020 DuplicateSignature: package:linux-image-5.4.0-33-generic:5.4.0-33.37 Removing linux-image-5.4.0-33-generic (5.4.0-33.37) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-5.4.0-33-generic (--remove): installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned error exit status 1 ErrorMessage: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=d6bf3c25-8add-4957-af64-c7d5ac93a7f4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/25/2018:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.sku: 06B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881951] Re: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned er
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881951 Title: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: occured when installing packages with synaptic ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm bnep intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi coretemp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core iwlmvm mac80211 btusb btrtl dell_laptop uvcvideo mei_hdcp btbcm btintel rtsx_usb_ms bluetooth intel_cstate intel_rapl_perf memstick ledtrig_audio dell_smm_hwmon i915 iwlwifi cfg80211 dell_wmi dell_smbios dcdbas wmi_bmof mei_me mei mac_hid sparse_keymap dell_wmi_descriptor dell_rbtn rtsx_usb_sdmmc rtsx_usb hid_rmi rmi_core videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc i2c_i801 r8169 lpc_ich realtek wmi i2c_hid ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eon1423 F pulseaudio /dev/snd/controlC0: eon1423 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 4 00:53:57 2020 DuplicateSignature: package:linux-image-5.4.0-33-generic:5.4.0-33.37 Removing linux-image-5.4.0-33-generic (5.4.0-33.37) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-5.4.0-33-generic (--remove): installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned error exit status 1 ErrorMessage: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=d6bf3c25-8add-4957-af64-c7d5ac93a7f4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/25/2018:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.sku: 06B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881951] [NEW] package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned
Public bug reported: occured when installing packages with synaptic ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm bnep intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi coretemp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core iwlmvm mac80211 btusb btrtl dell_laptop uvcvideo mei_hdcp btbcm btintel rtsx_usb_ms bluetooth intel_cstate intel_rapl_perf memstick ledtrig_audio dell_smm_hwmon i915 iwlwifi cfg80211 dell_wmi dell_smbios dcdbas wmi_bmof mei_me mei mac_hid sparse_keymap dell_wmi_descriptor dell_rbtn rtsx_usb_sdmmc rtsx_usb hid_rmi rmi_core videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc i2c_i801 r8169 lpc_ich realtek wmi i2c_hid ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eon1423 F pulseaudio /dev/snd/controlC0: eon1423 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 4 00:53:57 2020 DuplicateSignature: package:linux-image-5.4.0-33-generic:5.4.0-33.37 Removing linux-image-5.4.0-33-generic (5.4.0-33.37) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-5.4.0-33-generic (--remove): installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned error exit status 1 ErrorMessage: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=d6bf3c25-8add-4957-af64-c7d5ac93a7f4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/25/2018:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.sku: 06B0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881951 Title: package linux-image-5.4.0-33-generic 5.4.0-33.37 failed to install/upgrade: installed linux-image-5.4.0-33-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: occured when installing packages with synaptic ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm bnep intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi coretemp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core iwlmvm mac80211 btusb btrtl dell_laptop uvcvideo mei_hdcp btbcm btintel rtsx_usb_ms bluetooth intel_cstate intel_rapl_perf memstick ledtrig_audio dell_smm_hwmon i915 iwlwifi cfg80211 dell_wmi dell_smbios dcdbas wmi_bmof mei_me mei mac_hid sparse_keymap dell_wmi_descriptor dell_rbtn rtsx_usb_sdmmc rtsx_usb hid_rmi rmi_core videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc i2c_i801 r8169 lpc_ich realtek wmi i2c_hid ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eon1423 F pulseaudio /dev/snd/controlC0: eon1423 F pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 4 00:53:57 2020 DuplicateSignature: package:linux-image-5.4.0-33-generic:5.4.0-33.37 Removing linux-image-5.4.0-33-generic (5.4.0-33.37) ... E: Aborting removal of
[Kernel-packages] [Bug 1878480] Re: Centrino Wireless-N 1000 [Condor Peak]
No its the same. Have some moments it works ok then it starts behave like the other kernels. A lot of pp are complaining in the forums about bad networks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878480 Title: Centrino Wireless-N 1000 [Condor Peak] Status in linux package in Ubuntu: Incomplete Bug description: After upgrade to 20.04 my wireless starts to be very unstable, it goes from 65mbs to 1mbs. I need to reenable wirless ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 2846 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 20:57:07 2020 HibernationDevice: RESUME=UUID=0f71c458-758c-439d-9dd0-b7ddcd620218 MachineType: Alienware M14xR1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=fcba8370-4563-4d59-8a53-f1a70ebb8e1d ro quiet splash nouveau.blacklist=1 nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2011 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: M14xR1 dmi.board.vendor: Alienware dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd12/24/2011:svnAlienware:pnM14xR1:pvrA08:rvnAlienware:rnM14xR1:rvrA08:cvnAlienware:ct8:cvrA08: dmi.product.family: 103C_5335KV dmi.product.name: M14xR1 dmi.product.sku: xxx123x#ABA dmi.product.version: A08 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
Could we change the name of the bug? It is not a kernel 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/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in MAAS 2.7 series: Triaged Status in MAAS 2.8 series: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
For documentation purposes, The bcache-specific patch has been sent today. Waiting on review before providing test kernels. [PATCH] bcache: check and adjust logical block size for backing devices https://www.spinics.net/lists/linux-bcache/msg08411.html cheers, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Confirmed Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 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: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
Maybe push it to PPA? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876022] Re: Wireless adapter not detected (WiFi) Acer One S1003
Hello. Any news about this ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876022 Title: Wireless adapter not detected (WiFi) Acer One S1003 Status in linux package in Ubuntu: Confirmed Bug description: This tablet was running Windows when I first bought it. Known problem under windows : the wireless connection would fail after device wake up from suspend. It could still see and detect networks tho I was interested into having a Linux tablet so I installed Ubuntu 2020.04 on it. Since my bios wouldn't accept 64 efi boot files, I had to use bootia32.efi. It failed many times on creating a boot partition until I connected it to the internet using a wired connection. Please note that while windows was still present on the disk, I could still use the WLAN under live linux. It's only when I had it completely erased Windows 10 that it stopped being detected by Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 05:27:54 2020 InstallationDate: Installed on 2020-04-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: phil942 F pulseaudio /dev/snd/controlC0: phil942 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-29 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. usb0 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 2717:ff88 Xiaomi Inc. Mi/Redmi series (RNDIS + ADB) Bus 001 Device 002: ID 06cb:73f5 Synaptics, Inc. ITE Device(8910) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer One S1003 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=1175955f-9b01-4159-b54d-4fd481a9755c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/20/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.19 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: One S1003 dmi.board.vendor: Acer dmi.board.version: V1.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.19:bd03/20/2018:svnAcer:pnOneS1003:pvrV1.19:rvnAcer:rnOneS1003:rvrV1.19:cvnAcer:ct32:cvrChassisVersion: dmi.product.family: CHT-CR dmi.product.name: One S1003 dmi.product.sku: S1003_1025112B_1.19 dmi.product.version: V1.19 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
I built a fixed version here if you're willing to trust a stranger on the internet: https://drive.google.com/file/d/1BrXOZH-E_cw93HBmk7id1LzUJtnYVsQn/view?usp=sharing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856434] Re: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Had the exact same problem on Dell hardware with HBA330. Possible to solve with a "sg_format --format" on every single drive or by upgrading fw on the HBA controller. https://www.dell.com/support/home/en- us/drivers/driversdetails?driverid=nknvc&oscode=wst14&productcode =poweredge-r740xd -Fixes a firmware initialization problem that causes T10 Protection Information (PI) Logical Block and Guard Tag errors under Linux operating systems. This can result in an inability to read from T10 PI capable drives. More info about T10 Protection Information (T10-PI) https://www.seagate.com/files/staticfiles/docs/pdf/whitepaper/safeguarding-data-from-corruption-technology-paper-tp621us.pdf Check status with sg_readcap -l /dev/sda "Protection: prot_en=1, p_type=1, p_i_exponent=0 [type 2 protection]" or smartctl --all /dev/sda "Formatted with type 2 protection" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856434 Title: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Status in linux package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) unknown 3) no error 4) error in log app. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: htpc 9157 F pulseaudio /dev/snd/controlC1: htpc 9157 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (48 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lxcbr0no wireless extensions. lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: wayland-session eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6b dmi.board.name: GA-MA780G-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA780G-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu1 --- alsa-ucm-conf (1.2.2-1ubuntu1) groovy; urgency=medium * Fix the audio crash on the machine without Intel HDMI audio (lp: #1874698) -- Hui Wang Mon, 25 May 2020 14:36:48 +0800 ** Changed in: alsa-ucm-conf (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
Prior to this commit https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490 hostapd doesn't check if the driver supports 802.11R aka. FT. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881927] [NEW] Focal update: v5.4.44 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.44 upstream stable release from git://git.kernel.org/ ax25: fix setsockopt(SO_BINDTODEVICE) dpaa_eth: fix usage as DSA master, try 3 net: don't return invalid table id error when we fall back to PF_UNSPEC net: dsa: mt7530: fix roaming from DSA user ports net: ethernet: ti: cpsw: fix ASSERT_RTNL() warning during suspend __netif_receive_skb_core: pass skb by reference net: inet_csk: Fix so_reuseport bind-address cache in tb->fast* net: ipip: fix wrong address family in init error path net/mlx5: Add command entry handling completion net: mvpp2: fix RX hashing for non-10G ports net: nlmsg_cancel() if put fails for nhmsg net: qrtr: Fix passing invalid reference to qrtr_local_enqueue() net: revert "net: get rid of an signed integer overflow in ip_idents_reserve()" net sched: fix reporting the first-time use timestamp net/tls: fix race condition causing kernel panic nexthop: Fix attribute checking for groups r8152: support additional Microsoft Surface Ethernet Adapter variant sctp: Don't add the shutdown timer if its already been added sctp: Start shutdown on association restart if in SHUTDOWN-SENT state and socket is closed tipc: block BH before using dst_cache net/mlx5e: kTLS, Destroy key object after destroying the TIS net/mlx5e: Fix inner tirs handling net/mlx5: Fix memory leak in mlx5_events_init net/mlx5e: Update netdev txq on completions during closure net/mlx5: Fix error flow in case of function_setup failure net/mlx5: Annotate mutex destroy for root ns net/tls: fix encryption error checking net/tls: free record only on encryption error net: sun: fix missing release regions in cas_init_one(). net/mlx4_core: fix a memory leak bug. mlxsw: spectrum: Fix use-after-free of split/unsplit/type_set in case reload fails ARM: dts: rockchip: fix phy nodename for rk3228-evb ARM: dts: rockchip: fix phy nodename for rk3229-xms6 arm64: dts: rockchip: fix status for &gmac2phy in rk3328-evb.dts arm64: dts: rockchip: swap interrupts interrupt-names rk3399 gpu node ARM: dts: rockchip: swap clock-names of gpu nodes ARM: dts: rockchip: fix pinctrl sub nodename for spi in rk322x.dtsi gpio: tegra: mask GPIO IRQs during IRQ shutdown ALSA: usb-audio: add mapping for ASRock TRX40 Creator net: microchip: encx24j600: add missed kthread_stop gfs2: move privileged user check to gfs2_quota_lock_check gfs2: Grab glock reference sooner in gfs2_add_revoke drm/amdgpu: drop unnecessary cancel_delayed_work_sync on PG ungate drm/amd/powerplay: perform PG ungate prior to CG ungate drm/amdgpu: Use GEM obj reference for KFD BOs cachefiles: Fix race between read_waiter and read_copier involving op->to_do usb: dwc3: pci: Enable extcon driver for Intel Merrifield usb: phy: twl6030-usb: Fix a resource leak in an error handling path in 'twl6030_usb_probe()' usb: gadget: legacy: fix redundant initialization warnings net: freescale: select CONFIG_FIXED_PHY where needed IB/i40iw: Remove bogus call to netdev_master_upper_dev_get() riscv: stacktrace: Fix undefined reference to `walk_stackframe' clk: ti: am33xx: fix RTC clock parent csky: Fixup msa highest 3 bits mask csky: Fixup perf callchain unwind csky: Fixup remove duplicate irq_disable hwmon: (nct7904) Fix incorrect range of temperature limit registers cifs: Fix null pointer check in cifs_read csky: Fixup raw_copy_from_user() samples: bpf: Fix build error drivers: net: hamradio: Fix suspicious RCU usage warning in bpqether.c Input: usbtouchscreen - add support for BonXeon TP Input: evdev - call input_flush_device() on release(), not flush() Input: xpad - add custom init packet for Xbox One S controllers Input: dlink-dir685-touchkeys - fix a typo in driver name Input: i8042 - add ThinkPad S230u to i8042 reset list Input: synaptics-rmi4 - really fix attn_data use-after-free Input: synaptics-rmi4 - fix error return code in rmi_driver_probe() ARM: 8970/1: decompressor: increase tag size ARM: uaccess: consolidate uaccess asm to asm/uaccess-asm.h ARM: uaccess: integrate uaccess_save and uaccess_restore ARM: uaccess: fix DACR mismatch with nested exceptions gpio: exar: Fix bad handling for ida_simple_get error path arm64: dts: mt8173: fix vcodec-enc clock soc: mediatek: cmdq: return send msg error code gpu/drm: Ingenic: Fix opaque pointer casted to wrong type IB/qib: Call kobject_put() when kobject_init_and_add() fails ARM: dts/imx6q-bx50v3: Set display interface clock parents ARM: dts: bcm2835-rpi-zero-w: Fix led polarity ARM: dts: bcm: HR2: Fix PPI interrupt types mmc: block: Fix use-after-free issue for rpmb gpio: pxa: Fi
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
Thanks for the background info, in 2.7 MAAS started modelling the speeds of interfaces and links, so I expect that 2.6 will not have the same problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in MAAS 2.7 series: Triaged Status in MAAS 2.8 series: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
Testing with MAAS 2.6 and the network interfaces were detected correctly. This points to MAAS 2.7 having a bug in the way it tests the link speeds. Also, the smartctl-validate tests were successful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in MAAS 2.7 series: Triaged Status in MAAS 2.8 series: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up
** Changed in: grub2 (Ubuntu) Status: New => Incomplete ** Changed in: grub2 (Ubuntu Bionic) Status: New => Incomplete -- 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/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in grub2 source package in Bionic: Incomplete Bug description: With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub. There is no any log in journal when it fails to boot up, and earlyprintk shows nothing on the screen, either. System Information Manufacturer: Dell Inc. Product Name: Latitude 7300 Version: Not Specified Serial Number: J83ZST2 UUID: 4C4C4544-0038-3310-805A-CAC04F535432 Wake-up Type: Power Switch SKU Number: 08E0 Family: Latitude BIOS Information Vendor: Dell Inc. Version: 1.6.1 Release Date: 11/14/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 24 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831543] Re: Standard_A2_v2 Azure instance will have CPU in offline state
** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux-azure (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1831543 Title: Standard_A2_v2 Azure instance will have CPU in offline state Status in ubuntu-kernel-tests: Won't Fix Status in linux-azure package in Ubuntu: Won't Fix Bug description: This needs to be investigated to see if it's been disabled intentionally. The cpu-hot-plug test shows there are 126 offlined CPUs. selftests: cpu-on-off-test.sh pid 9824's current affinity mask: 3 pid 9824's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 2-127 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up
Readding linux-oem ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New -- 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/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in grub2 source package in Bionic: Incomplete Bug description: With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub. There is no any log in journal when it fails to boot up, and earlyprintk shows nothing on the screen, either. System Information Manufacturer: Dell Inc. Product Name: Latitude 7300 Version: Not Specified Serial Number: J83ZST2 UUID: 4C4C4544-0038-3310-805A-CAC04F535432 Wake-up Type: Power Switch SKU Number: 08E0 Family: Latitude BIOS Information Vendor: Dell Inc. Version: 1.6.1 Release Date: 11/14/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 24 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
** Also affects: maas/2.7 Importance: Undecided Status: New ** Also affects: maas/2.8 Importance: Critical Assignee: Lee Trager (ltrager) Status: Triaged ** Changed in: maas/2.8 Milestone: None => 2.8.0rc1 ** Changed in: maas/2.7 Milestone: None => 2.7.2 ** Changed in: maas/2.7 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/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in MAAS 2.7 series: Triaged Status in MAAS 2.8 series: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881828] Re: Lenovo X1 Extreme screen never wakes up
Signed and installed 5.7.0-050700-generic from mainline. I will test it out and see what I get, thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881828 Title: Lenovo X1 Extreme screen never wakes up Status in linux package in Ubuntu: Confirmed Bug description: Unreliably, but 9 times out of 10, if my screen goes to sleep on my laptop it will never wake back up. Looking in kern.log I see this output, scrolling on repeat, until I long-press the power button to shut off the laptop. Happened occasionally in Ubuntu 19.10, now regularly on 20.04. Persisted with the nvidia proprietary driver as well as the open source one. It has persisted across several official ubuntu packaged kernel revisions. I got kernel taint down to "0" and it kept happening. (Previously virtualbox and nvidia driver were in there.) May 26 20:02:30 hawk-x1 kernel: [28401.972981] No Local Variables are initialized for Method [NVPO] May 26 20:02:30 hawk-x1 kernel: [28401.972986] No Arguments are initialized for method [NVPO] May 26 20:02:30 hawk-x1 kernel: [28401.972991] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.NVPO due to previous error (AE_AML_LOOP_TIMEOUT) (20190816/psparse-529) May 26 20:02:30 hawk-x1 kernel: [28401.973016] ACPI Error: Aborting method \_SB.PCI0.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20190816/psparse-529) May 26 20:02:30 hawk-x1 kernel: [28401.973033] ACPI Error: Aborting method \_SB.PCI0.PEG0.PG00._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20190816/psparse-529) May 26 20:02:30 hawk-x1 kernel: [28401.973058] acpi device:00: Failed to change power state to D0 May 26 20:02:31 hawk-x1 kernel: [28403.217052] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) May 26 20:02:31 hawk-x1 kernel: [28403.217064] nouveau :01:00.0: Refused to change power state, currently in D3 May 26 20:02:31 hawk-x1 kernel: [28403.277092] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) May 26 20:02:31 hawk-x1 kernel: [28403.296906] nouveau :01:00.0: Refused to change power state, currently in D3 May 26 20:02:31 hawk-x1 kernel: [28403.296915] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) May 26 20:02:31 hawk-x1 kernel: [28403.316894] nouveau :01:00.0: Refused to change power state, currently in D3 May 26 20:02:31 hawk-x1 kernel: [28403.319495] nouveau :01:00.0: tmr: stalled at May 26 20:02:31 hawk-x1 kernel: [28403.319497] [ cut here ] May 26 20:02:31 hawk-x1 kernel: [28403.319498] nouveau :01:00.0: timeout May 26 20:02:31 hawk-x1 kernel: [28403.319551] WARNING: CPU: 2 PID: 2697 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0xd6/0xe0 [nouveau] May 26 20:02:31 hawk-x1 kernel: [28403.319552] Modules linked in: xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype bpfilter ccm overlay aufs bnep binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt iwlmvm snd_sof_intel_ipc snd_sof mac80211 uvcvideo snd_sof_xtensa_dsp snd_hda_ext_core videobuf2_vmalloc snd_soc_acpi_intel_match videobuf2_memops snd_soc_acpi btusb libarc4 videobuf2_v4l2 btrtl videobuf2_common btbcm wmi_bmof thinkpad_acpi input_leds joydev snd_hda_codec_realtek btintel snd_soc_core snd_seq_midi videodev bluetooth snd_hda_codec_generic serio_raw snd_seq_midi_event nvram snd_compress ac97_bus intel_wmi_thunderbolt snd_pcm_dmaengine ledtrig_audio mc iwlwifi snd_rawmidi ecdh_generic 8250_dw ecc snd_hda_intel mei_me cfg80211 May 26 20:02:31 hawk-x1 kernel: [28403.319567] snd_intel_dspcfg mei snd_hda_codec snd_seq snd_hda_core ucsi_acpi snd_hwdep processor_thermal_device typec_ucsi intel_rapl_common snd_pcm intel_pch_thermal intel_soc_dts_iosf typec snd_seq_device snd_timer snd soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper aesni_intel syscopyarea sysfillrect crypto_simd sysimgblt cryptd fb_sys_fops glue_helper nvme psmouse e1000e drm intel_lpss_pci i2c_i801 nvme_core thunderbolt intel_lpss idma64 virt_dma wmi video May 26 20:02:31 hawk-x1 kernel: [28403.319582] CPU: 2 PID: 2697 Comm: gnome-shell Kdump: loaded Not tainted 5.4.0-31-generic #35-Ubuntu May 26 20:02:31 hawk-x1 kernel: [28403.
[Kernel-packages] [Bug 1881107] Re: zfs: backport AES-GCM performance accelleration
I've tested this on a Haswell, Intel Core2 Duo and Conroe CPUs under emulation. The latter two CPUS don't have AES instruction sets and work fine. Attached are some benchmarks. Also regression tested on Intel Core2 Duo and Haswell with the ubuntu zfs autotests, so I believe I've covered AES and non-AES code paths in the testing. ** Attachment added: "LibreOffice Calc spreadsheet data from performance tests on a memory backed ZFS encrypted file system." https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+attachment/5380055/+files/zfs-accellerated-performance-test.ods ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1881107 Title: zfs: backport AES-GCM performance accelleration Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. Also test with the 4 types of ZFS ubuntu autotests, should not fail any of these. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
Ahh yes, comment #11 even details how this is reasonable, that the interface speed exceeds the per-link advertisments. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
** Changed in: maas Importance: Undecided => Critical ** Changed in: maas Assignee: (unassigned) => Lee Trager (ltrager) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
It may be that we are not able to assume these figures are the same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
This appears to be a bug in the cisco enic driver. It will always report 1baseT/Full, regardless of the link speed itself. It has always been like this in mainline, and I am also not supprised if the upstream driver is also similarly broken. static int enic_get_ksettings(struct net_device *netdev, struct ethtool_link_ksettings *ecmd) { [...] ethtool_link_ksettings_add_link_mode(ecmd, supported, 1baseT_Full); ethtool_link_ksettings_add_link_mode(ecmd, supported, FIBRE); ethtool_link_ksettings_add_link_mode(ecmd, advertising, 1baseT_Full); ethtool_link_ksettings_add_link_mode(ecmd, advertising, FIBRE); base->port = PORT_FIBRE; if (netif_carrier_ok(netdev)) { base->speed = vnic_dev_port_speed(enic->vdev); base->duplex = DUPLEX_FULL; } else { base->speed = SPEED_UNKNOWN; base->duplex = DUPLEX_UNKNOWN; } [...] } -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
since groovy doesn't have that yet, I'll upload -1ubuntu1 to groovy and -1ubuntu0.1 to focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
That speed comes from drivers/net/ethernet/cisco/enic/enic_ethtool.c:enic_get_ksettings. static int enic_get_ksettings(struct net_device *netdev, struct ethtool_link_ksettings *ecmd) { struct enic *enic = netdev_priv(netdev); struct ethtool_link_settings *base = &ecmd->base; ethtool_link_ksettings_add_link_mode(ecmd, supported, 1baseT_Full); ethtool_link_ksettings_add_link_mode(ecmd, supported, FIBRE); ethtool_link_ksettings_add_link_mode(ecmd, advertising, 1baseT_Full); ethtool_link_ksettings_add_link_mode(ecmd, advertising, FIBRE); base->port = PORT_FIBRE; if (netif_carrier_ok(netdev)) { base->speed = vnic_dev_port_speed(enic->vdev); base->duplex = DUPLEX_FULL; } else { base->speed = SPEED_UNKNOWN; base->duplex = DUPLEX_UNKNOWN; } base->autoneg = AUTONEG_DISABLE; return 0; } vnic_dev_port_speed comes from the hardware at function drivers/net/ethernet/cisco/enic/vnic_dev.c:vnic_dev_notify_setcmd. static int vnic_dev_notify_setcmd(struct vnic_dev *vdev, void *notify_addr, dma_addr_t notify_pa, u16 intr) { u64 a0, a1; int wait = 1000; int r; memset(notify_addr, 0, sizeof(struct vnic_devcmd_notify)); vdev->notify = notify_addr; vdev->notify_pa = notify_pa; a0 = (u64)notify_pa; a1 = ((u64)intr << 32) & 0xULL; a1 += sizeof(struct vnic_devcmd_notify); r = vnic_dev_cmd(vdev, CMD_NOTIFY, &a0, &a1, wait); vdev->notify_sz = (r == 0) ? (u32)a1 : 0; return r; } struct vnic_devcmd_notify { u32 csum; /* checksum over following words */ u32 link_state; /* link up == 1 */ u32 port_speed; /* effective port speed (rate limit) */ u32 mtu;/* MTU */ u32 msglvl; /* requested driver msg lvl */ u32 uif;/* uplink interface */ u32 status; /* status bits (see VNIC_STF_*) */ u32 error; /* error code (see ERR_*) for first ERR */ u32 link_down_cnt; /* running count of link down transitions */ u32 perbi_rebuild_cnt; /* running count of perbi rebuilds */ }; -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
RE: it being a kernel bug A link can span multiple interfaces, so the reported speed of a link can be higher than the individual interfaces . See page 5 https://www.cisco.com/c/dam/en/us/products/collateral/interfaces-modules /unified-computing-system-adapters/vic-tuning-wp.pdf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881821 Title: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade Status in MAAS: Triaged Status in linux package in Ubuntu: Confirmed Bug description: MAAS 2.7.1 Ubuntu 18.04.4 When attempting to commission a Cisco UCS B200 M5 blade, the commissioning finishes (if smartctl-validate is disabled), however on the machine in question in the Networking tab, it only shows 2 nics, eth0 and eth1. and shows no storage. Going to SSH in the middle of commissioning, running lshw shows all 10 NICs, and the disk of the proper size. This is causing the buckets.yaml for FCE to be inaccurate, and thus cannot write a bucketsconfig.yaml since the actual devices don't show up. This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for commissioning, all have the same behavior. I was previously hitting this bug https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from comment #10, and am no longer getting any commissioning errors. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1881821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881909] [NEW] Screen tearing [Optimus - GeForce 610m]
Public bug reported: I have screen tearing when using nvidia card with 390 driver, affect browsers such as firefox and chromium also desktop since I have screen tearing when moving window around. I have no such problem when using using 18.04.4 and nvidia card with 390 driver. Intel graphic have no such problem weather in 18.04 or 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 21:18:49 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652] InstallationDate: Installed on 2020-06-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK Computer Inc. K43SD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SD.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K43SD 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.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K43SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Summary changed: - Screen tearing [Optimus] + Screen tearing [Optimus - GeForce 610m] ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1881909 Title: Screen tearing [Optimus - GeForce 610m] Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I have screen tearing when using nvidia card with 390 driver, affect browsers such as firefox and chromium also desktop since I have screen tearing when moving window around. I have no such problem when using using 18.04.4 and nvidia card with 390 driver. Intel graphic have no such problem weather in 18.04 or 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 21:18:49 2020 DistUpgraded: Fresh i
[Kernel-packages] [Bug 1839124] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle
The workaround is to unload the linux kernel module before suspend. But most likely this needs to be fixed in kernel driver or firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839124 Title: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: A generic issue which happens on Intel BT(8087:0aaa) and Atheros BT(0cf3:e005)(0cf3:e007). Once the system has paired with BT4 devices(disconnected), the system will be waken up randomly from S3/s2idle while receiving advertising packet from any random BT4 devices in the environment which are even not paired/connected. By removing all previously paired BT4 devices(disconnected) from BT menu can fix this issue. The advertising packet could be none connectable undirected or connectable undirected. And the BT4 devices we found can reproduce this issue are 1. Microsoft Surface 1678 2. Logitech K375s 3. Microsoft Designer Mouse --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1539 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0FN010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881909] [NEW] Screen tearing [Optimus - GeForce 610m]
You have been subscribed to a public bug: I have screen tearing when using nvidia card with 390 driver, affect browsers such as firefox and chromium also desktop since I have screen tearing when moving window around. I have no such problem when using using 18.04.4 and nvidia card with 390 driver. Intel graphic have no such problem weather in 18.04 or 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 21:18:49 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652] InstallationDate: Installed on 2020-06-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK Computer Inc. K43SD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SD.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K43SD 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.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K43SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Screen tearing [Optimus - GeForce 610m] https://bugs.launchpad.net/bugs/1881909 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 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 1881907] 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 1881907 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/1881907 Title: xfrm interface: fix oops when deleting a x-netns interface Status in linux package in Ubuntu: Incomplete Bug description: [Impact] When a netns is removed, it may corrupt x-netns xfrm interfaces that have their link part in this netns. It will later trigger an oops when those interfaces are removed. This problem has been fixed in the upstream commit c95c5f58b35e ("xfrm interface: fix oops when deleting a x-netns interface"): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c95c5f58b35e [Test Case] The steps to reproduce the oops is explained in the commit log of the upstream patch. [Regression Potential] The patch affects only the xfrm interface driver, more precisely, the deletion part. Thus, the potential regressions are limited to this area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881907] [NEW] xfrm interface: fix oops when deleting a x-netns interface
Public bug reported: [Impact] When a netns is removed, it may corrupt x-netns xfrm interfaces that have their link part in this netns. It will later trigger an oops when those interfaces are removed. This problem has been fixed in the upstream commit c95c5f58b35e ("xfrm interface: fix oops when deleting a x-netns interface"): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c95c5f58b35e [Test Case] The steps to reproduce the oops is explained in the commit log of the upstream patch. [Regression Potential] The patch affects only the xfrm interface driver, more precisely, the deletion part. Thus, the potential regressions are limited to this area. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881907 Title: xfrm interface: fix oops when deleting a x-netns interface Status in linux package in Ubuntu: New Bug description: [Impact] When a netns is removed, it may corrupt x-netns xfrm interfaces that have their link part in this netns. It will later trigger an oops when those interfaces are removed. This problem has been fixed in the upstream commit c95c5f58b35e ("xfrm interface: fix oops when deleting a x-netns interface"): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c95c5f58b35e [Test Case] The steps to reproduce the oops is explained in the commit log of the upstream patch. [Regression Potential] The patch affects only the xfrm interface driver, more precisely, the deletion part. Thus, the potential regressions are limited to this area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881907/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879711] Re: aws: disable CONFIG_DMA_CMA
** Changed in: linux-aws (Ubuntu Eoan) Assignee: (unassigned) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1879711 Title: aws: disable CONFIG_DMA_CMA Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: In Progress Status in linux-aws source package in Focal: In Progress Bug description: [Impact] The option CONFIG_DMA_CMA seems to cause hibernation failures on the t2.* instance types (Xen). With this option enabled device drivers are allowed to use the Contiguous Memory Allocator (CMA) for DMA operations. So, drivers can allocate large physically-contiguous blocks of memory, instead of relying on the I/O map or scatter-gather support. However, on resume, the memory used by DMA needs to be re-initialized / re-allocated, but it may fail to allocate large chunks of contiguous memory due to the fact that we also need to restore the hibernation image, using more memory and causing a system hang during the resume process. [Test case] Hibernate / resume any t2.* instance (especially t2.nano, where the problem seems to happen 100% of the times after 2 consecutive hibernate/resume cycles). [Fix] Disable CONFIG_DMA_CMA. NOTE: this option is already disabled in the generic kernel (see LP: #1362261). With this option disabled the success rate of hibernation on the t2.* instance types during our tests jumped to 100%. [Regression potential] It is a .config change, no regression potential except for the fact that disabling this option also disables the module 'etnaviv' (Vivante graphic card), that is not really needed in the aws kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1879711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881888] 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/1881888 Title: Atheros AR3012 BluetoothBluetooth [04ca:300b] Always Disconnected After Suspend Status in linux package in Ubuntu: Confirmed Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881888] Re: Atheros AR3012 Bluetooth Bluetooth [04ca:300b] Always Disconnected After Suspend
** Summary changed: - Bluetooth Always Disconnected After Suspend + Atheros AR3012 BluetoothBluetooth [04ca:300b] Always Disconnected After Suspend -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881888 Title: Atheros AR3012 BluetoothBluetooth [04ca:300b] Always Disconnected After Suspend Status in linux package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Tags added: hwe-bluetooth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881888 Title: Bluetooth Always Disconnected After Suspend Status in linux package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Package changed: bluez (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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in linux package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
Not conclusive this's a kernel driver issue yet, also affects to "wpa" as wpasupplicant could be related. ** Also affects: wpa (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Status in wpa package in Ubuntu: New Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
Can you please attach full dmesg for v5.7? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876875] Re: Improve download-signed script to support current & grub2
** Changed in: s390-tools-signed (Ubuntu) Status: New => Won't Fix ** Changed in: linux-signed (Ubuntu) Importance: Undecided => Wishlist ** Changed in: linux-signed (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1876875 Title: Improve download-signed script to support current & grub2 Status in grub2-signed package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Committed Status in s390-tools-signed package in Ubuntu: Won't Fix Bug description: [Impact] * Improve and generalise download-signed script to allow using it with any signed binaries we care about * Add support to download simply the most current version * Add support to download /uefi/ signed binaries * Clean up arg parsing, add help, drop unused statements & imports. [Test Case] * Test downloading signed kernel works with public & private archives * Test that rebuilt signed .debs are the same [Regression Potential] * This is a built time script, as long the binaries are downloaded & packaged up the same, there is no end-user facing impact. [Other Info] * With these changes, download-signed script can be used by s390-tools-signed & grub2-signed, as well as all the kernels. * This is needed to support resigning with different keys for different ubuntu products. For example, UC20 uses the same grub binaries, but wants an additional trustpath to UC20 CA for grade:secured core images. At the moment creating such a signature is only possible via a round-trip in a PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1876875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
Use the same BIOS, on KDE of 20.04. Attach a USB-C to DP monitor and a Lenovo dock. This issue is not reproduced. Probably it is caused by usb-c to DP dongle or dock. Could you try unplug one or both of them? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "hciconfig adapter info" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380006/+files/hciconfig ** Description changed: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 - L2CAP: Connection Response (0x03) ident 16 len 8 - Destination CID: 0 - Source CID: 68 - Result: Connection refused - PSM not supported (0x0002) - Status: No further information available (0x) + L2CAP: Connection Response (0x03) ident 16 len 8 + Destination CID: 0 + Source CID: 68 + Result: Connection refused - PSM not supported (0x0002) + Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) + bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 - UP RUNNING PSCAN - RX bytes:3010 acl:50 sco:0 events:153 errors:0 - TX bytes:5047 acl:50 sco:0 commands:67 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 + UP RUNNING PSCAN + RX bytes:3010 acl:50 sco:0 events:153 errors:0 + TX bytes:5047 acl:50 sco:0 commands:67 errors:0 -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.
[Kernel-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "hcitrace from btmon (snoop format)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380001/+files/btmon.hcitrace.snoop -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881888] [NEW] Bluetooth Always Disconnected After Suspend
Public bug reported: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "hcitrace from btmon" https://bugs.launchpad.net/bugs/1881888/+attachment/5379984/+files/btmon.hcitrace.txt -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.ver
[Kernel-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380002/+files/bugreport.syslog -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "devices list (bluetoothctl)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380003/+files/bluetoothctl.devices -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "show output (bluetoothctl)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380004/+files/bluetoothctl.show -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881888] Re: Bluetooth Always Disconnected After Suspend
** Attachment added: "vivo device (bluetoothctl)" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+attachment/5380005/+files/bluetoothctl.vivo.info -- 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/1881888 Title: Bluetooth Always Disconnected After Suspend Status in bluez package in Ubuntu: New Bug description: After suspend (either manually or automatically), every time I connect my phone to the computer through bluetooth, it always disconnected after several seconds. Inspecting hcitrace from btmon, I got: ``` < ACL Data TX: Handle 21 flags 0x00 dlen 16 #209 [hci0] 121.395244 L2CAP: Connection Response (0x03) ident 16 len 8 Destination CID: 0 Source CID: 68 Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x) > ``` Often, the symptom is when I play audio from connected phone, I didn't hear the sound from my headset connected on my computer, even though I maxed out volume on the phone. The problem does not occur when the computer rebooted. Bluetooth Phone Device: vivo 1609 (Vivo V5 Lite) Bluetooth Device Version: 2.5 (Bluetooth Share APK) bluetoothctl version: 5.53 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 17:47:59 2020 InstallationDate: Installed on 2020-05-05 (28 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=30956875-cf76-41af-963e-866e73f8e23e ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E5-571 dmi.product.sku: Aspire E5-571_0866_V1.04 dmi.product.version: V1.04 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:0F:06:FB ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:3010 acl:50 sco:0 events:153 errors:0 TX bytes:5047 acl:50 sco:0 commands:67 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871977] Re: g_ether not working after reboot
Sorry OTG is not working on my Pi4 after upgrade to Focal, so I cannot tell. Again, pls. refer to bug #1861070 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1871977 Title: g_ether not working after reboot Status in linux-raspi package in Ubuntu: Incomplete Status in linux-raspi2 package in Ubuntu: Incomplete Status in linux-raspi2 source package in Eoan: New Status in linux-raspi source package in Focal: Confirmed Bug description: There is an issue with g_ether after warm reboot. Hardware I used for testing: Thinkpad L470 + Dock, Ubuntu 19.10 USB 3.0 "A male-plug Y-cable" + USB-A to USB-C adapter Pi4 4GB powered by Y-cable connecting to dock and separate USB PSU, Ubuntu 19.10 == it seems like whenever I reboot my Pi, USB gadget port is not detected. How to reproduce: 1) make sure g_ether works on Pi 4 2) make sure cdc_ether works on L470, as in dmesg it shows... [112961.147030] usb 1-3.2: new high-speed USB device number 11 using xhci_hcd [112961.237399] usb 1-3.2: New USB device found, idVendor=045e, idProduct=0301, bcdDevice= 5.03 [112961.237406] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [112961.237411] usb 1-3.2: Product: USB Adapter [112961.237414] usb 1-3.2: Manufacturer: Raspberry Pi [112961.237418] usb 1-3.2: SerialNumber: ***MASKED*** [112961.245067] cdc_ether 1-3.2:1.0 eth1: register 'cdc_ether' at usb-:00:14.0-3.2, CDC Ethernet Device, ***MASKED*** 3) verify IP connectivity works from L470 to Pi 4. 4) reboot Pi 4; on L470 it shows: [113343.783925] usb 1-3.2: USB disconnect, device number 11 [113343.784164] cdc_ether 1-3.2:1.0 eth1: unregister 'cdc_ether' usb-:00:14.0-3.2, CDC Ethernet Device 5) wait for Pi 4 to become available (I use wifi on Pi 4 + ssh on L470) == Expected: Pi4 should show up to L470 as USB ethernet gadget after warm reboot Actual: g_ether is loaded on Pi4 but L470 does not detect it Workaround: unplug Pi4 and plug in again, it will work; given that I am using Y-cable, unplugging will not power down Pi 4. Concern: lose connectivity that needs human intervention to correct, i.e. cannot do it remotely. Note: I remember it is detected okay before I file for bug #1861070, not sure if it is related or not. using g_cdc should be the same, but not separately tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1871977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861070] Re: Raspberry Pi 4B: USB OTG is not working
I just upgraded to Focal and yes, the issue just come back. ## from dmesg ## [5.722325] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [5.722385] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [5.722541] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host So unlikely the compilation flag is applied to the current Focal kernel. ## from dpkg -l ## ii linux-raspi2 5.4.0.1011.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Triaged Status in linux-raspi2 source package in Eoan: Fix Released Status in linux-raspi source package in Focal: Fix Committed Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by default, very very few users will choose dwc2 driver, and the dwc2 driver is not enabled by default in our kernel. And bug reporter and I already tested that the peripheral mode works after this change. I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1
[Kernel-packages] [Bug 1864132] Re: g_ether missing eem support
Sorry I cannot tell, as the OTG issue just come back after I upgraded to Focal via do-release-upgrade. Pls. refer to bug #1861070 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1864132 Title: g_ether missing eem support Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Eoan: New Bug description: I am looking into enabling EEM with g_ether by module option use_eem=1, and g_ether won't be loaded because it has no EEM support compiled. Expected: EEM is compiled with g_ether (no such option for g_cdc) so that it can be enabled by use_eem=1. My "/sys/module/g_ether/parameters": -r--r--r-- 1 root root 4096 Feb 20 13:40 bcdDevice -r--r--r-- 1 root root 4096 Feb 20 13:40 dev_addr -r--r--r-- 1 root root 4096 Feb 20 13:40 host_addr -r--r--r-- 1 root root 4096 Feb 20 13:40 iManufacturer -r--r--r-- 1 root root 4096 Feb 20 13:40 iProduct -r--r--r-- 1 root root 4096 Feb 20 13:40 iSerialNumber -r--r--r-- 1 root root 4096 Feb 20 13:40 idProduct -r--r--r-- 1 root root 4096 Feb 20 13:40 idVendor -rw-r--r-- 1 root root 4096 Feb 20 14:08 qmult modinfo g_ether: parm: idVendor:USB Vendor ID (ushort) parm: idProduct:USB Product ID (ushort) parm: bcdDevice:USB Device version (BCD) (ushort) parm: iSerialNumber:SerialNumber string (charp) parm: iManufacturer:USB Manufacturer string (charp) parm: iProduct:USB Product string (charp) parm: qmult:queue length multiplier at high/super speed (uint) parm: dev_addr:Device Ethernet Address (charp) parm: host_addr:Host Ethernet Address (charp) parm: use_eem:use CDC EEM mode (bool) dmesg: ... [4.474689] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers ... [5.768660] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [5.772414] g_ether fe98.usb: failed to start g_ether: -2 ... should it be another bug? - There is another issue that when my laptop is connected and the with my Pi 4 reboot, the cdc_ether function provided to my laptop will not be available again until I reconnect the cable (I have USB Y-cable + type-c adapter so I can unplug on laptop side w/o Pi 4 losing power). I remember it was working as expected when I was testing out OTG function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1864132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Hi. Experienced this issue on an HP Envy X360 (Ryzen 2500U) and can confirm #54 fixed resuming from sleep, it also fixed resuming from hibernation for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388] do_syscall_64+0x57/0x190 Oct 21 10:57:26 pc kernel: [ 9475.309392] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
I made another attempt with a kernel from https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.7/ The dmesg looks slightly different. But I think, that the bug behaves a little different every time. Sometimes I just get a black screen, sometimes the picture freezes and sometimes I can still move the mouse cursor over the frozen picture. ** Attachment added: "dmesg with kernel 5.7" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1881494/+attachment/5379977/+files/linux-5.7_gnome_dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 9YN58EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-a
[Kernel-packages] [Bug 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
At the moment, just wait... With some time those oops pages might get analysed automatically and problem report links added to them. Also with time a kernel engineer should be able to help with the amdgpu issue in your dmesg log. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 9YN58EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug